Slashdot Mirror

← Back to Stories (view on slashdot.org)

Hacked Sites of the Future

Posted by CmdrTaco on from the amusing-stuff dept.

Innova sent us a hilarious page over at 2600.com which has proposals for replacement homepages for a few popular sites, should someone happen to crack them. The Victims are Microsoft, Amazon.com, the Whitehouse, and 2600 itself. Some of the funniest stuff I've seen in days.

4 of 55 comments (clear)

  1. Endorsement of site crackers and 2600. by Anonymous Coward · · Score: 2

    I'm very disappointed CmdrTaco publicly sort of endorse site crackers (or wannabes) and the 2600-underground.
    Thus, I will boycott slashdot.org for one day (wait, that's too hard, let's say for one hour :-).

  2. Endorsement of site crackers and 2600. by A+well+known+coward · · Score: 3

    I would normally agree with your statement, but it is not the case here. If you read the 2600 site, they state quite clearly:

    "These were submitted by people who like to be clever and witty but who don't really want to launch federal probes by being clever and witty. So they've gone ahead and modified some famous web sites without actually hacking them."

    Perfectly acceptable in my point of view.

    Later.

  3. Slashdotting. by BiGGO · · Score: 2

    So....
    The "almighty hackers" have been slashdotted.
    I thought they're smarted than that.

    I think the /. effect is becoming quite positive.
    even better, i suggest a "distibuted net" slashdot-daemon,
    It will check slashdot.org/effect and slashdot all the links from there automaticly.
    (that would be a good way to knock some NT sites quickly such as algore2000 and microsoft)



    ---

    --


    ---
    I'm going to live forever, or die in the attempt.
  4. /. effect. by richnut · · Score: 2

    You know it's not only /. that causes this sort of thing. I used to work at an ISP in Chicago, and we used to dread when a customer would call us and say "We're going to be cool site of the day tomorrow, is that a problem?" If the people would have ever given us more than 24 hours of notice we would never have had a problem, but generally it was at 5pm the day before, or 9am the day of. :-) (Hmm warning.. Something to consider, Rob?)

    #define ISP_WAR_STORY
    Mac people might remember when Bungie relased the first Marathon demo. Our core routers were pegged at %110 capacity and our UNIX servers were between 11 and 30 load average for about a day. Ah.. the good old days.
    #undef ISP_WAR_STORY

    -Rich