Why use squashfs when you can do the same OP did and serve a compressed version, so that the client is overwhelmed by both the uncompression and the DOM depth:
The thing with ISPs is the small guys are more likely to have to pay, and the smaller you are the more likely you are to pay more.
If you are a Tier 1 ISP, everyone is willing to pay you to carry their traffic and other Tier 1s just make peering agreements with you.
If you're johnscheapvps.com, you're likely to pay all your upstream ISPs for your traffic. If you're GCP or, say, digitalocean.com, everyone would love to be paying you to get faster access to all the sites hosted on your platform (and because paying you is probably going to be cheaper than their regular upstream)
There is much more Android phones, tablets, TVs, Linux routers and other gear sold every year than Intel-based PCs with ME, so the articles' claim may need narrowing to "OS used in PCs" and even that has a chance of being wrong, given how AMD is doing these years.
I also don't get these, but for another reason: why write a dotfiles-specific configuration management tool with templating, conditions and all of that when we already have proper SCMs like salt or ansible that perfectly scale down to a single user and a small number of configs, but are still orders of magnitude more powerful when you need it.
I will do a lot of work to avoid having to touch ansible and friends. Fortunately, I don't have to do a lot of work because I spent 10 minutes writing a 50 line Go program a decade ago that has done everything I've needed it to do in the interim (IIRC the only change I made to it was supporting Go modules back in ~2015).
At that point, I believe Mullvad (who is actually behind Mozilla VPN service) is more trustworthy than Mozilla themselves. And if that is true, why don't just use Mullvad directly?
My understanding if you given money to Mozilla who then give it to mullvad
All Mozilla know is the mullvad username. Mullvad don’t know the credit card details of the purchaser. To link a given vpn ip to a specific credit card would require compromising mullvad and Mozilla.
(Or of course the normal way of fingerprinting which doesn’t rely on IPs)
Now sure you can buy mullvad via cash, but that’s far more work. Using Mozilla as a reseller feels like one more step in the chain
You don't. I almost always use termux with virtual keyboard and it feels fine for doing something quick and on the go.
Modal UIs (like vim) work better than modifier- and functional keys-heavy though.
You can use any file browser that supports android's document api to browse termux's filesystem.
If you are using something like samsung oneui it can't do that, but you can install Anemo and use its shortcut to open android's default "Files" instead of samsung's
You probably should try to do it old analog style: just plug your microphones into each other’s PCs and set up soundcard's mixer to add mic input into the mix
Signal can pull a Durov and start hopping popular cloud hostings and CDNs, pushing latest server IPs via FCM. This worked for a year in Russia - they banned several large subnets of AWS and DigitalOcean, millions of IPs and smaller subnets, temporarily banned Google, but in the end still gave up after a year.
yes "<div>"|dd bs=1M count=10240 iflag=fullblock|gzip | pv > zipdiv.gz
Resulting file is about 15 mib long and uncompresses into a 10 gib monstrosity containing 1789569706 unclosed nested divs