Neaveru

My page was on digg last week and managed to get both to the front page and in the top ten. It became the number one story for about an hour before it was removed from the top 10 (Stories are removed 12 hours after becoming popular).
Here is the bandwidth graph (I believe it takes the average every 5 minutes):

And, I’ve used awstats to create some (filtered) stats to show the digg traffic. This is traffic only to the digg stats page during the time that it was on the front page, or where the referrer is from that page.
Digg Traffic Statistics

Some interesting notes:
The story was submitted around 6PM on Sunday and got a few hits (18 at the far left of the graph)
It became one of the popular upcoming stories around 10:30PM
It hit the front page at around 11PM (The huge spike)
Interestingly enough, 8AM had a higher spike than 9AM (EST)
Right before 11AM is when the page was taken off the top 10, which is a shame since the California traffic didn’t get to see it.
I still got a decent amount of hits until around 11PM on sunday, when it was taken off the most popular in the last 24 hours.

I still get a modest number of hits, just not as often. But, considering that specific page has never been seen before it was posted on digg, it shows that digg traffic can at least bring some repeat traffic.
Oh, and google finally decided to list me. That was kind of them…

Other interesting stats (Os of Tuesday, around 4PM):
Total diggs: 2096
Blog posts from the blog section of digg: 7
Blog posts from blog section of digg that are obvious spam: 3 (And 3 of the other 4 seemed to just copy whatever was on the front page)
Del.icio.us bookmarks: 55

And of course, now with the google listing and the digg, I get the inevitable script kiddies hitting the page. Some of them are just ridiculous though. I mean, either they have 0 day exploits that happened to not work or they are using vulnerability from, I’m not exaggerating, 2003. I hope they don’t WinNuke my server. (OK in all seriousness, it’s probably just a worm from an already compromised server, but still)