Post Puns On Main
THE MAIN RULE: ALL TEXT POSTS MUST CONTAIN "MAIN" OR BE ENTIRELY IMAGES (INLINE OR EMOJI)
(Temporary moratorium on main rule to encourage more posting on main. We reserve the right to arbitrarily enforce it whenever we wish and the right to strike this line and enforce mainposting with zero notification to the users because its funny)
A hexbear.net commainity. Main sure to subscribe to other communities as well. Your feed will become the Lion's Main!
Good comrades mainly sort posts by hot and comments by new!
State-by-state guide on maintaining firearm ownership
Domain guide on mutual aid and foodbank resources
Tips for looking at financials of non-profits (How to donate amainly)
Community-sourced megapost on the main media sources to radicalize libs and chuds with
Main Source for Feminism for Babies
Maintaining OpSec / Data Spring Cleaning guide
Remain up to date on what time is it in Moscow
view the rest of the comments
How can this issue be mitigated? The current system of a (usually not so) benevolent dictator(s) is the model for all FOSS projects I know of, lemmy included. As you've touched on, this is not at all democratic. However, I don't know if there are any version control hosting platforms (gitea, forgejo, etc.) that work without the code being held in the iron fist of an authoritarian code monkey. Then there is the issue of who should be allowed to contribute; there needs to be a way of keeping out people who contribute malware, or from taking so much control that they themselves become a code tyrant without a king code monkey to spitefully swat down improvements.
Even if those issues are resolved, there is still the massive gulf in power between code monkeys and non-technical users. If none of the code monkeys deign to implement features or bug fixes that non-technical users want or need, then those users are shit out of luck. Another wrench is thrown into things when it's software that runs on a server and there are also sysadmins who could pull the plug at any time even if a democratic system was built into the software.
I guess what I'm getting at is: what is a way to make FOSS as anarchic as possible without opening holes that bad actors could easily exploit and without leaving users incapable of making code be beholden to the code monkeys? The main thing FOSS has going for it is that its governance isn't as shit as how tech companies would handle it, and that's a very low bar to get over.