Kevin Rose promises fix for buggy new Digg

Updated happygeek 0 Tallied Votes 410 Views Share

The post on Twitter late last night simply said "changes coming to digg v4" but it was enough to get me excited, mainly because the person posting those five words was none other than Digg founder and head honcho Kevin Rose.

The launch of Digg version 4 , which as we reported here on DaniWeb was less of a minor tweak and more of a major move towards tackling the growing popularity of Twitter and Facebook, only happened a couple of days ago. But 48 hours is a long time on the Internet, and angry Digg users have been very vocal in making their largely negative opinions known. Not that it's the first time Digg users have vented spleens over changes, anyone recall the great Digg advertising debate?

Kevin Rose and the Digg team find themselves between a rock and hard place, needing to do something to reverse the monthly visitor downturn (from 30 million to 25 million per month during the last year) but at the same time not piss off those loyal Digg users who have stuck with them through good times and bad. And so it was 'that Tweet' appeared last night, promising changes will come to the new Digg just 48 hours after it was born. So what is the problem, and what is Kevin Rose going to do? Well, actually, the problem is plural.

In a missive entitled Rose admits that "not everyone is happy" with the new design, but insists that "the usage looks extremely good" with more people registering on a daily basis than before. However, Rose does take the opportunity to "address some of the common concerns" that have been aired regarding the new site look and feel.

In amongst the thrust and counter-thrust of complaints and justifications, are some interesting admissions of things that have gone very wrong: Rose admits that user favorites should not have been deleted "Our fault, we'll add these to your 'saved stories' section" and that timestamps being removed was a bug that he "hopes to have fixed soon" for example. Not forgetting the resetting of historical submission Digg counts and mangling of associated comment sections, which again Rose promises to fix.

Not too many bugs then? Well, actually, I've not finished yet: Rose also admits to bugs that have caused all usernames to be lower-case, that have stopped RSS feeds from working and broken all third-party tools. "Some of these fixes/features will take longer than others" Rose states, adding "we hope to have the bulk of these issues resolved soon". The top priority would appear to be to stabilize the new Digg site, then and only then will Rose and his team look at the user feedback and usage data and decide what, if anything, needs changing moving forward.

Those vocal and angry users will, I imagine, be hoping that changes are made to bring back the upcoming stories section, address the balance of power issue between mainstream outlets/power users and ordinary 'diggers', and getting the main story discussion back up in front of the friends comment feed.

Dani AI

Generated

Useful context and practical next steps for anyone hitting the same issues described above by (and noted in 's cheeky comment): large front-end rewrites commonly expose a mix of migration and integration problems. The problems you see are best treated in two streams: immediate user-side mitigation, and clear, prioritized bug reports for the engineers.

Typical technical causes (short):

  • Data migration or schema changes that fail to map older records to new fields (lost "favorites", missing timestamps, case changes in usernames).
  • URL or feed endpoint changes that break RSS and third-party clients.
  • API/authentication changes that stop external tools from working.
  • Client-side logic changes that reorder or hide comment threads.

What to do now (actionable):

  • Protect any content you care about: export or bookmark important links, take screenshots of comment threads, and keep a local copy of lists you use.
  • When reporting bugs, include reproducible steps and environment details. A concise template to paste into a report:
Summary: one-line description
Browser / OS / device: (e.g., Chrome 85 on Windows 10)
Account: @yourusername (if relevant)
Steps to reproduce: 1) Go to X 2) Click Y 3) See Z
Expected result:
Actual result:
Time(s) seen (with timezone):
Screenshots / HAR / console logs: attached
Any temporary workarounds tried:
  • How to capture useful logs: open DevTools (F12) -> Network -> check "Preserve log" -> reproduce -> right-click -> "Save all as HAR". Attach that file to the report.

Short-term workarounds:

  • Use an external feed reader or browser bookmarks until RSS is restored.
  • Check third-party clients for updates; many developers release quick fixes when APIs change.
  • Group multiple reports into a single, clear bug for high-impact regressions (saved data, account inconsistencies, or anything that risks permanent loss).

Community note: concrete, repeatable reports and HAR files move bugs up the priority list faster than general complaints. If you can, post one clear repro here referencing so the thread collects useful test cases.

happygeek 2,411 Most Valuable Poster Team Colleague Featured Poster

Looks like those changes are starting to come - just visited Digg and got this!

pcalior 0 Newbie Poster

this is exactly a clone of twitter.. but wheres the whale?

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.