Thanks for your thoughts. We're having a discussion on how to approach
this issue, and hopefully we'll have something for you early next
> I work with Discovery Channel as a writer, over various publications, and I
> have seen quite a few things get buried. In fact, a big part of that was
> anything that was considered "liberal." If you recall the whole Digg
> Patriots thing that went down, my digg account (jerryjamesstone) was one of
> the accounts that was targeted because I submit a lot of green news. Not
> just from Discovery but from many "trusted" sites.
> I consult for over 12 different publishers total and I have seen this
> behavior happen quite a bit. Now, I fully understand your concerns about
> spammers. I myself do not want to see the Digg front page taken over by
> spam. It seems logical, no, that by letting us know of a bury via the API is
> not anymore info than what they could get from the site themselves.
> I would think this wouldn't help them reverse engineer the algo because they
> would not have the bury counts. Or am I missing something?
> Thanks for your consideration!
> On Thu, Dec 9, 2010 at 4:13 PM, Will <wlar...@digg.com> wrote:
> > I can definitely see how this would be helpful, but the concern is
> > that it would be most helpful for spammers who are trying to reverse
> > engineer the spam detection algorithms. For legitimate publishers, it
> > is relatively uncommon for their stories to get buried off.
> > That said, let me have a discussion with the rest of the team here and
> > see if others feel I'm being too conservative.
> > Thanks,
> > Will
> > On Dec 9, 12:41 pm, Failed Pics <failep...@gmail.com> wrote:
> > > I agree with Jerry, adding status -> "buried" in getInfo API would be
> > > an great improvement.
> > > On Dec 10, 12:59 am, Jerry James Stone <m...@jerryjamesstone.com>
> > > wrote:
> > > > Hi Will
> > > > I understand what you are saying about the bury count but I am not
> > asking
> > > > for that sensitive data. I am asking for data which is, more or less,
> > > > currently front facing. At Digg.com, when a story receives whatever the
> > > > magic count of buries is...it is removed from the flow of Top News or
> > > > Upcoming. It would be nice to have a flag that let's us developers know
> > when
> > > > this has happened.
> > > > I don't need to know how many buries it received or what not. But if a
> > story
> > > > is pulled from the general flow and not exposed to Digg's visitors, why
> > > > can't the API reflect that too? Just as a publisher wants to know that
> > a
> > > > story has been submitted to Digg, they are going to want to know if
> > that
> > > > story is no longer in the mix. No?
> > > > Jerry
> > > > On Thu, Dec 9, 2010 at 11:47 AM, Will <wlar...@digg.com> wrote:
> > > > > Hi Jerry,
> > > > > Although we're asking users to bury low quality content, Digg.com
> > > > > doesn't expose the number of buries, and generally we're taking the
> > > > > approach that the API doesn't expose sensitive data which isn't
> > > > > already exposed on Digg.com. In that light, it's unfortunately not
> > > > > currently in our plans to expose bury data via the API.
> > > > > Thanks!
> > > > > Will
> > > > > On Dec 9, 8:20 am, Jerry James Stone <m...@jerryjamesstone.com>
> > wrote:
> > > > > > Hi again
> > > > > > So now that the bury functionality has been added back to the UI,
> > can we
> > > > > > please have a flag or something that tells us this info in the API.
> > This
> > > > > was
> > > > > > the biggest disconnect in version 1.0 of the API, IMHO.
> > > > > > The tool I am working on is really for publishers to better
> > understand
> > > > > where
> > > > > > their content places. And if the Digg community buries it, we want
> > to let
> > > > > > them know.
> > > > > > Thanks!
> > > > > > Jerry
> > > > > --
> > > > > You received this message because you are subscribed to the Google
> > Groups
> > > > > "Digg API" group.
> > > > > To post to this group, send email to email@example.com.
> > > > > To unsubscribe from this group, send email to
> > > > > firstname.lastname@example.org<diggapi%2Bunsubscribe@googlegroups.com >
> > <diggapi%2Bunsubscribe@googlegroups.com<diggapi%252Bunsubscribe@googlegroup s.com>>
> > > > > .
> > > > > For more options, visit this group at
> > > > >http://groups.google.com/group/diggapi?hl=en.
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Digg API" group.
> > To post to this group, send email to email@example.com.
> > To unsubscribe from this group, send email to
> > firstname.lastname@example.org<diggapi%2Bunsubscribe@googlegroups.com >
> > .
> > For more options, visit this group at