September, 10, 2004 archives

ben hyde writes very smart things about collaborative model synchronization based on my earlier post about decentralized notifications and content distribution.

the privacy issue is something i forgot to mention, but is definitely another factor to consider. (i’m not sure it is a critical issue, but my perspective is likely skewed by how public i am with my list of subscribed blogs.)

here’s another: how does the publisher know how many people are following what they write? (again, not something i personally feel is critical, but i also rarely even look at the stats or logs of my sites.)

jeff barr, of syndic8, is tackling the update-notification distribution problem. (using mod_pubsub.)

sam ruby blogged about feedmesh, an idea for handling the sharing of ping notifications among some of the current collectors.

i probably just missed this when it was mentioned earlier, but you can visit a url like http://yaqs.com/jim winstead and it uses the path info to redirect to the appropriate search results on the yahoo! search site.

it is just an internet-draft, but here is a proposal for bounce address tag verification, which could eventually stem the tide of bounces for messages you did not actually send.

with a pubsub client, you can now get the feed of pings from http://localhost:8000/kn/pings. there's no end-user interface on it, but you can use the subscribe.py client from the mod_pubsub distribution.

this may change, or go away. right now, it only includes results from pings, not the result of aggregated update information.

i have taken this down. the thought from people that know is that something like xmpp or a custom protocol will be more appropriate.