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.

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.

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

Usual tracking and fingerprinting issues. Would need to sandbox it to make it secure, but that then makes the fake traffic easier to identify. Not worth it in the end.

That defeats the privacy and bandwidth reasons you’d want to use uBlock but that’s close to the operating idea of AdNauseam.

I just want some doc language that handles conditional sections sanely and has useful appendix tools.

I think one has to cope with it the same way the inventor of the ice pick had to cope with Walter Jackson Freeman II. You can’t really control what people do with your tools. If you think someone actively destroying lives will bend to the whims of a license, that’s cool. I wish I had that level of optimism. Right now it’s still pulling teeth to get companies to respect GPLv3.

Pinchflat is one of the good containers that doesn’t try to play with ID remapping or anything. You just need a container quadlet like the following:

[Install]
WantedBy=default.target

[Container]
Image=ghcr.io/kieraneglin/pinchflat:latest

Environment=TZ=CHANGEME

Volume=CHANGEME/config:/config
Volume=CHANGEME/downloads:/downloads

PublishPort=127.0.0.1:8945:8945

It’ll run as the quadlet user id by default.

I haven’t heard anyone talk about puppy Linux in a bit. That used to be the go to for ultra lightweight setups.

All of these alternatives and you missed the best one ripgrep (rg). The other ones in my opinion are nice to have. Recursive multi-threaded grep that respects gitignore files is a must for me.

“I want to know why this is broken. How to fix it can come later.”

Or override the TERM variable in your ssh config. Setting it to an xterm value has been supported by any niche term I’ve used over the years without sacrificing any of the usual functions.

Arch. Started using it in high school. Never had a reason to switch. Now I’m just regularly frustrated by other distros trying to make things easier by abstracting simple configurations behind layers of custom scripts.

AUR, when I can. I run my own binary package repo. App images are an interesting concept, but usually they are compiled against ancient versions of glibc for increased compatibility. Optimizations and CVE patches may or may not be applied, LD lookups are longer, etc.

Sway still primarily counts as a WM + Compositor, but considering it has keymaps, autostart, and libinput config mechanisms embedded in it, I would say it borders a desktop environment.

The inhibit_idle specifier is cool, thanks for the pointer. This two liner can be replaced with:

for_window [all] inhibit_idle fullscreen

Please people, these stand alone guides are fine but continual use of the wiki ensures it is kept up to date. These should not act as or be used like a substitute.

https://wiki.archlinux.org/title/Linux_console/Keyboard_configuration https://wiki.archlinux.org/title/Xorg/Keyboard_configuration

The real problem: Define beginner distro

Every user is starting from a different point. There is no such thing as a beginner distro. You can say this distro is good for people who can grasp the idea of a command line or this distro is good for people who have no idea command line interfaces exist, but that doesn’t differentiate between beginner friendly or not.