set $redir_to_gz 1;<br></br>if ($host = gz.niko.lgbt) {<br></br> set $redir_to_gz 0;<br></br>}<br></br>if ($user_agent !~* (claudebot|ZoominfoBot|GPTBot|SeznamBot|DotBot|Amazonbot|DataForSeoBot|2ip) {<br></br> set $redir_to_gz 0;<br></br>}<br></br>if ($redir_to_gz) {<br></br> return 301 https://gz.niko.lgbt/;<br></br>}<br></br>
basically tosses all the AI bots i've seen into gz.niko.lgbt (click at own risk, decompresses 100GB file in memory :3) with a compression type of gzip so it has to be decompressed to see any "content" (there is none)
@notfire i just edited it with the two major setup things behind gz.niko.lgbt (don't forget the gunzip off if you host it yourself that way nginx doesn't blow its foot off if the client doesn't support gzip)
outside of those two it's just a completely normal nginx server block
@notfire depending on the HTTP client the other end uses the client might either decompress on the fly (not a single one i've tested does that) or download the entire body and then decompress (curl, firefox, and chromium do this)
it would work for the former but the latter would just eventually end up having a connection closed thanks to some other reason likely
@niko yeah i meant for either of them really, just serve infinite data till the connection gets broken to waste as much bandwidth and time as possible for companies' ai bots
@notfire i would think an OOM condition on a server thanks to uncontrolled gzip decompression would have slightly more negative impacts which honestly is half the point with this otherwise i'd do what you suggested yeah
@niko@ashten could also redirect to mstar.evilthings.de/cat/awawawa. Just responds with a permanent awawa stream that only ends once you cut the connection on your end
Add comment