Why did you write diggstats?
Diggstats was born out of experimenting with the Digg API. Not only the data it returns, but the differences in the data it returns at disparate times.
What is diggstats written in?
Diggstats (and it’s underlying framework, which I call diggwatcher) are a set of php 5 cli scripts which poll, record and compare polled digg data over time.
What’s so different about diggstats?
Digg doesn’t expose the number of buried stories. For that reason, you’ll find few — if any — digg analysis tools which report the number of buried stories. Buried stories simply disappear from digg, never to be seen again.
Further, finding buried stories is almost impossible if you don’t know exactly what you’re looking for. You can search for stories, and note that a story you saw before doesn’t appear; Then check the tickbox in the search form which says “Include buried stories” and search again, noting the story exists in one search, but doesn’t exist in the other. This is a cumbersome process, and doesn’t render the types of data I was looking for, namely, “What kinds of stories that aren’t spam get buried and why?
