Containers are the best, so probably

Those both work fine in Wayland.

I use Bazzite for devwork too, I do use distrobox though which allows me to get proper dependencies without layering more onto the system image.

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?

The only real way to do heat transfer in space is through infrared. But that is not very efficient, so most compute in space is managed to reduce heat as much as possible. Data centers, or even just a few 2-4u servers with GPUs produce significantly more heat.

What if the craft is in the sun? Then, you not only have to dump the heat from the onboard servers, but also the sun. These changes are rapid, and not easily managed. Plus, the cold side would still need something to radiate into. Heat does not transfer the same way in a vacuum, even closed loop systems on the ground need air to dump heat into. And these companies don’t even want to use that because it’s not efficient, so they waste our water instead.

Make it make sense.

Server farms, especially ones with tons of GPUs, see little benefit from being in LEO. They cannot radiate heat efficiently, especially this amount of heat. Plus, unless boosted every now and then, they’ll eventually burn up.

How do you fix a hardware issue up there?

None of it adds up on the balance sheet. It makes zero sense to do this in space. The only benefit is hyping up the AI market because space. That benefit won’t last very long in our newscycle.

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.

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

That’s part of ADHD for a lot of people: hyperfixation/focus on topics that interest them, and struggles otherwise.

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.

Since someone asked in a cross post, DeFlock has an image-based guide on how to identify common ALPRs: https://deflock.me/identify

If you’re like me (and your area has a lot of them like mine does), once you notice one, you’ll start seeing them everywhere.

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.