@ariadne Rename edera to bunco

quote of the day

@ariadne @wfk @lhp @fossdd abolish su.

@ariadne @fossdd wanting to rewrite something in $other_programming_language gives you an opportunity to not only merely rewrite (because that is the easy part, let's face it) but question design decisions and try to be *better* than the thing you're trying to somehow rewrite.

If sudo-rs is much more than just sudo rewritten in rust (and I'm sure that's the case, because the same tool written in a different language certainly is not interesting. Rewriting is cheap nowadays, for better or worse) then it probably should part ways with "sudo". Because if it is *just* merely a rewrite, it failed.

new old phone in new box.

#nuraeco #shotonnura

I was at the #thrift store, and I asked the electronics attendee if they had old PCs, he said no. But he did say he had some at home.

I'm now the proud owner of a full-fat #TNT2 and an #IDE #Zip drive!

#retrocomputing

grrrrrrr.

again: AlpineBSD is *not* related to Alpine in any way. drew has built a distribution from scratch using abuild and apk (certainly nothing wrong with this part).

but the media keeps reporting as if this is literally Alpine, but BSD instead. other than using the build scripts and package format, it has basically nothing to do with Alpine.

for example @lproven in his coverage, describes it as "Combining the NetBSD kernel with the Alpine Linux userland", which it very much is not.

i really wish drew would rename his project...

RE: https://mastodon.social/@cks/117547904775599551

if you rewrite software in rust and then deviate from how that software behaves -- you haven't actually rewritten the software in rust, you've just made an incompatible clone.

(the real security problems with sudo are related to the combinatorial complexity of the config format anyway)

@ariadne ok I'm wrong

@ariadne At least that's what he said on irc

@ariadne I thought it was a temporary name

@jn Interesting!

Harvard researchers studied 718 companies and found AI coding agents increased lines of code by 30%, but no meaningful increase in completed tasks or projects.

Meanwhile, review time rose 49%.

Generating code faster hasn’t translated into completing more work. The bottleneck has moved to code reviews.

The solution the industry is landing on is throwing more AI at the problem. AI writes the code, AI reviews the code and no one knows how it works.

https://fion.ac/jellyfish.pdf

Data:
- LLMs are killing the planet
- LLMs are raising utility prices
- LLMs are raising computer prices
- LLMs give you teh dums
- LLMs show negligible increases in net productivity
- LLM costs are going up
- LLMs run on stolen content
- LLM companies keep breaking laws and saying, "Oopsie!"

Open Source maintainers for some reason:
- We are debating our AI policy, but it's a tough decision. *whines*

Dudes. WTF is wrong with you?

@jn haha https://wiki.nura.eco/wiki/KTC_msd6a358m2c1_(ktc-msd6a358m2c1)#Uart

Anthropic's Claude Code Cursor extension was also compromised, same remote access backdoor https://cursor.com/blog/claude-code-extension-security-notice

Anthropic still haven't admitted what has happened.

Anthropic Visual Studio Claude Code extension on Cursor has malware in it, which creates a remote access Trojan to desktops.

https://phorion.io/blog/offical-claude-code-vsx-compromise/

this is infuriating @nctvnl, why are security and counterterrorism swapped in your <title>?

🙏❤️ Please support my beautiful family. 🥹🌷 My family deserves your support and kindness. 🇵🇸💖 Every little help means so much to us. 🤲✨https://chuffed.org/project/208485-give-waleeds-family-a-chance-to-live

Maintainers of open source projects should be mentoring folks to become their replacements. Not just thinking this is about controlling their project.
I have learned this the hard way for gcc.
You can't just think it is your way or the highway. Also gsoc is NOT a replacement for mentoring inside the project. It should supplement the mentoring that is done, just like an internship.

Also this is not unique to gcc, it is many open source projects.
And then there is the gaming of github stats, the one or two commits in llvm and leave issue. Those are used to gain stats for a job.
Seriously open source is broken because of the gaming of the system.

Even inside companies where you have the person with the most open source commits. Or the person who opened the most issue. Or the person who reviewed the most. (What is funny is that i am that person but I am not trying to play the game of counting, I am just trying to push gcc forward).
At the same time I am mentoring folks both inside and outside of qualcomm on both gcc (and even to a less sense llvm) and performance analysis.
But going back to my original point is mentoring and maintainship overlaps. It is not one or the other but rather both in the same role.

By the time you step down you should have at least mentored a few to be able to take you from you. If you have not you partially failed a as a maintainer as the project will no longer can be maintained in the future.