4 ms·
https://42.zip https://42.zip served just that (after the 42.zip named on https://en.wikipedia.org/wiki/Zip_bomb https://en.wikipedia.org/wiki/Zip_bomb) until s
by ehPReth 3y ago
https://42.zip https://42.zip served just that (after the 42.zip named on https://en.wikipedia.org/wiki/Zip_bomb https://en.wikipedia.org/wiki/Zip_bomb) until some ****hole reported it to Google/etc for.... phishing? Kinda sad, lol.
One of the arguments I've seen is: 'what if your antivirus scans it' to which I think: if your antivirus blows up on a zip bomb in 2024, you need a new antivirus that isn't total garbage?
- geek_at 3y agoThis could be the result of a google indexing error. Strangeley enough my blog (the one linked in this hn post) itself was de-listed from google justa few weeks ago. The Blog is a static HTML page with no external dependencies and I didn't even update it in the time google thought there was phishing somewhere. The Webmastertools showed the error but didn't link to any specific site (it even said null). So i sent it in to re-evaluate and it was put back on google (without changing anything on the static files themselves). Very strange stuff