Oh yeah totally. But while one could argue we are owed security, we are not owed updates. (And when we do, they’re offered to us via “buy another phone”, such is Capitalism).

FLACs

on a phone

in SD card

¿??? it’s not like you’re going to be able to autism at a -0.0002dB disparity on the trumpets channel with those audio chips, why not just store the files there as opus or MP3 for ~6x more capacity? (not to mention faster overall reads)

Security is not a state but a scale, and is gauged against everything else.

From the perspective of a privacy / security zealot, a smartphone is SOL as soon as they lave the factory, as not only not even OTA updates keep them safe (and you can argue that with some manufacturers such as Samsung, OTA does is the primary risk vector!) but they can eg.: ship with unfixable vulns at the hardware level that would lead to ditch the whole thing anyway.

So long as there isn’t something like a state-funded program for citizens to renew their phones every ~2 years for fully open ones, I’d not worry much. After all, the other option would be not using a phone because current ones are a PITA and just as vulnerable from the other end.

I can’t see any of the graphs. The show as a black box.

This despite disabling Canvas Blocker on the page for testing. According to my briwser, loading the resources from “cdn.jsdelivr.net” is blocked due to a CORS failure.

Aren there by any chance image dumps of the charts in any normal graphics image format? Or even jpeg-xl, for variety.

My primary phone belongs to my work.

So it’s not yours. Looks from here that’s the one issue you have to solve before everything else.

No one says you have to upgrade your phone OS to the latest Android. You can just keep using the Android (and/or Custom ROM) that works.

requests Google Static

requests Cloudflare

Nice try, fed.

Some of the best stuff in the world looks like it’s 20 years past a prime that isn’t, because they’re truly good eternal.

Yes.

Next up!

ICANN approves use of .awesome-selfhosted domain for your network

To be fair it’s 2024 and I’m still doing this, because adding an alternate location to install flatpaks in results in Flatseal not being able to detect those apps or edit those permissions. Just setting the default location as a symlink to where I want to magically fixes everything.

Yeah I’ve heard about punycode. Personally, I’m well against it because it puts down non-MURRICAN English domain names as second-class citizens on the internet. If I have a website about Copiapó, a perfectly legal town, there’s no good reason why the domain name should not be copiapó.cl rather than copiap-xcwhngoingohi4oleleiyho42yt4ptg4ht4.cl, making it look “suspect” and “malware-y”.

There were quite some complains back in the time about Firefox choosing not to “flag” internationalized names as potentially dangerous, and pretty much all those complaints that I know of likely came from English speakers who simply can’t understand other countries in the world even can have different alphabets.

And don’t get me started on TLS certificates in local networks…

I hate this and the fact that modern platforms seem to require TLS even if you’re serving localhost, so much.

I’ve taken to using .here (or .aqui, “here” in Español, much harder to match outside) as alternatives until something better comes up.

Ideally I’d use .aquí, correctly with the diacritic, but DNS doesn’t seem to support even the basics of Unicode in 2024.

64-bit IPv5

64-bit IP would be IPv8, not IPv5.

Not a big deal. We’re projected to run out of years by 2000 and then the world will end.

I felt dirty!

“Senpai, route me like one of your French ISPs”

128 bits basically gives one ip4 address space to each square meter of earth.

That sounds like terminal stage capitalism to me. Why would we want every tree in the Amazons to be cybergorized with its own IP? I don’t know Rick, 64 kbits bits ought to be enough for everybody, and I’m already risking it.

IPv6 is unfortunately not six bytes, no. For some weird, ass-backwards reason.

Boy do we like it!