Mediatek has been making phone SoCs since forever now, they have two lines - Helios and Dimensity. They’re used in many phones, usually on the lower end. Even Samsung uses them. Both lines have abysmal custom rom support compared to Snapdragon phones, so I don’t think you can hope for much there.

deleted by creator

Podman not because of security but because of quadlets (systemd integration). Makes setting up and managing container services a breeze.

So much more. It’s not even in the same ballpark.

What’s up with the abuse of the word open lately. I had a look at that project to see how they were doing the conversion, but I couldn’t find it. But I found this:

Short answer, yes! OpenScanCloud (OSC) is and will stay closed source…

Your data will be transferred through Dropbox and stored/processed on my local servers. I will use those image sets and resulting 3d models for further research, but none of your data will be published without your explicit consent!

I feel like I’d rather use Autodesk at that point. At least I know what I’m dealing with right out of the gate.

But check that it has all the features you need because it lags behind gitea in some aspects (like ci).

A few months ago I needed to install Google home for something Chromecast related, so I quickly searched the play store and installed it. Loaded it up and I see an ad, what the hell. App opens and I realise it isn’t Google Home, it’s something made to trick me into thinking it was when I wasn’t paying attention.

Google is letting their ads steal their own users from them.

I mean I learned it in a few days and found it very intuitive as well. Far more intuitive than I found fusion when I tried that years later. Inventor and onshape also feel more pleasant to use.

The issue seems to be that the fusion interface is very non-standard when compared to other cad suites, so people that get used to it first find everything else unintuitive.

Have you tried running xiaomi.eu ROMs?

Podman quadlets have been a blessing. They basically let you manage containers as if they were simple services. You just plop a container unit file in /etc/containers/systemd/, daemon-reload and presto, you’ve got a service that other containers or services can depend on.

I’ve been in love with the concept of ansible since I discovered it almost a decade ago, but I still hate how verbose it is, and how cumbersome the yaml based DSL is. You can have a role that basically does the job of 3 lines of bash and it’ll need 3 yaml files in 4 directories.

About 3 years ago I wrote a big ansible playbook that would fully configure my home server, desktop and laptop from a minimal arch install. Then I used said playbook for my laptop and server.

I just got a new laptop and went to look at the playbook but realised it probably needs to be updated in a few places. I got feelings of dread thinking about reading all that yaml and updating it.

So instead I’m just gonna rewrite everything in simple python with a few helper functions. The few roles I rewrote are already so much cleaner and shorter. Should be way faster and more user friendly and maintainable.

I’ll keep ansible for actual deployments.

Not sure what you’re on about, most package managers have a literal database of most package manager installed files. Debian and derivatives have dpkg --verify or debsums to verify the files, arch has paccheck, I’m sure other distros have something similar. And fixing them is just a matter of reinstalling the package, which you can do from a chroot if the system won’t boot.

Or you can just run your system on a checksumming FS like btrfs which will instantly tell you when a file goes bad.

Someone found a way to weaponise bikeshedding.

Let’s celebrate his life and his accomplishments

I’m a big fan of his work in the field of genocide denial and atrocity apologetics, truly inspirational.

The message that we approve of the removal of the headphone jack done in order to peddle wireless headphones…

All public companies are, it’s just what Boeing makes things that fall out of the sky if they mess up, so it’s more obvious.

Just have NAS A send a rocket with the data to NAS B.

If this was done by multiple people, I’m sure the person that designed this delivery mechanism is really annoyed with the person that made the sloppy payload, since that made it all get detected right away.

Seems to me that a lot of the world’s problems start with “well, the managers think…” They all seem extremely bad at the whole managing thing, good thing we don’t overpay them or anything like that.

TIL there are Linux people that don’t use OpenWRT. I always assumed everyone in the Linux community used it. It’s great.

Works great with mt7621 based routers if anyone ends up looking for something compatible.