<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Upcoming Q&amp;A With Digg</title>
	<atom:link href="http://www.devlounge.net/general/upcoming-qa-with-digg/feed" rel="self" type="application/rss+xml" />
	<link>http://www.devlounge.net/general/upcoming-qa-with-digg</link>
	<description>Design, Develop, and Grow</description>
	<lastBuildDate>Wed, 08 Feb 2012 09:03:06 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Connor Wilson</title>
		<link>http://www.devlounge.net/general/upcoming-qa-with-digg/comment-page-1#comment-22650</link>
		<dc:creator>Connor Wilson</dc:creator>
		<pubDate>Fri, 16 Feb 2007 21:07:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.devlounge.net/sidenotes/upcoming-qa-with-digg#comment-22650</guid>
		<description>Also forgot: What&#039;s it like knowing that everything you do front-end wise is going to have both positive and negative feedback from the hardcore users? Do you take a lot of the feature and design suggestions to heart?</description>
		<content:encoded><![CDATA[<p>Also forgot: What&#8217;s it like knowing that everything you do front-end wise is going to have both positive and negative feedback from the hardcore users? Do you take a lot of the feature and design suggestions to heart?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Connor Wilson</title>
		<link>http://www.devlounge.net/general/upcoming-qa-with-digg/comment-page-1#comment-22648</link>
		<dc:creator>Connor Wilson</dc:creator>
		<pubDate>Fri, 16 Feb 2007 21:05:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.devlounge.net/sidenotes/upcoming-qa-with-digg#comment-22648</guid>
		<description>How likely is it that you will be going strong and still run by the same people in the next 5 - 10 years? Is selling to another company something that you see in the near future?</description>
		<content:encoded><![CDATA[<p>How likely is it that you will be going strong and still run by the same people in the next 5 &#8211; 10 years? Is selling to another company something that you see in the near future?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Devlounge &#124; Friday Focus #18</title>
		<link>http://www.devlounge.net/general/upcoming-qa-with-digg/comment-page-1#comment-22523</link>
		<dc:creator>Devlounge &#124; Friday Focus #18</dc:creator>
		<pubDate>Fri, 16 Feb 2007 06:39:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.devlounge.net/sidenotes/upcoming-qa-with-digg#comment-22523</guid>
		<description>[...] we need your questions for our upcoming interview with Digg! Right now we don&#8217;t even have enough submissions to formulate the interview. We&#8217;d [...]</description>
		<content:encoded><![CDATA[<p>[...] we need your questions for our upcoming interview with Digg! Right now we don&#8217;t even have enough submissions to formulate the interview. We&#8217;d [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: aj</title>
		<link>http://www.devlounge.net/general/upcoming-qa-with-digg/comment-page-1#comment-22124</link>
		<dc:creator>aj</dc:creator>
		<pubDate>Tue, 13 Feb 2007 21:02:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.devlounge.net/sidenotes/upcoming-qa-with-digg#comment-22124</guid>
		<description>@all - We&#039;ll be looking at all possible questions, but please try to formulate them with as much information and examples as possible (like Clint did). This makes the process of picking the final questions at the end of the week easier, and gives the Digg crew more to work with.</description>
		<content:encoded><![CDATA[<p>@all &#8211; We&#8217;ll be looking at all possible questions, but please try to formulate them with as much information and examples as possible (like Clint did). This makes the process of picking the final questions at the end of the week easier, and gives the Digg crew more to work with.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Clint</title>
		<link>http://www.devlounge.net/general/upcoming-qa-with-digg/comment-page-1#comment-22084</link>
		<dc:creator>Clint</dc:creator>
		<pubDate>Tue, 13 Feb 2007 16:10:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.devlounge.net/sidenotes/upcoming-qa-with-digg#comment-22084</guid>
		<description>Jamie, 

#1a. The newest updates have locked down resubmissions so tightly that you *can not* resubmit the site.  If the URL matches, it simply does not allow you to resubmit it, it just points you to the article that someone else submitted and you&#039;re done, no chance to resubmit.  People can effectively lock out your content with poor titles and description.  The only way to get around this is to be purposefully subversive and append URL parameters to trick the URL checking system.

As for my position with Digg, I am probably the furthest thing from an outside.  I have been a user and reader for well over a year and I am probably one of the biggest contributors and active participants in the site.

#2.  Friends reccomendation aren&#039;t what Im talking about.  Digg penalises a story if the same group of people consistently digg together.  Prolific submitters have groupies who trail behind them digging everything they submit.  This effectively penalises all their submissions.  When these prolific submitters take to sitting around and submitting all the content your site produces, all your stories are disadvantaged from the get-go, out of no fault of your own.</description>
		<content:encoded><![CDATA[<p>Jamie, </p>
<p>#1a. The newest updates have locked down resubmissions so tightly that you *can not* resubmit the site.  If the URL matches, it simply does not allow you to resubmit it, it just points you to the article that someone else submitted and you&#8217;re done, no chance to resubmit.  People can effectively lock out your content with poor titles and description.  The only way to get around this is to be purposefully subversive and append URL parameters to trick the URL checking system.</p>
<p>As for my position with Digg, I am probably the furthest thing from an outside.  I have been a user and reader for well over a year and I am probably one of the biggest contributors and active participants in the site.</p>
<p>#2.  Friends reccomendation aren&#8217;t what Im talking about.  Digg penalises a story if the same group of people consistently digg together.  Prolific submitters have groupies who trail behind them digging everything they submit.  This effectively penalises all their submissions.  When these prolific submitters take to sitting around and submitting all the content your site produces, all your stories are disadvantaged from the get-go, out of no fault of your own.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jamie Huskisson</title>
		<link>http://www.devlounge.net/general/upcoming-qa-with-digg/comment-page-1#comment-22066</link>
		<dc:creator>Jamie Huskisson</dc:creator>
		<pubDate>Tue, 13 Feb 2007 12:49:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.devlounge.net/sidenotes/upcoming-qa-with-digg#comment-22066</guid>
		<description>Client&#039;s questions sound very negative and from an outsiders view, rather than someone who uses the site.

#1a  - re-submit the darn article
#1b - they aren&#039;t technorari they are a social news site, though newsvine do select import streams from newscientist etc. I can&#039;t see digg going the same way as it&#039;s about what the user&#039;s like.
#2 - &#039;baby step&#039;? They&#039;ve added a friends recommendation tool too - more than a baby step.

I&#039;d ask about the Digg API and when they are bringing it to the table, how it could be used (examples). Where they see Digg five years from now, what&#039;s their office environment like - laid back, strict etc. What they think sets them apart from Newsvine and the like - stuff that people don&#039;t ask.

It&#039;s always better to see an interview that isn&#039;t just like every other interview asking the same questions, so hopefully that&#039;s what you&#039;ll be doing AJ ;)</description>
		<content:encoded><![CDATA[<p>Client&#8217;s questions sound very negative and from an outsiders view, rather than someone who uses the site.</p>
<p>#1a  &#8211; re-submit the darn article<br />
#1b &#8211; they aren&#8217;t technorari they are a social news site, though newsvine do select import streams from newscientist etc. I can&#8217;t see digg going the same way as it&#8217;s about what the user&#8217;s like.<br />
#2 &#8211; &#8216;baby step&#8217;? They&#8217;ve added a friends recommendation tool too &#8211; more than a baby step.</p>
<p>I&#8217;d ask about the Digg API and when they are bringing it to the table, how it could be used (examples). Where they see Digg five years from now, what&#8217;s their office environment like &#8211; laid back, strict etc. What they think sets them apart from Newsvine and the like &#8211; stuff that people don&#8217;t ask.</p>
<p>It&#8217;s always better to see an interview that isn&#8217;t just like every other interview asking the same questions, so hopefully that&#8217;s what you&#8217;ll be doing AJ <img src='http://www.devlounge.net/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Poe</title>
		<link>http://www.devlounge.net/general/upcoming-qa-with-digg/comment-page-1#comment-21972</link>
		<dc:creator>Poe</dc:creator>
		<pubDate>Tue, 13 Feb 2007 05:54:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.devlounge.net/sidenotes/upcoming-qa-with-digg#comment-21972</guid>
		<description>International plans?</description>
		<content:encoded><![CDATA[<p>International plans?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Clint</title>
		<link>http://www.devlounge.net/general/upcoming-qa-with-digg/comment-page-1#comment-21957</link>
		<dc:creator>Clint</dc:creator>
		<pubDate>Tue, 13 Feb 2007 04:03:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.devlounge.net/sidenotes/upcoming-qa-with-digg#comment-21957</guid>
		<description>#1a.  If a user submits your content and gives it a horrible title and description, you&#039;re currently out of luck.  With the most recent round of updates it is now impossible to relist the content with a better title and description as it redirects you to the improper listing. The only way &quot;around&quot; this is to purposefully trick the URL checker by suffixing the URL with fake parameters. How is this fair?  Malicious users could theoretically submit content with nearly blank descriptions and effectively blacklist your site out of digg.  How will you counter this shortcoming and how can site owners &quot;fight back&quot; against poor listers?  

#1b. Are there any plans for allowing users to register as &quot;owners&quot;  of a particular URL (similar to how a user can register as the owner of a blog at technorati) and to allow them to &quot;adjust&quot; poorly chosen (or somethime blatantly false) titles and descriptions that link to their content?

#2. There are many &quot;top diggers&quot; who submit a lot of content in general and try to submit a every single bit of content published from a small set of very popular sites in hopes of nailing a few big ones.  These extremely popular users have huge friends lists who will dutifully digg anything they submit.  According to some of the things I&#039;ve read recently, this sort of behaviour is now penalized.  This dings sites for whom these types of users consistently list their content on Digg, causing them to have to fight harder for recognition out of no fault of their own.  I know you&#039;ve taken a baby step toward this by removing the &quot;Top Digg Users&quot; list but it still prevalent and widespread.  How do you plan to address this shortcoming?</description>
		<content:encoded><![CDATA[<p>#1a.  If a user submits your content and gives it a horrible title and description, you&#8217;re currently out of luck.  With the most recent round of updates it is now impossible to relist the content with a better title and description as it redirects you to the improper listing. The only way &#8220;around&#8221; this is to purposefully trick the URL checker by suffixing the URL with fake parameters. How is this fair?  Malicious users could theoretically submit content with nearly blank descriptions and effectively blacklist your site out of digg.  How will you counter this shortcoming and how can site owners &#8220;fight back&#8221; against poor listers?  </p>
<p>#1b. Are there any plans for allowing users to register as &#8220;owners&#8221;  of a particular URL (similar to how a user can register as the owner of a blog at technorati) and to allow them to &#8220;adjust&#8221; poorly chosen (or somethime blatantly false) titles and descriptions that link to their content?</p>
<p>#2. There are many &#8220;top diggers&#8221; who submit a lot of content in general and try to submit a every single bit of content published from a small set of very popular sites in hopes of nailing a few big ones.  These extremely popular users have huge friends lists who will dutifully digg anything they submit.  According to some of the things I&#8217;ve read recently, this sort of behaviour is now penalized.  This dings sites for whom these types of users consistently list their content on Digg, causing them to have to fight harder for recognition out of no fault of their own.  I know you&#8217;ve taken a baby step toward this by removing the &#8220;Top Digg Users&#8221; list but it still prevalent and widespread.  How do you plan to address this shortcoming?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: OnTheTech</title>
		<link>http://www.devlounge.net/general/upcoming-qa-with-digg/comment-page-1#comment-21911</link>
		<dc:creator>OnTheTech</dc:creator>
		<pubDate>Mon, 12 Feb 2007 21:29:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.devlounge.net/sidenotes/upcoming-qa-with-digg#comment-21911</guid>
		<description>When will the Digg API be available?</description>
		<content:encoded><![CDATA[<p>When will the Digg API be available?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

