FBXL Social

NixOS Is Dead; Here's Why It Was 100% Avoidable
https://www.youtube.com/watch?v=bb6SonDePzk

@anarchotaoist@liberdon.com
"Don't give up power" is a tactic with a definitive expiry date. Part of running a BDFL should include succession planning.
Another risk of being king is that you may make your death / injury a much more expident route to sabotaging your project.

I don't follow nixOS so I'm unfamiliar with this particular incident however.

>Another risk of being king is that you may make your death / injury a much more expident route to sabotaging your project.
Who on earth is going to assassinate an open source maintainer?
replies
1
announces
0
likes
0

@Hyolobrika@social.fbxl.net
Boeing!
Kidding aside, there are many other things that can be done before it gets to that level. But I wouldn't rule out psychological torture (
which sorta happened in he XZ incident iirc).

@Hyolobrika@social.fbxl.net
Couldn't find where I saw/heard about the XZ situation with that detail.
Closest I could find was this
OpenSUSE post:

Furthermore, others have already emphasized that the initial attack vector wasn’t technical. It wasn’t an archaic tarball. The actual initial attack was social engineering and used toxic behavior in communities. This is real and not only in this case affects the existing maintainers of open-source projects.

@gabriel I don't know about toxic behavior in communities, but it definitely was social engineering. They basically took advantage of his mental illness IIRC.