I've been thinking about a new system for PeerToPeerJournalism. I don't have a name for it yet, so I placed it here. Though, I was thinking of calling it the TINSEL Protocol--The Internet News Subscribed Edited Lists, except that's really lame. Suggestions are welcome.
The system is simple; simple enough to hack in one night's coding giving judicious abuse of Perl. Each user has her own a newsbox. She then subscribes to other newsboxes. Whatever those newsboxes decide to publish, she will receive. She can optionally decide to republish news in her own newsbox (say by clicking a checkbox). Then, others can subscribe to her newsbox too. Content can be created by anyone just by inserting it into his own newsbox.
The system is resistant from attack because idiot nodes will be unsubscribed from and thus lose efficacy. There is no way to push content onto others either. The system distributes load by republishing material throughout the network. Moreover, good material is more likely to be "republished" than bad material, so the system will naturally tend to propogate good material over bad.
It's also trivial to build gateways to foreign networks, like RichSiteSummary feeds or even WebLogs. The system can also work like e-mail by clustering many newsboxes at local clusters, yet allowing them to seemlessly interoperate with other servers. The protocol can also be trivially expressed in HTTP. In fact, it is feasible to run a personal server on your desktop.
For added kicks, a strong local cluster can provide a lot of features, like creating a common content pool. I'm thinking of a UI like Advogato's diary and "new user" lists. This increases the chances of attack, as one could spam the content queue, but additional security can be introduced at that level like rating systems or wiki-style SoftSecurity.
The protocol could be XML, possibly RSS/RDF (??). For efficiency, we can assign each item a UUID, hash value, and timestamp. Then, at the protocol level, a subscriber can get only the item headers to determine whether a story is a duplicate. But these are technical details that's not really interesting right now.
So, what do y'all think? -- SunirShah
Yeah, ok. RadioUserland? is like the LotusNotes to our tinyHTTPD. Actually, I was thinking of implementing this on Jabber as well. It would be fun to build a real-time broadcast news system on an IM/distributed XML platform. Jabber is more fun than SOAP. I'm also thinking of how this might help wiki-like systems exchange pages. Then again, maybe it would be easier just to use RadioUserland?. -- SunirShah
DaveWiner's mechanism for doing subscription/notification can be seperated from his Radio Userland application. He calls the technology xmlStorageSystem, and it's basically an xml-rpc/soap api. And it's also a really lame name, imo. :) But it might do what you're looking for, and it's being incorporated into new tools coming out. hurray for interop.
Here's where to look:
This reminds me my [Social Routing] concept. In communication you have two sides. Each one has some partial information about what information should be transferred. The receiving party knows about his preferences the sending party knows about the information item it is about to send. The task is to build an effective protocol for making decisions about what infomation should be send where. -- ZbigniewLukasiak