Seb wants a system where people can categorise their posts and put them in a global index. Automatic "topical, shared blog" generation, powered by TrackBack or RadioUserLand's [multi-author weblog tool]. Or something like that.|
Seb wanted a system where people can categorise their posts and put them in a global index. Automatic "topical, shared blog" generation, powered by TrackBack or RadioUserLand's [multi-author weblog tool]. Or something like that.|
Here is an implementation of the concept: TopicExchange.|
([Maximillian Dornseif] is working on TrackBack in Radio. It looks like [Dave Winer is too].)
PhillipPearson, in December 2002, eventually built the TopicExchange, which has nicely solved Seb's problem.|
The server has some XmlRpc methods:|
The server would have some XmlRpc methods:|
:See http://topicexchange.com/doc/xmlrpc for what the real XmlRpc methods look like.|
Seb wanted a system where people can categorise their posts and put them in a global index. Automatic "topical, shared blog" generation, powered by TrackBack or RadioUserLand's [multi-author weblog tool]. Or something like that.
This is very similar to TrackBack. Most of it is TrackBack. The cool thing is that is will be easy to use. Currently TB requires you to create a whole new blog for each topic. This sort of thing would require one mega-blog server that would only work accept posts via TB.
Read the link above for the rest of it. As he says, this approach is a good bootstrap, but IMHO there are still too many steps required for this to be 'ridiculously easy'. It requires everybody involved to create a new category, and the category 'owner' has to poll all their RSS feeds regularly to pick up the info. -- PhillipPearson
Is that what we're doing? Like unmoderated newsgroups, except restricted to blogs and without any restrictions on group creation. I think the original thing here is that the connections should be easy. Easy for bloggers, that is, and hard for spammers. -- PhillipPearson
I don't see why a central server is needed at all. RidiculouslyEasyGroupForming is a great idea, but it can happen using only MeatBall:PeerToPeerSyndication. If you write about a "topic", and so does someone else, then just exchange posts; don't just send them your post, but send them other posts that you have heard on the topic, i.e. route. A network will rapidly form.
This is now exactly like UseNet?, except that it is ridiculously easy to form a new group, and you may as well even reuse some if its protocol, if convenient (I don't know about the UseNet? protocol myself). You don't have to worry about the load on a central server. And there is much more room for innovation.
I would also attach some sort of hop count to each message. I.e. if your group is called "XML", do you really want everything that anyone thinks has to do with XML to come to you? There will be too much traffic. With a MeatBall:PeerToPeerSyndication scheme, you can say things like "I trust Bob's judgement on what is interesting about XML, and I trust his friends , but if you keep going forever there is too much junk. I'll drop everything with a hop count of more than 2". You end up getting a MeatBall:WebOfTrustModeration scheme pretty cheaply.
Hmm. How about if the server is just a Perl script that you can leave on your server. Perhaps a plugin to Movable Type that extends TrackBack?
The important thing to consider here is usability. Everyone uses BloggerApi? clients with Blogger because they can just enter their username and password and get going. To do the same with RadioUserLand requires you to set up three config items and know that the local XmlRpc URL is http://127.0.0.1:5335/RPC2, which is too hard. It's that sort of thing I want to avoid. If it's possible to get it going without that (i.e. with something like RSS autodetection or TrackBack RDF links), that's fine by me.
A little interjection before work starts getting duplicated - the topics being described sound very like those of Topic Maps, which is a well-established system (XTM is an ISO standard). Things might get messy using the XTM XML syntax directly, but this stuff can already be represented easily in RDF - maybe best through one of the translations of TMs to RDF schema. http://www.topicmaps.org
We've been discussing what we called BlogThreads (very close to RidiculouslyEasyGroupForming, I think, but threads are more explicit) and Shelley Powers' proposed implementation of the server (dubbed ThreadNeedle?) here: http://www.quicktopic.com/14/H/P96CAYje2yc. I made a few suggestions that align with the simplicity proposed here. They're in messages , , and . I especially like the idea in  where the thread server locates the proper thread using HTTP_REFERER information.
Assume a central server to host some topics. There can be multiple topic servers, but I don't think this will work with a client app controlling everything. RadioUserLand will need to have an executable part that runs on the server. Maybe on the CommunityServer?
The server has a database which contains:
The server generates the following on demand, perhaps caching them or generating static HTML as required:
The server would have some XmlRpc methods:
I'm fairly convinced that ownership (and group ownership) can be well gained implementing features containing facets of GameTheory? .
(with encouragement to post by SteveYost)
They are both good, they aren't the same, and they have different strengths and weaknesses.
Threadneedle is better for aggregating a human conversation, whose topic meanders under a named thread.
A topic-focused blog won't get you a human conversation (that would be ai-complete). A human conversation won't get you a subject-organized index (not without editing after the fact).
So, one blog that would aggregate the posts on Smart Mobs and Lessig's Code and whatever other books the BlogMob? is reading.
Does anyone want to take a crack at this? I'll be travelling in the coming week, but will have some time after that.
... oh, and we can call it RidiculouslyEasyBookGroupForming? :-)
P.S. Some implementation thoughts:
Then syndicate and aggregate by category.