|
 |
Wednesday, October 24, 2001 |
 <>>>>
Important safety alert. Don't download the new upgrade to Microsoft Instant Messenger. Why? It will truly screw with your system. Don't, don't, don't. Nuf said.
9:47:29 PM 
|
|
>>>>
If you are worried about the new expanded powers of the feds to snoop, pry, and generally screw with you try this: coded drag What I am looking for is a plug-in for Outlook Express. It works great as a strong encryption product even though it doesn't have e-mail integration (although, how hard would it be to build something that enable this??) Thanks Austria!
6:45:10 PM
|
|
>>>>
Zeldman. Don't cut your IT budget by using a content management system. He does make a couple good points: 1) Interwoven and Vignette will drain you of so much $moola$ it will make your head spin and that 2) you shouldn't try Zope unless you have a Phd in computer science. The obvious solution is to use a human accessible solution like Manila (which he doesn't mention -- for good reason).
However, JZ decides to tar all CMS's with the same brush and proceeds to make the argument I bet monks across the land (circa 15th century) once said: "Gutenberg can't produce high quality books, you need years of training to do this."
4:55:43 PM
|
|
>>>>
Adam Curry created a blogrolling macro for Manila. Dave rolled it in under an hour. Rolling, rolling, rolling.. keep those bloggies rolling... Rawhide!
4:22:40 PM
|
|
How K-Logs (knowledge management Weblogs) will evolve
K-Logs (88 members and growing)
Here is the result of some thinking I have been doing on how K-Logs have evolved and will eventually emerge as a core part of the desktop productivity suite:
1st Generation. K-Logs as a server-based Internet service. These basic Weblogs used a centralized services model to enable people to publish to the Web. There are a variety of vendors that provide this capability. However, most companies don't want to store vital corporate data outside the firewall. Also, there is a growing fear, given the current economic environment, that these services will suddenly stop working and vital data will be lost.
2nd Generation. Packed K-Log server software. This solution solved some of the problems with the services model by providing corporations with packaged Weblog software that they could install on their Intranet. However, this solution has the same problems with scalability, cost, and flexibility that plague centralized solutions we see in the Web world. Also, centralized software cannot easily take advantage of data stored in desktop applications or provide individuals with a fast loading mobile copy of their critical data.
3rd Generation. Desktop K-Log software. This is the point we are at today. Desktop K-Log software solves the scalability and personal storage issues by decentralizing K-Log development and publishing. Core functionality on this generation of software includes: Weblog publishing, categories, RSS headline aggregation, community data aggregation (recent updates for example), bookmark lists, directories, and file uploads. This decentralized approach provides people with a desktop archive of all information (aggregated or posted) as well as an ability to use the tool in a P2P framework.
4th Generation. Fully integrated desktop K-Log software. This is the generation where K-Logs challenge the current 1980's desktop productivity suite for dominance. This software includes the core functionality included in the 3rd generation but also: outlines, structured instant messaging, full e-mail integration, and P2P file/data transfer. Also, this software will fully integrate with corporate Webservices to allow employees to gather important information that can be then posted to his/her K-Log (for example: a SOAP service the provides sales figures at the end of each day -- more on this later). This tool is the end-point that can be fully customized by corporations to fit their needs. It allows an employee to aggregate dozens of data sources, analyze that data, and post it with an annotation to a K-Log (or multiple K-Logs based on categories). It breaks down data silos and puts otherwise random data into context that has meaning and structure. That posted knowledge can be searched, sorted and used by all employees with the appropriate access to improve their ability to do their job.
1:06:38 PM
|
|
>>>>
CoM. How vulnerable are the Saudi Oil fields?
11:26:42 AM
|
|
Why are all the P2P companies brain-dead??
Kontiki just released their new desktop P2P file transfer system. I have it running on my desktop now. Kontiki is the latest in a series of well funded P2P companies that were in aggregate able to suck down $100 m plus in VC money over the last year. It is a little slicker than Napster but it has the same flaws that make it still-born as a product.
Why? Kontiki and other P2P efforts don't leverage the Web. At this point we know how to build compelling Websites. Additionally, most compelling Websites are dynamic, in that they rely on a database and a content management system (CMS). So, for a P2P system to be truly compelling as a product it needs to be able to distribute complete dynamic Websites to PCs. What's missing in the Kontiki system? A desktop database, CMS, and http server (like Radio).
9:39:34 AM
|
|
The "Internet Desktop"
The Register. Blackcomb not until 2003 at the earliest. 2005 is likely says Gartner. Blackcomb is the real .Net operating system.
Here's the situation. For years Microsoft played a fast follower role to innovative developers (a fast follower targets innovators and quickly matches their innovations). However, its success as a fast follower have all but killed funding for an independent developer community focused on innovative products for Windows. It now finds itself forced with the task of leading development for the next generation of desktop software -- which is a task that Microsoft is particularly ill suited for. Note: this is almost the same situation we found ourselves in circa 1994.
It is pretty clear that the next generation of desktop software will remake the PC into a true "Internet Desktop" which includes three new technologies:
1) A desktop database (+ CMS ++ HTTP Server)
2) P2P connections (for IM, file transfer, Web service transport)
3) Connections to Web services
Blackcomb is expected to include these technologies, however, without an innovative independent developer community Microsoft is at a loss as to how to weave them together into compelling products. There are developers out there with a clue on how to do this, but given the history of competition with Microsoft there isn't much chance they will get the support they need to go forward.
8:59:03 AM
|
|
>>>>
Wired. Disney execs use children's programming to drive home anti-napster message. Message: "Good kids don't let their friends steal music"
8:09:17 AM
|
|
>>>>
News.com Time to pull the plug on AltaVista.
8:05:32 AM
|
|
>>>>
NYT. iPod.
""Mr. Jobs said the company had taken some steps to protect against piracy in its device. For instance, he said, songs loaded onto the iPod from a Macintosh computer, cannot then be loaded from the device to a different Macintosh computer, a step he said would make it difficult for people to distribute music they own to other users.""
Does anybody have a hack for this yet???
7:59:19 AM
|
|
© Copyright 2004 John Robb.
|
|
|
