RIP Megaupload

But the so-called "new address" looks good on the surface. Too bad it's a fake.

I'm sorry, but I can't help but read your posts in Domon's voice. </offtopic>

Seriously though, there's very little chance that megaupload.bz or whatever the "new" IP address of MU is is anything but something like a honeypot or a D Do S trap.

edited 19th Jan '12 9:46:46 PM by DemonSharkKisame

Being caught intentionally participating could net 10 years in prison...

The distinction is rather important, and rather ingenious of Anon. It is rather hard to prove intent for actions that are bypassing the "fire" confirm button...

@Swish: That, plus Anon doesn't lose anything if some innocent bystanders are, by some dark miracle, arrested. It becomes yet another injustice that stirs up hate for the government.

I'm not sure "I didn't know I was doing it!" holds up in the court of law.

Nor can you prove it.

edited 19th Jan '12 9:50:24 PM by Thorn14

@Thorn: It does, actually, hold up. People are not responsible for the actions of a browser hijack. Except for a very few specific crimes, the intent to commit a crime is required before there is a crime.

If the law specifies intent, in the USA, it does. The government has to prove intent...

Granted a jury may not buy such a defense, but it is rather hard for the government to prove intent for something like this. Not unless said computer was running the program for more than 8 or so hours...

^^^Proving that you didn't commit a crime, in US law, is never necessary. Demonstrating that it's not impossible that you didn't do it is all that you have to do for a "not guilty" verdict.

edited 19th Jan '12 9:53:09 PM by INUH

Still an unnecessary and expensive hassle.

It is kinda evil and unethical, but ingenious nevertheless. That way is pretty much impossible to rightfully imprison them.

There are several blog posts and news articles warning people.

I clicked it but my browser displayed a broken link screen, so I'm not sure it "worked" for me.

Also, it has 12K Facebook likes, if that's legit, and several people, both intentionally and unintentionally, are tweeting over it.

edited 19th Jan '12 10:58:28 PM by JuiceBoxHero

I was actually using Megaupload for legit filesharing/hosting... At least I have those files with me.

It looks like the reasons are legitimate, but shutting down the entire site is kind of harsh with bad repercussions. What about lifetime subscription users?

And it's bad timing too. First the British boy extradition issue, now this. US is making itself look like the dictator of Internet. All this ties into the unpopularity of SOPA/PIPA.

They'll be back (likely in another country, such as the Bahamas). Just like The Pirate Bay.

edited 20th Jan '12 12:36:15 AM by Buscemi

As far as I knew, MU always took all IP infrigment notices seriosuly. Only reason why I can think that there were that stuff is that the sheer number uploaded to their serves, that they can't police it themselves effectly.

Still, that doesn't mean their intent was to host pirated stuff.

@ abstractematics:

I can't say all this is going to help the Iran situation, amongst other problems.

From discussion on another site, apparently MU failed to comply with 36 DMCA takedowns:

It sad that megaupload is down but this sentence just cracked me up

From Wikipedia:

Well, now we know what is and isn't a rumor.

What if you visited the site for five seconds? Would it still trigger the DDoS Attack? I don't remember anything wrong when I visited the site.

edited 20th Jan '12 5:52:23 AM by Psyga315

Apparently it's a javascript that keeps making the same web request over and over, so yes it would trigger it.

This is very weird... I probably would have noticed something if it did ping the same site over and over.

Yet all I saw was the Megaupload screen. That's it.

If you are running No Script and ad blocker software I dont think it would trigger it.

Oh, okay then. That's a relief.

Wasn't running either of those things, but the site didn't load, so I just closed it after two seconds.

That's because of the 500 Internal Error.