On reflection the whole qt thing will probably be rendered moot by link preview cards and the only friction then ends up being "how hard is it to copy a link and paste it into the post field", in which case we're back to where we are.
@darius@ryanrandall@jessamyn@dansinker@danhon The dilemma about quote tweets is the result of trying to solve issues of substantive ethics through procedural means, because the people involved by definition do not have & do not want to have shared governance. Among other things, it is a design feature used to enlist growing numbers of people in conflict. If functioning shared governance existed, it would not be needed as much.
serious question: would you also want that ping for people posting a link to a post?
I am trying to balance the need of minority communities who desperately want the feature in order to do things like advocate for causes they care about against the need of (often overlapping) communities that have been hurt by similar features in the past.
Perhaps a DM notification that would require the initial poster to approve a quote boost before it goes out?
It not only would give them power to approve, but also provide warning that they might want to lock down their accounts if they've been found by a group trying to brigade against them.
This second facet would hopefully act as a deterrent against bad-faith, weaponized decontextualization.
@danhon the implementation on fedibird (a fork with quotes) is basically exactly an expanded link preview and a button in the UI that lets you one-click start a post with a link in it
When the post reaches servers that don't support it, it just renders like:
@darius@ryanrandall@jessamyn@dansinker@danhon I have sometimes wondered if the most useful feature for managing features like QT would be a way for people you know and trust to give you feedback when you’re being a jerk. Except that even this proceduralism would likely fail because of selection bias in friends and audience.
@darius I don’t think the answer will be found in situation-agnostic design features. It’s a question of power, which means institutions and culture and relationships. Thinking about Adrienne Marie Brown’s work in particular here.
@dansinker@danhon@ryanrandall@jessamyn@darius Intrigued by the data Q. Might post about it once I recover. Part 1: - burden of proof - how much harassment/harm is acceptable on avg - how the idea of a design feature causing harm takes you down a path that makes other kinds of intervention seem implausible Part 2: asking the Q: Micro: - recruitment to harassment - moral outrage Macro: - how was it used in practice on Twitter
@danhon@ryanrandall@jessamyn@darius@natematias I'm being serious! It just seems like on Mastodon there's this inherent understanding that QTs == bad and, well, could someone point me to the data that backs that up?
@danhon@ryanrandall@jessamyn@darius@natematias the funny thing about QTs is there seems to just be a religious conviction that they are a vehicle for harassment, but like... is there any data to back that up?
@ryanrandall@dansinker@danhon@jessamyn@darius Thank you for these thoughts! Because I want to contribute constructively beyond the limitations of scattered conversations and short posts, I have emailed Dan Hon asking how I can help, with a few ideas.
@natematias@dansinker@danhon@jessamyn@darius Cost-benefit is where my mind goes first, too… but at the risk of "responsibility-splaining" to folks with more experience, if the analysis is done uncritically, it's easy to mistake "we" for a constant, when "we" live within a varied matrix of interlocking oppressions.
"Our" harms will be unevenly distributed.
Analyzed uncritically, cost-benefit data'll show you that being Black & gay & an immigrant is inherently high-risk, when our problem is having far too many systems which each quite efficiently route harm toward such a person.
Right now, the lack of QTs seems to act as a Jersey barrier, with just enough friction to safely redirect low-effort, but occasionally intentional harms.
Taking the analogy further, hopefully there's an elegant design to let traffic cross lanes and change directions more safely… but any data analysis needs to be careful about what it mistakes for a constant, whose benefits / harms "count," & how they do.