noahgibbs: Me and my teddy bear at Karaoke after a day of RubyKaigi in HIroshima in 2017 (Default)
noahgibbs ([personal profile] noahgibbs) wrote2004-03-03 05:09 pm

Architecture for Metacommentary

I had an idea, related to (but different from) some things that Anton and I have been talking about lately.

The basic concept is: what if you could leave comments about web sites. *Any* web site. And other people could see your comments along with everybody else's. So products for sale, documentation, all the various information on the web, could be rated blog-style at their existing locations.

There are some problems, naturally, even if you can write your own browser to display the stuff automatically.

For instance: who hosts the comments? You don't want a web site to host its own comments, or unfavorable product reviews can be quietly removed by the person advertising the product! Censorship should be the right only of the original poster, and perhaps of some central rating authority, though preferably not that either.

It could be done as a web portal even now: you'd go to the portal, and browse in the normal way but through their stuff. The portal would automatically add the comments at the end and a form to post your own. However, that requires a portal and thus a central authority, which again leads to conflicts of interest.

You'd like the comments to be hosted by the commentors in some sense, both for security and to distribute the server load. But then how could you look up all the comments from all the servers for a particular web site? You could have a central server that collated all that information, but again you're back to the censorship and scalability problems, just on a smaller task.

So if you were going to store and query this stuff in a relatively peer-to-peer way (storage is easy that way, you just host your own comments), you'd need some kind of distributed query mechanism. The string you're querying on would be the URL -- any page you can bookmark, you can comment on. The returned items would be the comments, or perhaps a list of URLs/locations for them. Having the comments have URLs would make replying and threading relatively easy, though the efficiency might suck.

But how do you do the query? How do you ask the world at large, "say, what do you think of http://www.sleazy.com/cheap/filling/horsemeat.html"?

[identity profile] psychospunk.livejournal.com 2004-03-03 05:37 pm (UTC)(link)
There used to be an application like this a few years back on Windows. I can't remember the name of it anymore, though. Basically, a third party host would have the comments, and when you were running this application, it would allow you to view commentary. Now mind you, this is all from memory, and I never used it myself, but it's been tried unless I dreamed it.

[identity profile] queen-elvis.livejournal.com 2004-03-03 05:50 pm (UTC)(link)
I envision a very high signal-to-noise ratio for these comments. Which I guess is the problem with any internet communication device.

[identity profile] sui66iy.livejournal.com 2004-03-03 05:54 pm (UTC)(link)
There was an app called "Third Voice" that did this back in the heady dot.com days. It was a browser add-on, and used a centralized storage model. ESGear had similar capabilities, I think.

As for distributed query algorithms, you might find MIT's Chord (http://www.pdos.lcs.mit.edu/chord/) work interesting.

The problems that these usually run into are more on the social end: how do you get a large enough group of people to play, so that it's interesting? And once a large enough group is interested, how do you filter out all the crap? You need some sort of community moderation system.

More links...

[identity profile] gizbot.livejournal.com 2004-03-03 10:22 pm (UTC)(link)
My poor brain is leaky; I remember about four companies in the boom based on this technology. There were a few interesting copyright issues and most implemented as a plug-in that allowed some sort of layer with comments. Variations were based around the level of glitz on the layers and how to manage which community's comments made it to your browser. The Gator case made some back down, though Gator obviously mucked with the commercial value of the underlying web page.

The odd spot is that all the basic search terms are too generic: commentary, websites, commuity, mark-up, layers, etc. You could see a write-up on the old back-link and annotation stuff at Kuro5hin.

It feels like a "do research before writing code" kind of topic.