(SOURCE:"curious")-I guess this makes Live Topics obsolete. Can't wait to try it.
<quote>
Paolo and I are now subscribed to a single shared cloud (called WWWW) of topics using the k-collector server and client for Radio. This means that our posts will be aggregated together by k-collector on the basis of the topics we use. The demo interface shows a simple hierarchical view but we have lots of other things planned. Another poweful feature of this setup is the shared topic roll. Because we are both subscribed to the WWWW topic roll we use the same topics and any topics we create are automatically made available to other subscribers.
</quote> [Roland Tanglao: KLogs]

Excellent! Blogs = Instant publishing!
<quote>
Blogs are instant publishing. You write, you cut-and-paste images, you cut-and-paste links, you customize everything through a WYSIWIG interface, and with one click you publish. There is no Webmaster. There is no gatekeeper (necessarily). There's just you, your PC, your Internet connection, and a form. Think of HTML as a language for creating Web pages. Blogging is simply a Graphical User Interface that makes creating "content" as easy as -- writing. (And with audioblogging or videoblogging or blogs that just consist of pictures, photos, or other images -- it doesn't even have to be writing.) The implications of this are as profound as the implications of the Web itself. They are not limited to journalism. That is its public face, because blogging software is such a great tool for journalists. A lot more publications -- not just National Review and The Nation, are going to switch to a blogging format over the next year, because it saves a ton of money. But that is the tip of the iceberg. Blogging is going to be a great education tool. Blogging is the perfect groupware tool. Blogging really is Personal Publishing, the promise of HTML fulfilled.
</quote> [Roland Tanglao: KLogs]

(SOURCE:"curious")-A picture is worth a thousand words.
<quote>
K-collector. Matt has already written about k-collector today here and here. What can I add? Maybe a little drawing?
</quote> [Roland Tanglao: KLogs]

(SOURCE:Corante Social Software) - Nice counterpoint to WhyWikiWorksNot! [Roland Tanglao: KLogs]

(SOURCE:Corante Social Software) [Roland Tanglao: KLogs]

(SOURCE:"emm")-Nice!
<quote>
I thought that it would be cool to have a page that showed all the pictures that I have used in my blog postings. The myPictures tool that comes with Radio Userland puts the pictures in a year/month/day directory structure so I wanted to work with that in a recursive nature. Here is what mine looks like. I ended up doing two different macros: one for main main blog and one for categories. For the main blog macro, I decided to move my myPictures directory to wwwphotos because I don't want all the different template graphics showing up in my blog. For the category macro, I used the images directory because it doesn't seem to suffer from that problem. You can adjust as necessary.
</quote> [Roland Tanglao: KLogs]

(SOURCE:"mcgee")-Wow! A wondefully pragmatic proposal that not only sells blogs to business but also clearly explains how to train new bloggers and work around obstacles! Bravo!
<quote>
Implementation and Training Each person selected to have a weblog then needs to be trained how to set up and use the tool. This entails: * Setting up the weblog's personal taxonomy (categories) corresponding to their filing cabinet tabs or 'My Documents' folders * Setting up the weblog's 'permanent files': documents that are regularly and repeatedly used such as contact lists and policy documents * Setting up the weblog's links, directories, and subscriptions * Helping the weblog owner decide on appropriate publishing decision rules : what knowledge (reports, analyses etc,) he/she will be expected to create, what knowledge from other sources he/she will be expected to propagate, and who will be permitted or required to access or subscribe to which weblog categories * Helping the weblog owner decide explicitly what doesn't get published, to avoid confidentiality risks, intellectual property law violations, and information overload * Training the weblog owner to pause each time he/she saves or sends a document, link, or message, and decide whether to publish it to the weblog at the same time, using the agreed-upon decision rules * Possibly teaching the weblog owner how to create document abstracts, how to properly categorize posts, and how to notify potentially interested users of a post who aren't already subscribed The Five Obstacles I forsee five major obstacles to the successful introduction of weblogs into large organizations: * HTML / Microsoft format conversion. Most large companies use MS Office as their principal document standard, and the conversion of Office documents to HTML remains a bloated and untidy process. * Authoring rights: Decisions need to be made about who can post to each weblog, and about the potential use of 'group' weblogs, which in many organizations will be political. * Proprietary macros: Existing commercial weblog software is too complex and techy for the average business user, so customization will be needed to keep weblog maintenance as simple as possible for neophyte users. * Intermediation: Many business executives will want to delegate responsibility for their weblog to an administrative assistant or knowledge steward, which may complicate the process and dilute the benefit of using weblogs. * New knowledge behaviours: Weblog owners will need to learn to develop and use appropriate publishing decision criteria and how to abstract and categorize the knowledge they produce. It's no longer just their filing cabinet. The key to success is to pick the spots in your organization where weblogs can solve pressing business problems, make a compelling case for their use, ensure the weblog owners are properly trained, and anticipate and deal with obstacles in advance. Given the enormous potential of weblogs to realize some of the long-awaited benefits of knowledge management, this should be well worth the effort.
</quote> [Roland Tanglao: KLogs]