When they publish their code and then get shocked and upset when someone actually reads it.

Reply to this note

Please Login to reply.

Discussion

The entire point of publishing it is so that people can read it and keep you honest and figure out what you're _really_ doing.

This has been my problem with the "FOSS crowd", since Day 1 on here.

1) A lot of them can't code, but they publish code, and when you ask them about some of it, they freak out. I suspect their stuff does stuff they didn't realize it did, so when you point it out, they're like OMG.

2) They think code being published absolves them of all sense of duty or tradesmanship concerning quality. It doesn't need to work because you can just fork it, bro.

3) They are aggressively transparent, but they sometimes hide little bits of important information in the gigantic heap, so you can see 60000 lines of code, but can't figure out how function XYZ works because it calls Mysterious Thingy That Is Somewhere Else.

4) They judge each other by Number of Lines contributed, (a.k.a. Le Dots Green 🟩🟩🟩), which rewards bloated, inefficient code.

5) They often supply software "for free" but the development is paid for by a fund that users donate to, so the software development ends up costing the users more than if they just paid for it, outright, and the code is less maintainable because there's no pressure to be efficient.

Code is a place where lies can be hidden pretty easily. Code and the legacy social networks are a match made in hell. Once you can censor the opinions of others, the suck can be redistributed from liars to innocent people, making them victims and eventually criminals (participants in the lie). That incentivizes the original liars to cheat even more to get privileges from it

I'm happy that we have nostr and opinions can resist that censorship. That way, maybe these opinions can hinder the spread of those inhuman lies