UnityDevice

Every time I thought the US was stupid for doing a thing, the rest of the world followed with the same bullshit a few years later. Some sooner, some later. The US is not more stupid, they’re trendsetters.

They seem good on paper - every time I look for a phone on gsmarena’s phone finder I get a few of their rog phones in the results. But then I look at the price tag and the gamer aesthetic, and I ignore them.

I tried the link preview feature as well, and to say the response to it is overblown is putting it mildly. I haven’t looked at the source code, but based on how it appears to work I’m not sure it even qualifies as AI. It basically selects 2-3 sentences from the reading mode version of an article, but the selection is so bad it might as well be random. Not surprising as it’s a tiny model that runs locally and is only given a second to make the selection.

I actually laughed when I saw it - this is what all the weeks of fuss were about?

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.

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.

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.

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

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.

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.

I use gnome for the most part. I have been checking out kde recently to see how the newer versions stack up (gave up on it during the 4.0 days). As you mention kde supports dpms changes on wayland because they have their own protocol extension for that.

That’s actually my biggest gripe with wayland - the huge amount of fragmentation it has caused. I’m pretty confident that almost all the missing features I talked about are possible on one or two of the compositors, but not all of them. And definitely not on the one I use. I’m sure once some pragmatism takes hold that all the issues will be ironed out, but my plan for now is to stick to X11 until that happens.

For me it’s a million little details that just don’t work. Stuff like positioning windows, removing decorations from a window, remapping buttons on a trackball, setting a graphics output to tvrgb, disabling a display via ssh and enabling it again, etc.

It’s not just about hardware compatibility. It has to be compatible with existing workflows, and it’s currently very limiting.

set -euo pipefail at the top of every script makes stuff a lot safer. Explanation here.

I remember having this realisation about Mir, but only after we collectively ran it off the cliff wall. The main reason everyone piled on Mir was that it was thought that Canonical would be priming Linux desktop for fragmentation with two competing standards.

But in fact, Mir was providing a solution to the fragmentation Wayland was bringing. Now we have 3, 4, 5 Mir-s, all with slight incompatibilities. Want a feature? Better hope all of them decide to implement the extension after someone proposes it. We know how well that worked in the past.

This is also ironic because the detractors of Xorg constantly talked about the issues with Xorg extensions and how many of them there were. But I never really had to look up which extensions Xorg supported, while I have had to do that with Wayland compositors.