October 26, 2005
Reblog's 1.0 announcement promised "push-button republishing for the masses", and we've been doing pretty well following that track for the past year or so. Last night, we pushed the button on Reblog 2.0. The concept behind the software has always been a form of attention cagefight: many feeds go in, one feed comes out. Reblog closes the loop between piqued interest and publishing by making the act of marking a link for publication a one-step affair. We've long thought this was a pretty interesting addition to the standard functionality of an RSS reader, and I'm surprised to see that in late 2005, there's not a lot of other software that performs the same task.
In the meantime, Reblog has started to see slow but steady growth. Eyebeam and Rhizome both use the software to publish net art blogs, and Eyebeam has an explicit "curator" role in the fortnightly reblogger. Global Voices Online has expressed strong interest in adapting the project to their multitiered reblogging operation, and Reblg from Broadband Mechanics borrowed the term for a similar idea based on microformat republishing from within the browser. A lot of these uses place Reblog in the role of plumbing: like the mixer in your shower, it's there behind the wall but you never see it. Reblog's output is typically meant to be fed into a MoveableType or WordPress plugin, where it surfaces as a series of blog posts on an HTML site annoted with "Originally by so-and-so from..." attribution notes.
We've been thinking a bunch about expanding this role a bit, so that the RSS output from Reblog carries more weight. What happens when you chain a bunch of Reblog installations together, so that the output of one person's attention stream becomes fodder for the next? You get an omnidirectional passive e-mail substitute, great for washes of "FYI" type information and general interest sharing. In a lot of use cases there's no reason for the output to ever make it to a regular blog. Small, distributed groups can use the software to share information among themselves, and only escalate to the relatively disruptive e-mail level when action or response is required. Alternatively, chaining feeds together could result in a progressive-filtering mechanism, reducing the complexity of a thousand feeds into a few pertinent pieces of information through a pyramid of editors.
So, with the interest of making Reblog a more flexible sharing tool, we worked on version 2.0 with a few broad goals in mind:
-
Usability: Reblog's user interface needed to help the end-user manage large numbers of feeds more effectively. Tagging feeds & entries has proven to be the most flexible way to accomplish this. We were also interested in ways of making the interface look less... dorky. There was a lot of techno-cruft that just had to go.
-
Extensible Input via a public API: Greasemonkey is pretty damn cool, so we thought it'd be useful to provide for a way to perform common Reblog editing actions via a programmable API. XML is boring to parse, so Reblog now has a JSON-RPC API exposed.
-
Extensible Output via support for plug-ins: We were strongly interested in seeing some sort of plug-in ecosystem evolve around Reblog. If the software's useful, it makes sense to provide for a way to adapt it to specific uses. My own guide for this has been Blosxom, a simple blog engine written in Perl.
One huge change that became apparent as we wrote 2.0 was the need to post your own entries, independent of any particular feed. Historically, Reblog 1.x assumes that the target blog would be used for this purpose. In 2.0 we've added a "post item" feature, which acts as stripped-down Blogger or Del.icio.us analogue, and handles one of the primary uses cases suggested by Reblg. This idea has been gaining some traction recently, most conspicuously in Mark Pilgrim's microformat atom store concept. Mark decribes the idea as "having your own private database", but my own takeaway from Del.icio.us has been the value of making such micro-information public. Reblog is built to share. Bud Gibson has been referring to this idea as the xFolk Veg-o-matic, a slice & dice greasemonkey-based browser augmentation that trawls websites for microformatted links and posts them into Reblog for you.
We believe this is pretty cool.
|
unmediated.av:
The Weekly Show
drawing from extrastruggle.
We've been having a back channel conversation amongst the trackers at unmediated about how/whether to update the way in which we aggregate, present, and make useable the content on the site, in light of all the various aggregators, digg and its clones, and role model group blog sites that we all consume/use/hate/love. Since we all primarily support open media movements and the freedom of bits and so forth, and with all of us being busy with our primary projects, we are looking for ways to make getting content on the site easier and more streamlined, while making it obvious that we are presenting other sources content. With the availability of open API's for just about any type of media aggegration literally getting past the saturation point, and mashups taking every possible form, we are wondering, is it time to take a step back, or a step forward with how/what we do at umediated? In the course of my surfing today, i found this new site, Boxxet Which just might be the straw that breaks the camel's back in how we all perceive the current mix and match nature of the web as it now stands. What's different about Boxxet from other aggregators and mashups like the newest entry popurls, (which aggregates digg, slashdot, reddit, newsvine, tailrank, and flickr) is that Boxxet is a Website generator. Thats right, just pop in all the urls u want to aggregate (and WHAT from them) choose how u want to format it, plug in the url that u want it to be accessed at... and whammo: Your own site with everyone elses content, and all thats left to do is decide whether googleplex or yahooza is going to be the source of your linklove revenue. And if u have on older domain that u plug this into...well, we all know how the pageranking with search engines work by now. It used to be that u had to have a bit of code knowledge to make all this stuff work. Eyebeam's Re-blog engine which powers this site was not a simple undertaking at the time that Michael Frumin and Michael Migurski put it all together... a half a year before Marc Broadband-mechanicked the term Reblog as his latest buzzword before casting his attention on the ourmedia-meme. (kudo's, kudo's) But now, with the cut and paste mentality of webculture that we at unmediated have helped create, the pace at which people are remixing and repurposing code is accelerating at a rate similar to the curve that we saw with pro-sumer desktop video... almost anyone can do it. I have this sinking feeling in my gut that we will arrive sooner than later at the same existential threshold that the film studios and record labels are squirming under to our joyful cries of "die, dinosaurs, die!". What i am wondering, is how long until my hero of the open-information movement, Cory Doctorow, and the rest of our pals at BB will tolerate re-aggregation and repurposing of his content, (now that he is investing so much more time at the site) before he (or any of one us) screams, "FOUL!" Stewart Butterfield over at Flickr is dealing with this beast at the moment...and i have to admire the dryness with which he states, "I loaded the FlickrCentral pool and firefox got up to using 240mb of ram before dying. So that's not a great user experience, but it's really terrible for Flickr. If it catches on and you don't limit it, we'll have to cut you off :\" Sure, Stewart, blame it on the user experience and firefox. ;) I admire your candor, and personal attention/approach to what has become one of the hottest new BRANDS in Web 2.0 ...that u still have time to be personal and all flickr-fuzzy even after being acquired, but I am sure that your jeans feel like they're fitting a bit tighter all of a sudden. Pretty soon, I expect, a lot of us bell-bottomed infornistas are going to wake up in a similar pair of Jordaches. I'm curious which of us will cut the inseams and sew in another totally different material to keep our style,and which of us will claim that now that we're wearing skintight jeans ("they're really really comfortable...REALLY! You think i should get a pair of Reeboks to go with 'em?"), that the manufacture of bell-bottoms should be forbidden. I point this all out in good humour only to illustrate a point: The times, they are('nt) a changin'>, and Cory just might wake up one day soon in his magic kingdom, and say "Hey, man, where'd all my whuffie go? And he's going to have no choice but to join Walt's pinstripesuits in pushing for copyright extension. It's a pill i hope he (and we) never have to swallow. So i pose the question to our community readers: How do you see unmediated-Are we crossing the boundaries in how we repurpose content? Would you like to see more editorializing? Narrower/Broader scope? Are we a repository of information that you come back to use, or just part of your daily information addiction? Let us know... I, for one, would like to have an idea about what pair of jeans to wear this year ;) michael
Featured Project
Berkeley Conference: Online Video and the Future of Television - Friday, September 30, 2005
This one-day conference brings together archivists, educators, technologists, entrepreneurs, producers, legal experts, and investors to explore the enormous promise offered by the availability of online video and television content. Demonstrations and interactive panel discussions will highlight new video technologies, services, legal issues, and economic models. Participants from diverse – and until now, largely disconnected – specialties will be especially encouraged to interact.
del.icio.us/tag/unmediated
[+]
About unmediated
unmediated is a group blog that tracks the tools, processes,
and ideas being used to decentralize media production and distribution.
|
flickr/tag/
citizenmedia
[+]
|
