Thursday, October 6

if you had seen this entry, then yes, the blogger.com and blogspot.com servers have finally been revived. as based on the site counters, the servers had decided to take a vacation on the white beaches of hawaii soon after 8am, which i hope is not caused by a surge in traffic caused by my very first submission to slashdot.org. here's the screenshot:



it's a small one, but prior to that there was exactly 99 visits and then no more. every blog could not be accessed. sigh. slashdot.org is famous for that. let's see this definition of Slashdot Effect:

Slashdot Effect n.

1. Also spelled "/. effect"; what is said to have happened when a website being virtually unreachable because too many people are hitting it after the site was mentioned in an interesting article on the popular Slashdot news service. The term is quite widely used by /. readers, including variants like "That site has been slashdotted again!"
2. In a perhaps inevitable generation, the term is being used to describe any similar effect from being listed on a popular site. This would better be described as a flash crowd.

then, we can also some hilarious personal experiences on this:

Langlitz wrote, "I don't want other innocent webmaster to undergo the same trauma I went through when my site was mentioned on Slashdot. Even though it was only a brief mention, my server crashed within minutes of the posting. The Pentium CPU overheated, and actually caught on fire. The system was a total loss. In addition, my ISP charged me $50.00 for the additional bandwidth the Slashdot Effect sucked up." (Anyway, this was in 1999.)

nice reads, but i don't think i did the thing. one blog and a mere 100 views couldn't have crashed the blogspot.com server, right? agreed.

footprint left at 10:43 AM | Permalink