Containers are the best, so probably

I currently donate to Frigate, but I definitely should donate more. Especially to KDE…

My bank apps work on Graphene with the exploit protection compatibility mode enabled, even the ones that require Play Integreity API.

It should be noted that while you can do this, it can increase your attack surface, defeating a lot of the point of Graphene. Before I started using Graphene, I was a huge fan of rooting and getting full control of my device, so I definitely understand the appeal. But I don’t think I would root Graphene myself, automated or otherwise.

Any Austin is great

Depends on if it’s a soft brick or a hard brick. Does it bootloop? Or just not turn on at all? Can you get into recovery?

Downvote me all you want

Ok

Fun fact, back in 2018 I emailed them asking if someone would take over once they were not able to have that responsibility, and if so, who. They replied the next day, and just said (copy and pasted from that email):

Yes, it will be.  You would not know them.

theguyintheglass.com (about the poem) was last updated on 1998-10-03 and created on 1997-12-25 according to the footer.

It does, I think I’m a bit confused here. I think the apks may be signed with the original key from the previous repo, but that key doesn’t necessarily have to line up with what’s in the GitHub repo since a lot of the repo tasks were removed or changed. I’ll edit my post, but this kind of highlights how messy this handover was, and how confusing it is to users (myself included).

This isn’t something you’d really want to mess with, since typically it has full filesystem access.

The new repo has two releases in it now. These releases are not signed with the original key as far as I can tell. Further, GitHub is silently redirecting to the new repo, even in Obtainium, meaning it’s possible that if you had this previously installed via Obtainium and updated now, you may have unsigned apks installed that may or may not contain the changes in the repo.

This is a mess. I deleted the repo from Obtainium (luckily I don’t auto install updates) and will wait to see what happens over the next few months. Might just save my notes in a network share instead of using syncthing from my phone. Idk, notes are all that I was using it for.

Watch for spicy pillows… they’ll light your stuff on fire.

Firewatch.

They make countertop dishwashers that connect to your sink, still better than washing by hand imo

I loved Firewatch’s art style. And story. It was a masterpiece.

Does running termux all of the time affect battery much?

For real. I’m probably gunna swap over to something else, this is pretty sus.

Well, yes, but that is not exclusive to Pixels, and in fact, most phones (other than the latest iPhones) are more vulnerable. Pixels, especially the latest devices, have the best hardware security features of any Android phone (unfortunately). You’re focused on Pixel, but that’s only because of the recent leaks which specifically focused on Pixel because of their breaching difficulty. Here’s the full matrix from last year (which hasn’t leaked as recently):

https://discuss.grapheneos.org/d/14344-cellebrite-premium-july-2024-documentation

GrapheneOS, even now, is not vulnerable for several reasons, most of which tie into the hardware features of the Pixel. There’s a reason Graphene only works on Pixel.

All I’m saying is that it’s entirely misleading to imply that only Pixels are vulnerable. This is not the case, even for iPhones.

I’m also not sure why you seem to be trying to say I disagree on the fact that Google is happy to leave vulnerabilities wide open, when that is exactly what I said in my original comment. Their new release schedule allows them to leave these vulnerabilities open for an even longer time, making Cellebrite’s job easier.

The law enforcement angle is exactly the point, yep.

Agreed on all points, but especially #1. Fuck Nestle. Every time I buy a new product at the grocery store, I check to make sure they’re not made by Nestle or a subsidiarity of Nestle.