@landley why am I not surprised of that?
Just like I see people shitting on #systemd about it when #xz is literally the one thing one cannot blame it for...
https://infosec.space/@kkarhan/112206692463157328

Like it makes my blood boil getting talked smack when it's not me who fecked up, so I imagine @pid_eins feeling the same:

At least if one wants to be angry at him, be angry for valid reasons or better yet: Make something better!

@landley @pid_eins
Speaking of valid criticism:
The #Stallmanists and "#GPLv3 Fanboys" are a literal net negative as their nonchalant attitude about bricking userspace with minor updates, and complete disregard to the fact that not everything is #AGPLv3-compatible #FLOSS but that #CCSS also exists and thus "just recompile it!" is not an option, showed me.

It's the reason why I demand everything to be statically linked binaries in @OS1337, because I think people should also "own" the dependencies and take responsibility.

• Ideally this would push developers to building lean, clean and well-maintained as well as -maintainable applications.

@landley @pid_eins @OS1337

And being able to list all the dependencies for OS/1337 is not just interesting but also vital to making things reproducible and auditable to the point that people don't have to trust me or @SweetAIBelle or anyones' scripts but could essentially do it step-by-step manually (potentially on an aorgapled system) as @w84death showcased with #Floppinux...

https://archive.org/details/floppinux-manual/

#OS1337

@landley @pid_eins @SweetAIBelle

As a matter of fact, I literally had to document how to basically setup an entire payment provider's backend infrastructure from scratch with just a few configuration files and database backups at hand because a competitior went belly up and the one person at @BaFin who went #ToldYaSo on their superiors and colleagues that held them down not jist smelled blood but also caused a lot of heads to roll and panic to spread...

Amd.yes, that documentation had to be written down so detailed yet simple that even an absolute #TechIlliterate could do it just by following the instructions step-by-step.

And apparently that put the regulators well at ease too, cuz their.busoness is thiriving...

@landley @SweetAIBelle so yeah, I think #transparency is something #FLOSS can and should deliver more by virtue of enabling #ReproducibleBuilds and -Setups!

We expect #Reproduceability in #mechanics, #electronics and any other #engineering as well, and we should do that with #Software, #Hardware and #Firmware too because it not just removes the need to #trust but also allows for longer support...

So instead of demanding a #remote-#updateable shite that can literally enable maliciois actors to "Hastings" drivers, @EU_Commission should've rather demanded #ReproduceableFirmware and that all the componemts, design and Software to be #OpenSource'd permissively to enshure #LongTermSupport and #compatibility and ease of testing for anyone from Users amd 1st party service centers to 3rd Party repair shops to Historic Vehicle owners...