CA519705950 said:
If true, that's complete and utter fucking bullshit. In this case, Google should be blocked, as it has a little box into which users can type 'child porn'.
emigre said:
I actually downloaded something from MU a few hours ago.
I did five minutes ago. This thread was the first thing I saw after Todorov's Narrative Theory.
Google wouldn't be blocked as it isn't hosting anything. The sites that it could find would be what's blocked.
Anyway, megaupload isn't even blocked. The filter just makes it show the elevated number of requests screen. If you have a premium account, it'll work fine.
Far as I know the iwf filter works like this. Specific address is reported and blocked, in this case megaupload.com/badfile. It's actually blocked you cannot load the page, you'll get page not displayed. How ever for it to block that specific address, it has to go through the iwf proxy.
Now whether it's poorly implemented or it's just how it works, I'm not sure, but the way it works now is, any address on that domain, even if it isn't the blocked page, runs through the proxy. So megaupload simply sees loads of requests from the same ip ( the proxy) and gives you the error. Normally doing it this way doesn't cause any problems (like when they blocked a page on wiki, only that specific thing was not accessible, but the rest was), but it does cause problems for free users on sites like megaupload.
So it's not a specific block on megaupload, just a side effect of how the filter works, get a premium account and it'll still work.
