Commentary

Alexander Wolfe
 

Digg Jumps The Shark

Has success gone to Digg's head? The popular community destination, which drives lots of traffic to needy news sites and blogs (like yours truly's) has decided to update its story-input interface. It's a mistake; a big mistake.

Has success gone to Digg's head? The popular community destination, which drives lots of traffic to needy news sites and blogs (like yours truly's) has decided to update its story-input interface. It's a mistake; a big mistake.Used to be that Digg had a fairly clunky, but effective, interface, through which you entered the URL of the story you wanted to put into its queue, so that readers could vote for (aka "Digg") it. The more Diggs, the higher the story rose, so that a story with several hundred Diggs (and sometimes as few as 70 Diggs, depending on the rotation) would make it onto the home page.

Stuff so positioned would get tens of thousands of click-throughs, hence the importance of Digg as a referrer for blogs and news sites both large and small. You read that right: even sites as seemingly high and mighty as InformationWeek and competitors like ZDNet, eWeek, and ComputerWorld love to get a story high up on Digg, and benefit greatly from such traffic.


More Global CIO Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Like I was saying, the old Digg interface was clunky and not exactly fast (it wasn't overly slow; I'd characterize it as adequate). But it worked.

The other day, a newly designed interface appeared without warning on Digg. The problem with it is that the story-input process has now gone from the way I described it above (i.e., somewhat, but not too, slow) to really, really slow.

Why? Possibly because some genius has decided that, after each entry screen, Digg should go swirling off into the wild Web yonder to check some parameters. Digg's looking to see whether a story already has been posted, and perhaps it's mining Digg for related content earlier on than it used to. But Digg did all these things before without getting in the user's face like it does now.

Here's a screen shot to show what the new interface looks like, and how it dawdles (click to see the sequence of 5 shots, which show you all the steps you have to wade through):



Digg's new story-input interface is fancier, and slower, than the original. (Click picture to enlarge, and to see the other 4 in this sequence.)

The one improvement is that Digg no longer fritzes out when you go too long on the description portion of the template. Previously, if you went one character over, it would chop that whole block back to empty. On the negative side, though, when you preview your submission, you no longer get to see whether you entered the link correctly, cause the roll-over now shows "digg.com/submit" for everything. So the Digg folks violated rule No. 1 of good design, which is, don't screw up what previously worked just fine.

Anyway, I find this whole thing really dispiriting, because I thought sites with garage-shop pedigrees such as Digg were immune from the corporate nonsense that winds up making many bigger sites so bloated in comparison.

Are the Digg folks suddenly getting delusions of grandeur amid the insane Web 2.0 valuations which are being tossed around these days? Did they all sit in a conference room and decide they have to plan out some really cool revision to bring them into the "adult" world? Hey, guys, go back to playing pool in the basement, or wherever it was you were doing before you decided to tart up your site with unnecessary slowness.

The only problem is, as shark-jumping as the new Digg is, I'm stuck. What am I going to do? Go to AOL News's Propeller? I think not. I like reddit, but it's not as tech-oriented. I guess I'll hold my noise and continue to Digg the site I used to really dig, but now just kind of like for old-time's sake.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links