SuperDicqHow to fix modern search engines, I guess.
Protect your privacy and freedom. GNU/Linux lover. Let's burn everything down. I am doing networking stuff around linux kernel.
Become who you are!
Fernando F. Mancera
@ffmancera
- 190 Followers
- 138 Following
- 1.7K Posts
2cents: a moderator should not halt a discussion in a community even if it is heated and there are CoC violations. If there are, it should only mute/freeze the people not following CoC.
When you force-halt a discussion you are killing momentum which is essential to get things done. And, by the way, you are exerting chilling effect.
This tactic has been used by politician since a loooong time, so think twice before doing it in your community.
LWN.net[$] openSUSE "terms of site" raise complaints about age restrictions
Many people in the Linux community began using the operating system—and contributing to open source—at a tender age, often well before their 16th birthday. Thus, a rece [...]
Baldur Bjarnason"The old world of tech is dying and the new cannot be born"
https://www.baldurbjarnason.com/2026/the-old-world-of-tech-is-dying/
This ones leans a bit more into theory and politics than I usually do when writing about the industry, but this moment in time warrants it, I think.
Mitchell HashimotoI strongly believe there are entire companies right now under heavy AI psychosis and its impossible to have rational conversations about it with them. I can't name any specific people because they include personal friends I deeply respect, but I worry about how this plays out.
I lived through the great MTBF vs MTTR (mean-time-between-failure vs. mean-time-to-recovery) reckoning of infrastructure during the transition to cloud and cloud automation. All those arguments are rearing their ugly heads again but now its... the whole software development industry (maybe the whole world, really).
It's frightening, because the psychosis folks operate under an almost absolute "MTTR is all you need" mentality: "its fine to ship bugs because the agents will fix them so quickly and at a scale humans can't do!" We learned in infrastructure that MTTR is great but you can't yeet resilient systems entirely.
The main issue is I don't even know how to bring this up to people I know personally, because bringing this topic up leads to immediately dismissals like "no no, it has full test coverage" or "bug reports are going down" or something, which just don't paint the whole picture.
We already learned this lesson once in infrastructure: you can automate yourself into a very resilient catastrophe machine. Systems can appear healthy by local metrics while globally becoming incomprehensible. Bug reports can go down while latent risk explodes. Test coverage can rise while semantic understanding falls. Changes happens so fast that nobody notices the underlying architecture decaying.
I worry.
This is pure damage control because it got media coverage. Sadly, for some people it seems media coverage is more powerful than the project's community. But well, I should have expected this reasoning. At the end, it's coming from a corporate person not a community person, yay.
I won't reply on the thread because well, why would I do it at this point... but:
"My chief concern is why it seems none of the Council members were reached out to until after the vote."
This is just written in bad faith. By the time of the vote, I already quit. By the time of the vote there were 80 posts on the thread. By the time of the vote 2 FESCo members had complained already.
This argument is a strawman to deviate the attention and do damage control. Quite sad :(
IMHO, @lwn did it again. This is the best article I have found on the Fedora AI thread.
ljsI am entering Lorenzo act 2 where my shit posts will be made by claude.
I'll close with this. None of what I've written makes today easier. It isn't supposed to.
What I want you to know is that I've made this decision carefully, my intention is to make it only once, and I'm going to do right by the people blocking me and by the people still reading my shitposts.
It has been proven that Fedora made the right call moving to Forgejo.