Slashdot should cache pages to prevent the Slashdot Effect!
Sure, it's a great idea, but it has a lot of implications. For
example, commercial sites rely on their banner ads to generate revenue.
If I cache one of their pages, this will mess with their statistics,
and mess with their banner ads. In other words, this will piss them
off.
Of course, most of the time, the commercial sites that actually have
income from banner ads easily withstand the Slashdot Effect. So
perhaps we could draw the line at sites that don't have ads. They
are, after all, much more likely to buckle under the pressure of all
those unexpected hits. But what happens if I cache the site, and they
update themselves? Once again, I'm transmitting data that I shouldn't
be, only this time my cache is out of date!
I could try asking permission, but do you want to wait 6 hours for a
cool breaking story while we wait for permission to link someone?
So the quick answer is: "Sure, caching would be neat." It would make
things a lot easier when servers go down, but it's a complicated issue
that would need to be thought through in great detail before being
implemented.
Answered by: CmdrTaco
Last Modified: 6/14/00
I have a suggestion for improving moderation
Please read the Comments & Moderation
section before emailing any of us with your suggestion. The vast
majority of suggestions I get are ideas that are already explained
there. Of the remaining suggestions, most are ideas that I probably
should put there. The thing that is typically forgotten is that the
moderation system is a complicated collection of checks and balances
designed to prevent abuse: almost every suggestion that winds up
in my inbox, however well intended, opens up a hole for abuse.
Answered by: CmdrTaco
Last Modified: 6/14/00