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.
Static_Rocket
joined 2 years ago
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
Do the opposite of all this, assuming you ran this script some time between 2024 and now:
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.
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.
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
view more: next ›
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.