Legit thought it was just going to be a wall of text editors and nothing else

If I resort to using a Mac I want someone to put me out of my misery.

There was a rather famous piece of software at my last job. Guy writing it wanted job security. A lot of the core variables of the application were named based on the sounds a helicopter made. God damn onomatopoeia variables. Pretty sure that shit is still in use somewhere.

There were old wrappers that emulated sendmail but reformatted the message for use with gotify and such

Well, I wouldn’t go that far. Let’s not forget Nextcloud started as a fork for the same reason. The permissive license doesn’t stop us from keeping it alive, but it is something to be cautious of.

I’m curious about opencloud. It’s flashy, uses go, and has everything that I’m actively using in Nextcloud. The license does make me a little cautious about it though. Apache v2 on the server side is unusually permissive. AGPLv3 on the web ui is cool, but it’s also not really helpful if you’re not required to publish server changes.

deleted by creator

https://wiki.archlinux.org/title/Podman#Quadlet

It does, but it’s disabled by default. It’s explicitly for docker compatibility though, not a core part of the application.

You shouldn’t need to use the aur unless cachy is restricting your repo access. It’s all in arch extras.

I’m a little disappointed in the amount of time spent on the XZ attack. The title and it starting off with some good history made me think this was going to be more of a retrospective, looking into the issues that created the solutions used today.

It seems to be just calling out the solutions and how they would interfere or did interfere with a given attack, where XZ is most commonly used as an example.

You have the potential to run into issues if the device is externally managed. At&t likes to push firmware updates at early hours. Cutting power during one of those would be problematic.

It’s better than nothing but I hate the additional logs that came from it constantly fighting firewalld.

This was a large part of the reason I switched to rootless podman for everything

It’s astounding how many lowlifes are using commit counts to measure impact. It’s just throwing bisectability out the window and promoting stupid tactics for quick returns.

I use them all the time, but that’s just because of Yocto and the need to keep at least the 3 major LTS builds hot in the event something breaks.

This is unrealistic, agile stages aren’t missing unusual pieces that aren’t quite critical but probably should be there anyway.

Don’t forget about linkwarden

Just cross your fingers nobody attempts to import it…

Doesn’t avoiding JS typically structure a website in such a way that the browsers built-in assistive services can cover it easier?