First off, make a website defend mode that can be triggered to serve different content. Then, do the following: 1. Add a robots.txt, make it look like it's wordpress (Disallow: /wp-admin etc) 2. If any client requests /wp-admin, flag their IP ASN as bot. 3. If a client is a bot, send it a gzip bomb (100kB size, unpacked around 20GB), use Transfer-Encoding: gzip and Content-Encoding: gzip to also punish malicious web…
I would like to be your friend for 2 reasons. #1 is that you’re brilliantly devious. #2 is that I fervently wish to stay on your good side.
Ask HN: Website with 6^16 subpages and 80k+ daily bots
71–80 of 212 posts
Re: Ask HN: Website with 6^16 subpages and 80k+ daily bots
#72Contains downloadable PDF docs of googolplex written out in long form. There are a lot of PDFs, each with many pages.
Re: Ask HN: Website with 6^16 subpages and 80k+ daily bots
#73First off, make a website defend mode that can be triggered to serve different content. Then, do the following: 1. Add a robots.txt, make it look like it's wordpress (Disallow: /wp-admin etc) 2. If any client requests /wp-admin, flag their IP ASN as bot. 3. If a client is a bot, send it a gzip bomb (100kB size, unpacked around 20GB), use Transfer-Encoding: gzip and Content-Encoding: gzip to also punish malicious web…
Re: Ask HN: Website with 6^16 subpages and 80k+ daily bots
#74First off, make a website defend mode that can be triggered to serve different content. Then, do the following: 1. Add a robots.txt, make it look like it's wordpress (Disallow: /wp-admin etc) 2. If any client requests /wp-admin, flag their IP ASN as bot. 3. If a client is a bot, send it a gzip bomb (100kB size, unpacked around 20GB), use Transfer-Encoding: gzip and Content-Encoding: gzip to also punish malicious web…
Re: Ask HN: Website with 6^16 subpages and 80k+ daily bots
#75First off, make a website defend mode that can be triggered to serve different content. Then, do the following: 1. Add a robots.txt, make it look like it's wordpress (Disallow: /wp-admin etc) 2. If any client requests /wp-admin, flag their IP ASN as bot. 3. If a client is a bot, send it a gzip bomb (100kB size, unpacked around 20GB), use Transfer-Encoding: gzip and Content-Encoding: gzip to also punish malicious web…
Re: Ask HN: Website with 6^16 subpages and 80k+ daily bots
#76Earlier quoted context omitted.
Only someone poking about would ever hit that url on someone else's domain, so where's the downside? And "a lot" of false positives?? Recall, robots.txt is set to ignore this, so only malicious web scanners will hit it.
The downside is that you ban a whole ISP because of a single user misbehaving. Personally I sometimes do a quick request to /wp-admin to check if a site is WordPress, so I guess that has a nonzero chance of affecting me. And when I mirror a website I almost always ignore robots.txt (I'm not a robot and I do it for myself). And when I randomly open robots.txt and see a weird url I often visit it. And these are just my…
So that is a balance between a bad actor and even "stop it" blocks, and auto expire means transitory denial.
Re: Ask HN: Website with 6^16 subpages and 80k+ daily bots
#77First off, make a website defend mode that can be triggered to serve different content. Then, do the following: 1. Add a robots.txt, make it look like it's wordpress (Disallow: /wp-admin etc) 2. If any client requests /wp-admin, flag their IP ASN as bot. 3. If a client is a bot, send it a gzip bomb (100kB size, unpacked around 20GB), use Transfer-Encoding: gzip and Content-Encoding: gzip to also punish malicious web…
"If any client requests /wp-admin, flag their IP ASN as bot" You are going to hit a lot more false positives with this one than actual bots
add a captcha by limiting IP requests or return 429 to rate limit by IP. Using popular solutions like cloudflare could help reduce the load. Restrict by country. Alternatively, put in a login page which only solves the captcha and issues a session.
Re: Ask HN: Website with 6^16 subpages and 80k+ daily bots
#78First off, make a website defend mode that can be triggered to serve different content. Then, do the following: 1. Add a robots.txt, make it look like it's wordpress (Disallow: /wp-admin etc) 2. If any client requests /wp-admin, flag their IP ASN as bot. 3. If a client is a bot, send it a gzip bomb (100kB size, unpacked around 20GB), use Transfer-Encoding: gzip and Content-Encoding: gzip to also punish malicious web…
real pro, man, wow! :))
Re: Ask HN: Website with 6^16 subpages and 80k+ daily bots
#79Sell it to someone inexperienced who wants to pick up a high traffic website. Show the stats of visitors, monthly hits, etc. DO NOT MENTION BOTS. Easiest money you'll ever make. (Speaking from experience ;) )
Assuming you were the buyer. Did they also ran an add clicking scheme on it, to even further inflate their profit?
Re: Ask HN: Website with 6^16 subpages and 80k+ daily bots
#80Earlier quoted context omitted.
Not really. When numbers repeat, the value is the same. E.g 00 is the same as 00. So the possible outcomes is 6^16, but unique values per color channel is only 256 values. So unique colors are 256^3 = 16.7M colors.
Yes, each possible 6^16 outcome is it's own subpage... /000000 /000001 /000002 /000003 etc... Or am I missing something?
So how many 6-digit hexadecimal numbers from 0x000000 to 0xffffff? 0xffffff+1 = 16777216 = 16^6. 16 options for the first digit, times 16 options for the second digit, times 16 for the 3rd, times 16 for the 4th, times 16 for the 5th, times 16 for the 6th is 16^6. Or go to bytes: 3 bytes, each with 256 possible values is 256^3 = (16^2)^3 = 16^6. Or bits: 2^24 = (2^4)^6 = 16^6.
It's also pretty trivial to just count them. Run this in your browser console:
count = 0; for(i = 0x000000; i