Interestingly Perl comes in second, even I use it rarely (aka not at all) these days. But that's a slightly off-topic side note. :)

I like it's there as a choice for us who prefer the old-timey Audacity for some quick sample editing.

Of course, those peers where you ghost leech of then would correctly report the upload they generate (making THEM look suspicious of cheating by "over-reporting" upload.) It's impossible for any tracker staff to properly detect and attribute proper cheating in such cases, unless they can detect a pattern. The tracker staff objectively can only catch people that do really stupid things.

That's just the way BitTorrent and private tracker economics work. A "private" tracker is more like a social contract between its users to do the honourable thing, but you'll always have some idiots that do not get that, of course.

Humans of all kinds can breed and make new humans easily. Same for dogs... easily can breed with each other and increase diversity. So in both cases same species. But humans and chimpanzees? Probably not (albeit there are rumours? :) ), so different species.

It always loads the 'Just a quick check -- We’re checking your connection to prevent automated abuse' page. Depending on my settings I may or may not load the actual Cloudflare checkbox.

And at that point I just don't want to bother with that site anymore really. Obviously I must be some 11th world country on some random sanctioned list (aka Germany). :-)

(You still could get poked from the other users' hosts behind the ISP's NAT, of course.)

(still different from JPEG's method, of course)

You'll see a lot of deepfield, censys-scanner, visionheight.com, shadowserver.io, etc., but also the usual suspects of Chinese or Russian IPs.

With OpenWRT I use something like this: `tcpdump -i pppoe-wan 'inbound and tcp[tcpflags] & (tcp-syn|tcp-ack) == tcp-syn'`, or alternatively `tcpdump -i pppoe-wan 'inbound and tcp[tcpflags] & (tcp-syn|tcp-ack) == tcp-syn and not port 44000'`, if we have some torrent client running (e.g. here at port 44000) which would mess up the result. I'm not sure it's the best way to handle this, but it's definitely enlightening what bounces off on the router.

Browsers seem to release a major new version like every 2 weeks now. So this statement does no longer hold true. You'll have a lot of users with broken results, if you follow that advise (everyone who uses a ESR or is otherwise limited with updates and behind a month)

I'd say for safety one should target the browsers of the last 4 years at least. You easily can write new CSS —or Javascript— and then use a conversion during deployment to target the lower standards. That's more important for Javascript than for CSS though. If only half of the sites would deploy with `babel` and with some compatibility in mind 80% less of the web would be broken for users with older browsers.

One probably could get this down way below ~1 MiB with a properly tuned straight executable written in C (best not to use any of the "modern" stuff like Rust and Go, their default binary sizes for outputting "Hello, world!\n" are already extreme :-) )

By default anything needs at least 532480 bytes RSS on OSX (I tested it with the most minimal C hello world), so that's a threshold one probably can't beat on OS X at least. We probably could kill that value on Amiga OS with the exact same functionality. :-)