i voted today and i think you should too if/when you can. i live in a "safe blue area" but i did it anyway.

i'm very skeptical about posts appearing around the time of an election that seem to normalize or even glorify the idea that voting doesn't matter. it's not everything, but it is something. perhaps things will get worse either way, but get even worse when fascists win.

there are people who can't vote. if you can, consider them before deciding you won't, as they happen to be some of the most vulnerable right now.

you can think voting doesn't matter, or that it's bad for some reason, but it's a suspicious time to promote such ideas, imo.

i got the librewolf (firefox) update, and of course the roundening and gradientizing continues

the indicator for a container tab is just a 1-pixel line now? i have my tabs vertical and keep them collapsed most of the time, and it's so hard to see.

RE: https://mstdn.plus/@privacynews/117486993524091132

signal is out there reminding everyone that memory safety issues are not the only class of vulnerability that can result in extremely serious levels of compromise

(the vulnerable code was written in rust)

maybe i get it now; the user isn't even a part of that equation. they're nobody. in the comparison, the project's leadership (usually a single person, often a dude, just saying) is the consumer. they're the customer. AI slop is meat. and if they want to eat it, it's no one else's business.

except, in reality, it is the users' business, because we have to smell their shit

like, if you don't think there's anything wrong with eating meat, whatever, you do you. but if you offer it to me in a meal, i'll have to decline. that doesn't mean i'm forcing my eating habits onto you, i'm just establishing my own boundaries and preferences.

accepting slop into a project is not just an act of consumption on the part of the project; it's a choice that is pushed onto your users as well. i'm not sure why that's so hard to understand.

the analogy is just so backwards.

apparently people who don't want AI slop in their software are vegetarians, in this comparison. okay, then i suppose that means that the software project is like...a restaurant. or no, it's more like a meal. and the developers are... chefs contributing to the meal, then (i guess?).

it's not a restaurant in this example because everybody ends up with the same software (meal), unless you give them build-time options, but i don't think many projects let you exclude all AI-generated code at compile time.

so, if a chef contributes meat, that goes into a meal that every customer eats. you've now excluded vegetarians entirely in order to accommodate your chef's wishes, because - i suppose - they find it easier to work with meat?

ugh, it's just weird and confusing and not very fitting at all.

"Vegetarians don't force their eating habits onto everybody else. In the same spirit, [...] patches written with the help of LLMs aren't outright rejected"

...i have thoughts

nope, now it's definitely dead.

pmbootstrap time after all

oh, wait. i disabled sshd by default with systemd, but now with openrc, it's enabled on startup again... so i can get in and maybe fix something.

that did not go well!

will probably need to do pmbootstrap again then. i wonder if i'll lose my app data. (it was nothing too special, but still.)

let's see if i can figure out how to upgrade from systemd to openrc on #nura...

seeing the #nginx news and checking to see how #caddy is doing, i stumbled upon the #caddyshack tag and got worried for a sec

4

2027 can't be worse than 2026, right?

today is one of those "get your chores done before you even think about hopping on the computer" days

but i do still have a phone...

i have a newfound appreciation for password prompts that don't timeout quickly by default, especially in situations where i need to deal with password manager wrangling / have to type in a long one that was randomly generated. credit to the relatively short timeouts from gpg and polkit for helping me better appreciate the other prompts i interact with (and sudo!) that don't bring about such undue anxiety.

making some exciting (to me) progress here on being able to configure certain things via guix on nura! i learned about guix build --file=[...]. i've been working on a script that takes guix services and filters out the unneeded/unwanted dependencies (like file-system, boot, profile, system, etc, user-processes), creating new service types that lack them as necessary, and outputs paths to a shepherd config file and an activation script. at this point, it is looking like i'll perhaps only need the path for the shepherd script, and i can make a systemd service which starts shepherd. 🙌

of course it's all very hacky and certainly nowhere near a packageable state or anything like that, but i do plan to share more as i make more progress.

welp, i just learned that my tmux sessions get killed as soon as ssh disconnects on nura, which kinda defeats the purpose of using tmux for me. anyone know why and how to prevent this?

systemd[1]: session-c69.scope: Killing process 420 (tmux: server) with signal SIGTERM.

#nura #linux #tmux #systemd

looking at my profile page for a sec, i see i have three lil cards: one with my pronouns, and two with links to codey pages. 2/3 of these cards are verified, green. one looks out of place...

can... can i verify my pronouns?