A lot of people have been chatting about how Digg is better than slashdot. I agree wholeheartedly:
- It’s fast to adapt to new media
- It’s pretty
- No (arbitrary/bad) editors
- Community selection and moderation
- Good usable feeds
- Interesting (rather than self-important) content is often found
- Good meta content in the discussions (diggs)
.. and so forth. Digg started out just doing news and some blog entries, but it quickly replaced the “link finding” sites and now it links to just about everything. It’s good. Use it. I’ve pulled slashdot from my aggregator; digg gets all the good stuff anyhow.
But, as long as we’re on a roll, let’s correct a failure that slashdot has always had — use the coral cache.
Of course, the users of digg (insert Tragedy of the Commons reference) think of solutions after the fact, just like slashdot’s editors.
What I propose is that before Digg does more damage, that they become good citizens and run all of their links through the coral cache. Problem solved.
Now, the pundits will argue “we can’t do that, it’s a proxy avoidance technology, and WebSense (and surely numerous others) blocks it.” Yeah, it is. But, instead of blocking the coral cache, proxy authors could real easily apply the same filters to coral urls (just strip off the coral suffix, and then apply your filters) and provide to their users all the same benefits.
So really, I’m making two pleas here:
- Proxy developers, it’s time to wake up and embrace Coral, rather than just banning it because it’s the “easy” solution.
- Digg, let’s get your act together, and avoid breaking the internet, one interesting site at a time.