@LucyWildboots@c.im it's not as if there's no evidence at at all, though, that supports the claim that it is not the accessibility of the QT button that drives abuse.
Just as individuals' stories can not be brushed aside it can not be brushed aside.
Anyway, As it stands now you are relying on one person's or one term's decision, I believe, and that can not be counted on long-term. We have seen mastodon give up on some of its traditional principles.
Assuming for the sake of the argument that it is indeed the availability of that button that significantly promotes abuse, I believe that in the long run the problem can only be solved by
1. Community with rules and enforcement and norms, and/or
2. Forking Mastodon to maintain a version that complicates the behaviour as in pre-2015 twitter, or
3. Abandoning 
altogether as it allows this feature in other software which will become more familiar over time and probably will start spreading faster than Mastodon once someone with lots of money decides to invest heavily.
@jo@blahaj.zone @MetalSamurai@mas.to @jupiter_rowland@hub.netzgemeinde.eu
2. Forking Mastodon to maintain a version that complicates the behaviour as in pre-2015 twitter
Why fork? To have #Mastodon with QTs?
No need for a fork. "Mastodon with QTs" already exists. #Pleroma, #Akkoma, #MissKey, #CalcKey, #FoundKey etc.
In fact, they're all Mastodon with QTs and with text formatting. Just not with the exact same UI/UX as Mastodon because they're independent projects.
@Jo (she/her) @LucyWildboots 🏳️🌈
Tells you they’re interested in effective, concise communication.
