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.

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.

Who’s Charlie Kirk?

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.

Yeah, absolutely.

It probably will require her to pay up regarding attorney fees too right? I guess I’m not sure how it works in this case.

I’m glad I won’t ever have to hear about her ever again.

I notice that it’s mostly blue leaning states rushing to help people not starve. I guess it’s not a surprise, but people in red states are going to be affected by the lack of SNAP the most. I doubt it’ll make them stop voting against their own interests, of course.

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.

Surely the failure to work only applies to malicious programs and not vibecoded slop, right?

If the house flips, though, then the Epstein investigation along with other things can proceed, and the House can block bills before they go to the senate or president. So while it won’t fix anything outright, it can stop more damage.

Everyone who eats and drinks chemicals will eventually die!