Being an open source dev requires thicker skin than you'd think, and even thinker than most people have.
Either you go the community route where you build a loyal user base, listen to feedback, and have q community of contributors as well.
Or you go the 'I made something cool for me, and its open so anyone can use it too!'
The former is sustainable, the later is not if you domt maintain the idea that its yours first and only.
Once you start half listening to people using your stuff, but believe what you want is right, starts to isolate you.
You think all your users are stupid for their feature requests, because you don't need it. Plus you alone are in charge. Its your repo.
This ego can continue to inflate to this point. I've seen it in both closed and open source (anyone remever when the FSLabs A320 for Microsoft flightsim with malware? Just me?... Okay).
And all 3 hinge on the premise of courts will do 'sane' things, without any kind of justification for them. So yeah, all 3 are moot if you remove that assumption.
If you listen carefully, you can hear them moving the goal posts from "countering Facebook knowledge" to "must be universally better in every scenario"
Ai disclosure?
You should as a rule read community rules before posting your projects.
Your missing the disclosure in your title