@Mastodon @Gargron so when are you gonna fix hot issues, most notably #developers / #maintainers of #Mastodon who just close issues without reading them!
@hisold Not sorry, because I do actually care about #Mastodon and the #Fediverse so I am invested in it getting better.
If you want everything to be criminally simplified to fit the attention span of some shitty billionaire egoist, then maybe #Shitter has you covered.
@[email protected] @[email protected] There are [even more issues](https://github.com/mastodon/mastodon/issues/23249) [neglected](https://github.com/mastodon/mastodon/issues/33530) like that... #Mastodon #FLOSS
yeah but you won't get movement by yelling at mastodon devs
you have to contribute to the project yourself, or adopt a more circumspect approach
people who make loud angry demands do not help. they are in no position to have any leverage: open source is not a hierarchy, it's not like you're in the office and you call up a boss and they make things happen
i'm not really disagreeing with you, and you're really not yelling
but i do see this behavior unfortunately out there
@benroyce @kkarhan I've opened many issues on open source projects.
What really annoys me is wrong duplicate classifications. Many of which I do blame on laziness.
When I see they have a thousand open issues, I know there won't be happening much in the coming months. I know what it's like for them because it's the same at my work. A hundred User Stories that become 500 tasks plus 200 bugs following them and so on...
@hisold @benroyce exactly that is my problem....
I can accept that my issue won't be worked on anytime soon.
But I can accept 10+ year old, low-priority issues being open instead of lazy-ass shite.
@hisold @benroyce I write as dense as possible, but certain issues need explaining, including why it's not a duplicate and why this is an issue...
Do I sound jaded?