Gregory's Server@freemo @Gargron yeah, my point is we're all in this - if we're suggesting failures somewhere we need to suggest solutions.
Mastodon 4.x has webhook that greatly help here - you can plugin akismet or other anti spam services or look for dupe posts or trigger your own rate limits.
All of us should be coordinating and collaborating here - it's an OSS project and if you run a fork, it seems disingenuous to say "fix your code" if what they fix won't be able to address similar things happening from your fork - unless you have explicit suggestions :)
@supernovae @Gargron
Back before QOTO diverged too far from mastodon to be feasable most of our fixes were offered as PR to mastodon... surprise surprise Eugene usually rejected them for ideological reasons and here we are.
This isnt a case of "well its open-source"... no you have a highly opinionated guy running the scene who has made highly questionable and destructive decisions on various occasions and who has stifled good contributions to the codebase at every turn (and often gets called out)... So no the fault lies with Eugene here right fromt he getgo.
@supernovae @Gargron
Back before QOTO diverged too far from mastodon to be feasable most of our fixes were offered as PR to mastodon... surprise surprise Eugene usually rejected them for ideological reasons and here we are.
This isnt a case of "well its open-source"... no you have a highly opinionated guy running the scene who has made highly questionable and destructive decisions on various occasions and who has stifled good contributions to the codebase at every turn (and often gets called out)......