I have used digg on and off for the last few years. During this tine, digg has in some way contributed to the traffic on asifism.com too, but my latest attempts to use it have been anything but successful.
As you may already know, digg has redone the UI and changed the way some things work, but the basic principle is the same (sharing content for those of you who are wondering). Now, first of all, going live with an extremely buggy interface on a website that’s dealing with 25 million unique visitors a month is just not wise, so I can’t for the life of me figure out why they would do that.
Then, digg has fallen victim to the same fallacy that so many other web applications do: the excessive use of AJAX. Seriously, I do not want twitter type error messages that come down from the top of the screen. I was, and I am sure others were too, perfectly okay with the application digging through a submission and always working, as opposed to saying it can’t get content from the URL.
Let’s put it this way: I’ve tried to submit 20 articles to digg over the last couple of days and on only one occasion was I able to post something. Why do people insist on using AJAX where it is not required?
People at Digg, the whole point is to improve the user experience, not to destroy it.
Continue Reading
