<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Business Leaps &#187; digg</title>
	<atom:link href="http://businessleaps.com/tag/digg/feed/" rel="self" type="application/rss+xml" />
	<link>http://businessleaps.com</link>
	<description>taking business to the next level</description>
	<lastBuildDate>Sun, 18 Jan 2009 03:22:35 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Digg Dugg Its Own Grave</title>
		<link>http://businessleaps.com/2008/02/28/digg-dugg-its-own-grave/</link>
		<comments>http://businessleaps.com/2008/02/28/digg-dugg-its-own-grave/#comments</comments>
		<pubDate>Thu, 28 Feb 2008 12:07:41 +0000</pubDate>
		<dc:creator>Adam Doolittle</dc:creator>
				<category><![CDATA[Featured]]></category>
		<category><![CDATA[In the Break Room]]></category>
		<category><![CDATA[digg]]></category>

		<guid isPermaLink="false">http://businessleaps.com/2008/02/28/digg-dugg-its-own-grave/</guid>
		<description><![CDATA[
I’ve been banned from Digg. I used to love Digg, but I’ve done something to Digg it didn’t like. I’m now an “invalid user.” Digg you’ve dugg your own grave; you’re no longer run by users, but robotic editors. And It’s editing content and denying the existence of an editor that killed you. It’s also [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://businessleaps.com/wp-content/uploads/2008/02/digg-dugg-its-grave.gif" alt="digg-dugg-its-own-grave-image" /></p>
<p>I’ve been banned from Digg. I used to love Digg, but I’ve done something to Digg it didn’t like. I’m now an “invalid user.” Digg you’ve dugg your own grave; you’re no longer run by users, but robotic editors. And It’s editing content and denying the existence of an editor that killed you. It’s also the ease of dirty digging, like hurting your competition’s website that kill you.</p>
<p>Many of you have heard of the Digg Auto bury, it’s the editorial-robot killing hundreds of great stories every month. It’s the robot that kills most of forevergeek.com, johnchow.com, copyblogger.com’s stories — and now it killed my user name.</p>
<p>But don’t ask digg about autobury, it still believes “Digg surfaces the best stuff as voted on by our users. You won’t find editors at Digg — we’re here to provide a place where people can collectively determine the value of content.”</p>
<p>Yet, Kevin Rose, the founder of Digg, explains the autobury feature of digg, “When a single URL hits a threshold of reports, our standard procedure is to block that URL from submission.” If automatically blocking a URL from digg isn’t editing content, what is?</p>
<p>Stefan Juhl researched the idea of internal edited and found the “last referrer before the [bury] was crawl3.digg.internal.” It’s an internal autobury indeed.</p>
<p>“Mostly, landing on the Digg front page a couple times a month resulted only in a server-shaking stampede of worthless traffic. But mixed in with the basement-dwelling little boys who momentarily refrained from Playstationing with their Wiis long enough to tell me I sucked, I picked up new subscribers,” said Brian Clark from Copyblogger.com.</p>
<p>And now you can get even more subscribers and visitors by digging your competitor’s graves. It’s extremely easy to kill your competing site on digg, just follow these steps to get his or her domain on autobury. It’s called “dirty digging.”</p>
<h3>How to Digg Your Competitors Grave</h3>
<p><strong>1. Submit and Title Posts for Your Competition.</strong> And make the title standout, something like “Check this Post Out on Domain.com” or “This Was ReAlly Cool.”</p>
<p><strong>2. Create a Free Email Account Using The Domain Name.</strong> Go to Yahoo or Hotmail and create an email (yourcompetition@hotmail.com). Now have the domain’s RSS feed and digg every new post, again using spam titles. Keep submitting only the domain’s posts until you get the domain banned.</p>
<p><strong>3. Keep Creating New Accounts.</strong> Go to the library one day and create 15 or more new email accounts and digg accounts. Then submit posts only from your competitors domain.</p>
<p><strong>4. Now Bury Each Post.</strong> Use an account that hasn’t submitted the stories and bury each one. And if you want a ban even faster, get 15 or more of your friends on digg to bury the stories.</p>
<p><strong>5. Contact the Power Users.</strong> Again using a fake email, contact some power-users and ask them if they’re interested in getting paid to digg a list of stories. Be sure to list each post from your competitor’s site.</p>
<p>Along with how easy it is to use digg to do your dirty work, digg and all social media have reverted the trend back to individual blogs — where the blogger has complete control and can’t be banned. It’s this trend back to blogging that came from digg’s hypocrisy that killed it. Saying the users control the content seen on digg, then creating an autobury is hypocrisy.</p>
<p>As Lee Odden, a fellow blogger at toprankblog.com, explains, “The issue for me is when people try to submit a story they want to share with the digg community and get an error message ‘This domain name is banned from submissions’ it sends an inaccurate message. My complaint is not about being off of digg, its about someone else making that decision arbitrarily and digg support acting very much like DMOZ. And we all know where DMOZ ended up.”</p>
 <img src="http://businessleaps.com/wp-content/plugins/feed-statistics.php?view=1&post_id=27" width="1" height="1" style="display: none;" /><img src="http://businessleaps.com/?ak_action=api_record_view&id=27&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://businessleaps.com/2008/02/28/digg-dugg-its-own-grave/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>
