I'm emotionally aligned with you, but the dehumanisation is the default state (e.g. the able are standing and the wheelchair user is below eye level), and all accommodations are a result of society dedicating resources to moving the needle away from that.
It may not be sufficient, and we should criticise when it isn't sufficient, but we must in practical terms also accept tradeoffs in a scarcity economy. In the worst case, some of those tradeoffs accommodate one disability over another disability.
If the dean had a swanky office and the wheelchair kid must roll past the bins, then the school made the wrong choice. But if it's a ramp at the front or textbooks, then we must think a bit harder.
No. No luck here with any form of settings (I generally use uBlock origin in hard mode by default).
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). :-)
No idea, it should be under dev/lang where other lisps are, but Stefan Haubenthal is an accomplished software packager so perhaps there's a good reason.
On average about 100 (TCP) requests hit my home router per minute doing various probing and scanning. Lots of checking for the telnet port obviously. Sometimes you can see a swarm of entirely different IPs scanning the full port range (probing the ports one-by-one).
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.
The easiest way to deal with the usual suspects is to just block the entire countries network range(s). There really is no reason they should be connecting to your home router anyway, and you lose nothing from blocking them.
Sure their packets will still hit your router, but if they are dropped immediately at least you're not wasting a syn-ack on them.
> The easiest way to deal with the usual suspects is to just block the entire countries network range(s).
Keep in mind that this should be paired with an ASN blacklist - MaxMind also has an ASN mmdb for convenience - because IP address to country maps are almost entirely self-declared[0].
For example, Tencent (AS132203), which you almost certainly want to block, has ranges in 73 different countries per [1].
I, temporarly, banned some ip range.
I didn't find a source for pinpointing countries; though I am interested. Could you point me to some sources which, deterministically, resolve to some countries? To my knowledge you can not reliably identify countries by ip since this would be dependent on DNS servers. Though I am just a application programmer!
Your router doesn't care about their DNS settings. IP addresses are very easy to tie back to countries. The reason they say it's not reliable is because it's trivial to spoof the country, but even so, a lot of attackers don't even bother. It's sort of like the Nigerian prince scam calls: if you're wise enough to block Russia, you're not worth their time.
Your firewall vendor should supply you with country lists, just select the known bad ones and drop their traffic. If you have a consumer grade router, you will probably have to configure the blocklists manually.
> The reason they say it's not reliable is because it's trivial to spoof the country
ISPs sometimes do trade IPv4 blocks and countries to which it belongs do change occasionally. That can become a problem if you were like literally Netflix and someone few nation states over started an ISP.
Unless you're serving something, you should probably drop all incoming requests. If you are serving something, the US is a pretty big market to lock yourself out of.
I'm happy to unblock China from accessing my website, once China does something about the millions of daily hack attempts originating from that country.
I have ubiquity UniFi for this reason (amongst others). OpenWRT is a good choice as well. Most home router software is such junk, might as well leave the door open..
> The common advice now is to only use CSS that is supported in the last two major versions of each major browser.
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.
> 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)
Nope.
Safari only releases a major version once a year, so by only using features that are available in the last two major versions of each major browser, you're already waiting at least 2 years.
> I'd say for safety one should target the browsers of the last 4 years at least.
No.
Supporting browsers that old incentivises users not to update, which causes them to be insecure.
Better they know that something is broken so they have a greater incentive to update.
Goto (as in "Go to") and Goto (as in the romaji version of one of 後藤, 五藤, 五島, …) is simple two things that sound/look the same when written in ASCII w/o spaces. :)
where the first character means "behind" or "back" and the second character refers to wisteria vines.
(The first character is familiar to some of the martial arts practitioners, because it has an alternative pronunciation, "kō" instead of "go", which is used in the expression "kō-kutsu-shitsu", which is normally abbreviated to "kō-kutsu", and which means "with the back knee bent".)
The last name "Goto" in this case is actually read Gotou (ごとう), but romanization methods are their own flamewar. There's much less emphasis put on the "go" part than the "tou", so pronunciation doesn't actually sound anything like the English word "goto" at all.
Imagine the spanish word gato. Now elongate the "to", and change the ga to go, and you're close.
`ansiweather` needs like ~6.28 MiB (measured with `/usr/bin/time -l` on OS X), but it's a bash script that invokes cURL, so there's certainly various overheads there too.
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. :-)
On Linux you can bypass libc and use as little memory as you like. When you don't use libc and don't use dynamic loading there is no strict lower bound although you still start with a certain default stack size.