Digg Annoyances

So everyone's claiming Digg is going to overtake Slashdot, but I'm not so convinced... I've read it occationaly for the last couple months. Then the other day I noticed them promoting some new features, and upon clicking the link I was welcomed with a "You must upgrade Flash" notice as I keep seeing all over the web. The problem is that Adobe has still yet to release any version of Flash beyone version 7 for Linux users. So, basically Digg has made it clear to me that Linux/Unix/BSD users are pretty low on their priority list. I'm tired of being spit in the face of by all these sites, and I expected better from the so called tech site that is Digg.com.

Then today, strike 2 happens. I noticed an aricle talking about how AMD is considering open sourcing their ATI drivers and that there were no articles about it on Digg yet, so I made my first submission. Well, oddly the "diggs" came alot slower than I expected for such an important topic, and when I came back to check if it had gotten enough votes to show up on the front page I found that it had, BUT it had been marked as a duplicate by many users... some even felt the need to tell me in the comments, and then one of them put a link to the supposed post that I duplicated. Then I quickly saw that the article with much more diggs was posted over an hour after mine was, yet somehow they shot up and now I was being marked as a duplicate.

Sure, this is something pretty silly to get upset over, but it's also very disheartening to have this happen on my very first submission. Being the guy that I am, I quickly came up with a simple solution. Whenever someone marks an article as a duplicate they should also be required to provide the URL of the article that has been supposedly duplicated. Then a simple script can check the times they were posted and determine who the real dupe is. Then I guess they can even take it one step forward and place all the duplicate reports on the actual dupe instead of the real original. It sounds like a lot of trouble for something so silly, but it would have meant a lot to me if my first post wasn't treated so poorly by something that could be so easily corrected :(

I've submitted a bug report for both of these issues, but I'm not holding my breath that they'll actually do anything... so for now, I'll stick with Slashdot ;)

No comments: