Internet News: "New York-based ActiveBuddy has won a crucial patent covering instant messaging bot-making technology, but hobbyists and amateur developers aren't buying the company's claim that it invented the technology." [Scripting News]

» I'm drawn to wonder;  Does a patent application have a space for you to list your venture backers these days?  Does the patent office even bother to look for prior art?

From www.cpan.org

Net-AIM-0.01.readme                   18-Aug-1999 15:37  1.5K 
Net-AIM-0.01.tar.gz                   18-Aug-1999 16:34   25K 

I think the patent system should be changed into a community based process.  There should be an RSS stream generated by the various offices that details applications under review for processing and trackback should be used to allow the community to comment on them.

As to Tim Kay's assertion:

"If you want to do things that our products allow you to do, your best choice is to use our products," Kay said, referring to the recent launch of the Lite BuddyScript Server, which can be used by hobbyists to develop and run IM bots.

Well I guess I'd be that smug too if I'd just put one over on my competitors.

 

1. Follow my coach.
2. Someone else keeps up on all this nerdy stuff more than I do. Let me subscribe to almost all of his changes, adopting them automatically or at least putting them in a queue for approval. This way I focus on my content and let my coach pick/tweak tools, macros, templates, style sheets, news feed subscriptions, etc.

• I can unsubscribe bit-by-bit (perhaps tweaking my own templates) as I learn more and follow my own path.
• This may be the default for a company, department, community, hosting service.
• Affiliate one or more coach URLs with a "Radio Community Server".

From [a klog apart]

» Wow, here's a powerful idea.  I'm blown away by this.

You could apply it in so many places.  Almost every time you start using a new package and meet up with someone who you would like to mentor you in it.

Next Step -- The Personal VPN. I'm off into another area I don't know anything about -- VPNs. [Blunt Force Trauma]

» Since you've probably got more than one computer at home anyway I would be inclined to look into one of the cable/DSL switches that also provides VPN.  For example, the cable router that I could end up buying is the LinkSys BEFSX41 which includes built in VPN capability.  At the back of my mind not running this through Windows hopefully exposes you to less risks.

I'd appreciate more informed opinions though.

Protecting Radio Folders. A simple Meta tag to keep prying eyes from browsing weblog folders you don't want people to see. [Blunt Force Trauma]

» Another example of the security theme that is developing.  This is obviously going to become more important as Radio seeks to be the de facto PKP tool.

Can I get my referer lists as "RSS" feeds from the "Radio Community Server"?

Can we make the list a rolling 24 or 25 hours instead of a clean sweep at midnight?

[aka Blue Sky Radio]

[a klog apart]

» Now this would be cool.

TrackBack information should also appear this way (that's how I'm implementing it).

 

 

You know, I don't like the term klogging very much.  It has meaning to us "in the know" but I think it's rather an opaque term.

I would prefer a term like Personal Knowledge Publishing which actually says a little bit about what it means, and, harkens back to the DTP revolution.

I think PKP will hail the same revolution for Knowledge Management by emphasizing that it is people that matter.  Process should follow people.  Let people do what they are good at (thinking, scheming, designing, creating) and help them get it down "on paper" and let process and automation do the rest for them.

The technology should support the individual, not binding them.

1. Catalyst. Alpha blogger. Someone who klogs well, leads by example, provokes and inspires others to join a klogging community. If you've used Blogtree, naming your inspirations, you know what I mean.
   
2. Coach. The person who helps newbies, builds internal FAQs, nurtures laggards, acknowledges great posts. Soft skills, communication and social skills, are not evenly distributed. The coach helps everyone join and get better. Chief metablogger.
   
3. Armorer. Works with IT to develop configs, scripts, integration with enterprise apps and messaging services. Power macros. Engaging templates. Technologist and architect.
   
4. Practice leader. Informal leaders of subcultures in larger organizations. The one in legal who drives the whole department to start klogging. The rep in the Cincinatti sales office who gets her colleagues to start customer-specific blogs. Watch for lists of like-minded colleagues. They may also connect to like-minded communities at suppliers, customers, and the wild blogosphere.

Mix and match.

Recruit for excellence in one or more.

Hire ringers if your community is large enough.

One other point: I beleive (without hard numbers) that blogging and klogging can improve your personal marketability. I'm exploring this at Bloggers for Hire. Suggestions welcome.

[aka klogs]

[a klog apart]

» Phil's roles seem very XP like (and I'm not referring to Windows) to me which is nice as David Gurteen was just talking about XP & KM and how XP's embrace change principle applies just as much to implementing KM.  In fact many of the values embedded in the XP development philosophy apply just as well to KM:

"XP is successful because it stresses customer satisfaction. The methodology is designed to deliver the software your customer needs when it is needed. XP empowers your developers to confidently respond to changing customer requirements, even late in the life cycle."

"This methodology also emphasizes team work. Managers, customers, and developers are all part of a team dedicated to delivering quality software. XP implements a simple, yet effective way to enable groupware style development."

"XP improves a software project in four essential ways; communication, simplicity,feedback, and courage. XP programmers communicate with their customers and fellow programmers. They keep their design simple and clean. They get feedback by testing their software starting on day one. They deliver the system to the customers as early as possible and implement changes as suggested. With this foundation XP programmers are able to courageously respond to changing requirements and technology."