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.

Yeah, not sure how much he’s distancing himself from FUTO related things though. He brought up grayjay recently, but only specifically to talk about the devs comments on recent Texas app store legislation. Kind of a wash.

Given he is playing politician now, I don’t think he’s going to make a public statement about it. Not only would it hurt his influence but it would probably stall out any ongoing negotiations regarding right to repair. Shit sucks in general.

And what do you think that polling rate was to fill up a 512 GB SD card? It’s all speculation but this isn’t a super collider, we shouldn’t need sub second polling of a vehicle that can only move 5.6 km/h.

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.

This is so dumb, how could anyone at the FCC even humor such a request?

“Please help us, we overcomplicated billing and don’t want to explain it to anyone”

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

Honestly surprised nobody has tried to sell some bolt on diffusing/screen mask for this reason

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.

I’m pretty sure the mirror was setup before that was an option. No reason to turn it off now that it’s a source of entertainment.

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.

https://wiki.archlinux.org/title/Wayland#Automation

Honestly, I was running into the limits of stow. Want to unstow some configs on a bare machine? I hope you wanted that entire directory to be a symlink. Then I saw that someone had actually fixed that many years ago but the maintainer at the time was caught up in some personal crypto related projects and did not appear to be looking at the mailing list.

Chezmoi fixed that, applied a templating engine and added a data mechanism. In moving my stow configs I realized that application specific config file deployments are nice but shouldn’t be necessary. Templates fill that gap, and meshing them with scripts allows you to do some cool things only when variables change.

Plus I was beginning to play around with go at the time, so it just seemed like a good idea to use something I could contribute to if I needed.

I still don’t think I’m using chezmoi to it’s full potential, but I am fairly proud of the script I use to determine data sources for my waybar config on all of my machines.

All public and I regularly link people to my bash functions. Started with git bare repos, moved to stow, now on chezmoi. If I need anything more complex than chezmoi for these I’ll probably give up syncing them altogether.

https://github.com/StaticRocket/dotfiles

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.

The problem here being these payment processors are global and none of this is illegal in the jurisdictions affected. This regional blocking, while nice, shouldn’t even need to be a “solution” to this. It’s a sledgehammer “solution” to something that was never enough of an issue for actual legislation.

Edit: clarify point

Wouldn’t be the first time firmware and RCEs were linked together for them.

Well, to be fair the 10 series was actually an impressive improvement to what was available. Since then I switched to AMD for better SW support. I know since then the improvements have dwindled.