Some graphs:
This one shows the number of stories each user had on the front page (horizontal axis) and the number of friends that user had (vertical axis). So for example, there’s a user who had about 43 stories on the front page (of the first 1100). That user had about 210 friends).

Friends to Stories

This one shows the number of stories each user had and the number of fans that user has.

Fans to stories

Raw data:

I’ll be creating a few scripts that I’ve been thinking of doing sometime in the near future (hopefully).

Enjoy: Digg Top Ten Normalizer

I’m using the DOMNodeInserted event to see when any comments/replies are added to the comments of the currently viewed story. (It turns out that even though by default you only see the first x (50?) comments in digg, in the background it fetches the rest of the comments and inserts them into the DOM, hidden). So I figure if I see a reply to a comment and I haven’t received the data from the digg api of the number of ups/downs of that reply, I will fetch it using GM_xmlhttpRequest. Fine, should be simple enough.

But, turns out there is a problem with running GM_xmlhttpRequest inside a DOMNodeInserted event. You get the following error:

Error: Greasemonkey access violation: unsafeWindow cannot call GM_xmlhttpRequest.

Why does it consider it an unsafeWindow? I’m not sure. I’m not sure if it’s a firefox issue or a greasemonkey issue, but I have found a simple workaround. Just add the GM_xmlhttpRequest inside of a setTimeout:

Result: no error!
I’ve submitted a ticket to greasemonkey, but haven’t heard anything back. And since there is a simple workaround I don’t think it’s a high priority for anyone.

I’ll keep you all updated on any changes as I find out.

In the mean time, I’ve started a thread on it in the Digg API google group: http://groups.google.com/group/diggapi/browse_thread/thread/45b81c0ab610968b
And I’ve also sent a bug report.

Thanks for the patience!

I thought that maybe I could use it to plot the relationship of friends in a digg story. Works fine for stories with only a few diggs… not so well with any more than 30 or 40.
For the uninitiated, Digg gives members the ability to befriend other members. However, unlike facebook, myspace and the like, the other person doesn’t have to befriend you back. So, person A can have B as a friend, but not necessarily vice-versa.

So, I got a nice looking graph for a story with 30 people, but it was sort of boring. There was a small cluster of about 5 people who were friends with each other, but the rest were pretty much separate. So I tried a larger story, with 120 diggs. Not a good idea.
The result is a 1.5 mb file that doesn’t say anything at all.

For your amusement, I’ve uploaded it here. Click on the fuzziness below:

WARNING: 1.3MB

Install Script (Must have Greasemonkey installed on Firefox)

I created a greasemonkey script (FIREFOX ONLY, for now) to show the digg ups and digg downs on digg stories. Here’s a picture of what it looks like now:

For those who are interested, details are below. Those who aren’t can’t just go straight to downloading the script.

Some bugs that I am aware of:

• If you digg a comment up or down, the up and down don’t get updated. (Simple fix, I believe)
• Sometimes, the up and down don’t match the current rating. There is no fix to that. I’m retrieving the most up to date info from the API and sometimes either there is a delay with that or there is a delay with either the api (likely) or digg. This shouldn’t be a big problem, I’ve only noticed it once or twice while testing and it was only off by one.
• Doesn’t work with Opera. Will be fixed soon, for both of you.
• Under heavy load, the ups and downs may not get loaded. You can see if there was an API error in your javascript console, it will probably say error 500. Not sure what I can do about that. I could possibly make the API keep trying, but that’s just going to compound the problem on the server
• There is a delay, especially when loading large pages. Don’t know what I can do about that, but I’ll look into it

Features I want to add:

• Clicking on the number of digg downs or digg ups will down down or digg up the story.
• Ability to choose the design for how to display the ups/downs. (See previous post)
• Implementing any ideas you suggest.

Other random bits of information:

• Overhead: There is of course some overhead when using this. Essentially, for every comment you see, the script needs to retrieve that comment again from the api server. This is done asynchronously thanks to AJAX, so the page won’t load any slower than before (Unless you’re running on something like a 56k modem, in which case, welcome to the 21st century).
• Errors: Let me know if you run into any errors. They should be logged on the javascript console. (Firefox: Tools -> Error Console, should be under messages or errors depending on what the issue was).

Digg Rating Extender Greasemonkey Script

I’m planning on releasing the script shortly, I just have to work some small bugs out first. Keep on the lookout.

Also, I still haven’t received any designs for the digg comment statistics page, so if you are interested in that, there’s still time. Some people have already expressed interest, but I haven’t seen anything yet.