<body><script type="text/javascript"> function setAttributeOnload(object, attribute, val) { if(window.addEventListener) { window.addEventListener('load', function(){ object[attribute] = val; }, false); } else { window.attachEvent('onload', function(){ object[attribute] = val; }); } } </script> <div id="navbar-iframe-container"></div> <script type="text/javascript" src="https://apis.google.com/js/plusone.js"></script> <script type="text/javascript"> gapi.load("gapi.iframes:gapi.iframes.style.bubble", function() { if (gapi.iframes && gapi.iframes.getContext) { gapi.iframes.getContext().openChild({ url: 'https://www.blogger.com/navbar.g?targetBlogID\07515927334\46blogName\75Digg+Blog\46publishMode\75PUBLISH_MODE_BLOGSPOT\46navbarType\75SILVER\46layoutType\75CLASSIC\46searchRoot\75http://diggtheblog.blogspot.com/search\46blogLocale\75en_US\46v\0752\46homepageUrl\75http://diggtheblog.blogspot.com/\46vt\75-8046688738114209239', where: document.getElementById("navbar-iframe-container"), id: "navbar-iframe" }); } }); </script>

digg blog

Digging Fraud

Recently it was brought to our attention that several users have created accounts to mass digg and promote stories. While these accounts appear to be valid, they have in certain instances been used for automated in-order (scripted) digging. This is a violation of our terms of service and the accounts have since been banned.

As you can imagine with over 250,000 registered users (and adding thousands more per week) we are constantly monitoring and looking for user SPAM/fraud. Internally, we have several methods for detecting fraud which results in DOZENS of banned accounts per day.

The banning of forevergeek.com: Aside from the dozens of user reports, several accounts were created to artificially inflate the digg count of their stories. When a single URL hits a threshold of reports, our standard procedure is to block that URL from submission (spam control). Again, mass fraud digging is in violation of our terms of service.

Missing stories: A common question we receive is the confusion surrounding missing stories. Once a story has received enough user reports it is automatically removed from the digg queue or homepage (depending on where the story is living at that time). The number of reports required varies depending on how many diggs the story has. This system is going to change in the near future. Shortly after the next major launch of digg (v3.1), reported stories will fall into a 'buried stories' bin. Users will have the ability to pick through this story bin and vote to have a story reinstated should they believe it was falsely reported. Expect to see this feature in the next few months.

On a personal note: It has been pointed out that I too have dugg these fraud stories. I digg stories I enjoy reading and currently track over 40 users within digg. If it's good content, I digg it.

Kevin