You can update your phone with custom ROMs, but it won't update the closed source components of it(device drivers, bootloader, etc...). If a vulnerability is found in one of those components, it's unlikely that it will get parched

I guess he means that raspberry pi doesn't run a mainline kernel

Although it's true that you are increasing the attack surface when compared to locally stored OTP keys, in the context of OTPs, it doesn't matter. It still is doing it's job as the second factor of authentication. The password is something you know, and the OTP is something you have (your phone/SIM card).

I would argue it is much worse what 1Password and Bitwarden (and maybe others?) allows the users to do. Which is to have the both the password and the OTP generator inside the same vault. For all intents and purposes this becomes a single factor as both are now something you know (the password to your vault).

Am I naïve for thinking that manufacturers stopping support for devices, then claiming it affects your safety, is just to sell more phones?

Yes you are.

Vulnerabilities are constantly being found in the software stack used by Android, if you are running vulnerable software you're increasing the likelihood of some malicious app (or website, file, etc...) taking advantage of the vulnerability. The consequences of vulnerability vary from being able to fingerprint your device when it's not supposed, to escalateling privileges to root or even kernel mode. Although the later are significantly rarer.

and had zero security issues in a dozen years

That you know of... If the vulnerability is successfully exploited, the likelihood of you noticing are close to zero.

You could always flash a custom ROM to install the latest security patches, but you would still be missing the security updates for all the closed source components (such as the bootloader, device drivers, etc...). Not to mention all the security implications (good or bad) that comes with installing custom ROMs.

What kind of "control" do you mean? Your posts/comments get replicated across all the other instances. You can't really "guarantee" a delete, since the other instances might just ignore your request for delete.

I think those kind of vulnerabilities are pretty rare, though.

Not really... If you go read the security bulletin from google, you will see every month that there are a couple of issues fixed on closed source components https://source.android.com/docs/security/bulletin/2023-07-01

Also vulnerabilities related to kernel code, I highly doubt most ROM "developers" are actually backporting security fixes for that specific device's kernel branch/source.

I gotta admit, it's kinda funny how Rozenmyne perceived Ferdinand's Last Will as, "I MUST GO SAVE HIM," while the letter he sent through Justus was basically the opposite, "DON'T DO ANYTHING, YOU FOOL".

I wonder in what bizarre way, Rozemyne will extract the knowledge from Ferdinand. (I guess by printing some books)

My hypothesis is that Ferdinand was already planning to transfer/write his 30-40% knowledge of the G-book onto the 300 pages of "maximum quality fey paper" that he request from Rozemyne. Maybe he is already expecting to be executed by either the Royal famaly or Georgine/Detlinde and wants to preserve this knowledge somehow.

I'm probably obsessing over nothing, but the illustration showing Tuuli's reaction when her sister said "Tuuli... No matter what happens, I will protect you." was so good! This will probably sound pretty stupid, only now that we had this illustration did I realise how much Rozemyne grew, I was quite shocked.

The latest pixel devices (since 6 I think?) already provide accees to a /dev/kvm device, so maybe you could even run a normal Ubuntu server VM on your phone for hosting these services.

Unfortunately yes

Considering how big and relevant YouTube is, I don't see it getting replaced by PeerTubr. The alternative at the moment are apps like ViewTube which is a custom front-end for YouTube that removes all the ads and tracking

I ran GrapheneOS on a pixel 5 but ultimately went back to stock.

GrapheneOS was considerably slower on my phone. Apps took a bit longer to loader, but the worst was installing APKs, it takes so much longer compared to stock. Some apps (e.g. revolut) took more than 5 minutes to install, it was crazy.

In Europe I would say debit cards are way more common than credit cards. It's very rare to see someone paying with a credit card.

Made my own for myself and some friends. We couldn't be bothered creating account on the larger instances and have power tripping admins de-federating instances over trivial issues.

I guess that noble education is finally paying off, sort of... The only other noble one we know that wants to take another duchy is Georgine 🙃

I’d know if someone had any access to my phone

This is really a bold claim. How or why makes you so sure of that?

If the attacker/app manages to get some application running in the background as root, how would you know that they had access to your phone?

I think bitwarden fills all of your requirements.

GrapheneOS uses exec spawning by default, but it’s pretty trivial to disable and it does speed things up (at a slight cost to security).

Even with that option disabled the slow down was significant enough. Maybe the mid-range chip used in the Pixel 5 wasn't helping, but still... Overall the phone felt significantly quicker when switching back to stock.

I think using AOT rather than JIT compiling might be the cause of the slow installs, but I’m not sure (and I’ve not really noticed a problem myself).

That's it, I remember reading in their forums one of the mods(or devs?) mentioning this.

The code is still accessible, you just can't use the code search function in the web, which normal git doesn't have anyway.