Meanwhile Australia is going to fore carriers to disconnect customers with devices that are not guaranteed to support emergency calling over volte. As there are still unsolved problems with detecting that, the providers fall back to only allowing devices they provided themselves.

And that is why I pay for my own domain. The service can change, but my domain is eternal (or near enough for my purposes)

I wonder how fast a turnaround would really be. Can all the checks be run on the launchpad and how likely are repairs that cannot be done there?

Some do detect open developer tools and nuke the whole page, though.

The VPN is really not much more than white labelled mullvad + the browser extension with separate VPN servers per container.

Archiving might be allowed even now, but not with a public download library.

Some datahoarder probably has an offline copy.

Currently, cloudstrike offers two methods for Linux: a kernel driver / module and a theoretically safer alternative using epbf (you could call that “kernel level scripting”). Ironically, they triggered a kernel bug using that second option. They did not test all kernels they listed as compatible or something like that.

… Spin … Spin … Spin …

… Remember that you turned off your VPN

… Turn it on

… CF: OK, only humans use VPN, no need to show the challenge

Which is only available for a limited set of devices, does not have root, locks the bootloader again and is probably professional enough to get banks to approve their signing key. For those reasons it is nor a viable solution for everyone.

I know of no open source app with live traffic routing. I think Magic Earth should be a closed source option to t least minimize google tracking.