RojoLicious = Rojo + Del.icio.us

I finally peaked into rojo this week. Not sure if I am ready to switch from bloglines. Old habits die hard. But, there is a compelling case for it. Very compelling: I use my blog to network. Links are a way to start a conversation with a new person. I do it all the time. I read someone. I get to know what interests them. I start sending them links. Conversation ensues. Relationships develop. Anyways, a smoother process between reading and sharing and writing would be nice. Check it out. (via Allen Searls)

Hjalmar. Where you at?

Spurl.net autopublishes to Del.icio.us and Spurl offers some things that del.icio.us doesn't have like old school categorization (tagging too) + a hook into zniff. Spurl also has a bit of a Your-A-Pee-in following. So, I use spurl. I'd like to see a little more support for spurl on some of these new "lets use the tags in our system" sites.

---------------------------------------
Update:  Noah Brier got me thinking. Tags will cause directories to meet search. Old school top down directories are dead. We have publishing systems, we have sharing systems, we have aggregation and discovery tools, we have search tools. Tags reduce the barrier to hyperlinking. Tags could cause hyperlinking to go mainstream.

Comments

[Allen Searls]

Agreed. I hope to bump into Rojo at Supernova in SF on Tuesday and will definitely mention Spurl if I can.

Altogether, Rojo has been described as a 2nd generation aggregator, meaning they see quality aggregation as a given and focus on things to do over and above aggregating feeds, such as sharing posts, tagging posts, social networking w/ your fellow readers and so forth. I use them and Pluck's tools, together with Pubsub, to do all kinds of things I never knew an aggregator could do.

Allen

[cori schlegel]

I was originally planning on extending Rojolicious to support other bookmarking tools (I use LookSmart's Furl myself) and other configuration-type changes. However I decided that what I had gotten to, with an addition that I haven't published yet, was about the limits of what I wanted to rely on Greasemonkey to support from a configuration standpoint - to do more I'd have to rewrite substantial portions of the GM script for each individual set of configurations, and I didn't want Rojolicious to turn into something akin to CustomizeGoogle

An extension to do those things is on my (ever-growing) task list....