@giantspecks @mlanger @jakebrake @mayintoronto Hi John! I agree, you should be able to follow hashtags globally across the Fediverse. That's why we're making tags.pub.
Dylan M. Taylor is not a household name in the Linux world. At least, he wasn’t until recently.
The software engineer and longtime open source contributor has quietly built a respectable track record over the years: writing Python code for the Arch Linux installer, maintaining packages for NixOS, and contributing CI/CD pipelines to various FOSS projects.
But a recent change he made to systemd has pushed him into the spotlight, along with a wave of intense debate.
At the center of the controversy is a seemingly simple addition Dylan made: an optional birthDate field in systemd’s user database.
Simply not true. In any such project, major proposals first get discussed as issues and community either vets a plan or comes up with an alternative before more solid steps such as PRs start. What is being done here is clearly trying to downplay a major change as a minor one. There are loads of blog posts and discussions on why this isn’t a minor change, especially when the author of the PR himself admits the goal is to comply with age verification laws. I will not get into that here. Suffice to say, at best, this is a political statement of the kind “we are ok to comply with surveillance and will show minimal resistance”. Yet they try to play this as if they are just changing a typo in the documents. Thanks to Lennart for his life long contributions to FOSS, despite him at some point joining Microsoft, the antithesis of everything that is FOSS. I am sure many things he did shaped how the open-source developed on a world-wide level. This still does not mean that his reaction to everything will be correct. To me this was more like a “fuck all, this was a minor change, don’t care what you say” attitude, which in my world-view has place in propriety software world not FOSS.
Compliance with fascism is indistinguishable from fascism.
At the risk of being serious, there’s really no good way to set user environment variables. (It’s been a while since I last checked, so I might be wrong)
PAM used to have an equivalent to their /etc/environment for users, but that was deprecated or maybe removed last I checked.
Systemd user environment variables don’t apply in a shell context
.bashrc only works if you use bash as login shell and I’m not sure if it applies everywhere. Sure, I can set stuff in the shell I use, but it feels weird to modify my shell in order to change global environment variables.
Yeah it’s such a mess. Last I tried I had to set my variable in like 3 different places and it still didn’t apply everywhere I expected it to.
Dear #WordPress users, I want to hear your opinion!
I'm currently finishing my work on the Polls For #ActivityPub plugin.
I decided to use a custom post type for each poll. However, many people mentioned that they would like to also add polls to normal posts.
My first question is: what is the best workflow/UI for the block-editor when adding a new poll block to a normal post?
I started with an empty state: "Create new Poll, Embed existing poll". Here I was wondering, whether I should directly enforce the user to create a poll which is stored as a draft when choosing "Create new poll", or keeping all data local to the post until the post is saved/published.
And should I allow the user to edit an embedded poll inline? Or should I just link to the edit link of the poll directly, once it's created? And how many warnings about such relationships do users expect? When deleting a poll that might be embedded. Isn't it similar to media? What are your wishes?!
https://codeberg.org/linos/wordpress-polls-for-activitypub/issues/41
paywall
If only there was a link to archived copy in the post.
I didn’t know he did that movie, but it was fantastic, if tonally very different from Community.
Right, and as much as I’ve followed his work and tried to learn more about writing, all I can profess is deep perplexity about how I would go about writing this film!
Someone on the github issue thread has been asking for clinfo output on affected systems, theorising that client issues are caused by issues with vendor detection.
This is a bit of an ask, but if it’s quick to jump forward and back between ROCm releases on your setup, would you be able to pass your clinfo output from 7.2.0 into the ticket linked above? No worries if not
I uploaded a quick video about the issue for Github. Passing it along to you as well :)
appreciate you 😊
@jaz@toot.wales Great, the CFP for the track is now open!
https://hackers.pub/@fedidevkr/2026/fediverse-social-web-track-at-coscup-2026-cfp
Ooooo, nice! I made the same thing recently, but this one uses threadiverse communities for the Usenet groups - https://piefed.social/c/piefed_meta/p/1904499/back-to-the-future-interacting-with-threadiverse-communities-through-usenet-nntp