Collab.klog.km

KMpings & Trackback. The KMpings Experiment.
I created a little blog called KMpings that allows any blogger writing about knowledge management to ping their post to a tracking page (if their software supports it). Think of it as a themed www.weblogs.com for the knowledge management community.
I wanted to try out this experiment since I think the TrackBack function created by Movable Type has a lot of potential for aggregating blog posts within communities of practice on the web or an intranet. Please post any feed back you have to this message or shoot me an e-mail. [High Context]

» I really want TrackBack for Radio.

And KMpings sounds like a great idea.
[Curiouser and curiouser!]

Possible Community Server for Intranet

7:13:35 PM

comment []

An announcement from Macrobytes on a server-side security product for Frontier and Radio Userland. I'm looking into Macrobyte's Conversant community server as a framework for Radio-based collaboration.

Macrobyte Resources: TLS 0.3 for Frontier and Radio UserLand. "TLS provides client side tools for making secure HTTPS requests, and server side tools for running a secure web server."[Frontier News]

TopicRolling Update

7:03:11 PM

comment []

I still have trouble visualizing some of these interBlogatary referential rolling efforts, but I'm learning to trust a few of these Radio guys. We'll see where this one goes.

TopicRolling 101.
A feature that I have planned for the next release of liveTopics (the finishing touches go on the 1.0 release this week, for definite) is the topicRoll.
In the same way as a blogroll represents your subscription to other what other people are writing, the topicRoll represents your subscription to what other people are writing about -- their topics.
Whenever you add a topic to a post it is added to your topicRoll and (optionally) published automatically to your weblog. In turn you can subscribe to as many other topicRolls as you like. This means that as soon as someone uses a new topic, it is automatically added to the topics that your copy of liveTopics has ready for you to use. In the same way other users can see & re-use the topics you are using.
When combined with the idea of topicMiner (also due in version 1.5) this will allow you to thread together existing archived discussions in a completely new way. Mining topics allows you to find existing topics in archived posts. You will be able to mine other peoples topics from your own posts and vice verca.
I'm hoping this will enable some interesting cross-blog exchanges.

[Curiouser and curiouser!]

See also: Blunt Force Trauma | Blunt Force Trauma | Blunt Force Trauma | Curiouser and curiouser! : Curiouser and curiouser! | Curiouser and curiouser! : Curiouser and curiouser! | Blunt Force Trauma | Dewayne Mikkelson and his Radio WebDog, Shadow | Blunt Force Trauma | Roland Tanglao's Weblog: Wednesday, July 10, 2002 | Roland Tanglao's Weblog: Wednesday, July 10, 2002

Using Jabber IM for Weblog Change Notification on System Status

1:07:18 AM

comment []

Windley is over my head here, technically, but he makes reference to relevant discussions on the use of IM in the enterprise and points to some experimentation going on with Jabber. Windley thinks Jabber may be the right IM tool for the enterprise and there's more about it on his site.
If we're to have properly automated print manufacturing, then we clearly need easy, simple system notification that can be used in many ways. There is nothing in the industry today that makes reporting, notification, and status updates as ubiquitous or accessible as this simple idea of RSS feeds, weblogs, and a little IM.

IM and REST: First Class Events?.
After posting the previous piece about IM and REST, I happened to see a reference to work DJ Admans is doing with weblog updates and Jabber on Scripting News. The basic idea, as I understand it, is to use Jabber in lieu of something like MQSeries or JMS to notify people of changes to weblogs. I see the usefulness of that: remember those discussions in your undergraduate architecture class about polling vs. interrupts? [...]
[Windley's Enterprise Computing Weblog]

See also: Blunt Force Trauma | Blunt Force Trauma | Blunt Force Trauma | Blunt Force Trauma | Blunt Force Trauma | Blunt Force Trauma | Windley's Enterprise Computing Weblog | News Is Free: Jake's Radio 'Blog: Information About This Channel | News Is Free: Voidstar: Information About This Channel | News Is Free: Jake's Radio 'Blog: Information Apropos de cette

Blogs for System Status

12:52:12 AM

comment []

Phil Windley is CIO for the state of Utah and this guy is thinking like I'm thinking -- a $40 enterprise reporting system. I found Windley's Enterprise computing Weblog via David Gurteen and Windley has some great stuff.

Blogs for System Status Communications.
My organization operates hundreds of servers in several data centers and a network that connects over 250 separate locations. One of the problems we have is status communication to various interested parties. Tonight I decided we should have a system status blog that uses categories with separate RSS feeds for various severity levels and systems. For the low price of $40/year we could have:

One easy spot to post status announcements, which would be ordered in exactly the right way.
A web-based record of status.
Multiple RSS feeds of the various systems and severity levels.
Easy integration into the personalization feature of our intranet; RSS feeds would show up as gadget boxes for people who want them.
The ability to easily subscribe to RSS feeds and digest them in various ways for people with special needs.
How could you not like that?
[Windley's Enterprise Computing Weblog]

See also: Windley's Enterprise Computing Weblog | Windley's Enterprise Computing Weblog | GURTEEN - Weblog Entry: Blogs for System Status Communications by | System Status | Blog Studio - fast. free. simple. reliable. | Jarrett House North : The CIO of Utah gets it | Jarrett House North : | Software Poetry - Blog a Better NOC with KBnow | Blunt Force Trauma | Paul's Radio Weblog