One of the most disturbing arguments I've seen against having a quote boost #qt feature:

Unlike a reply, quote tweets allow people to discus *what other people have said* Not reply to that person but make what they have said a topic of discussion.

People examining the discourse of others is troubling? (even if they can opt out, no, this shouldn't happen the argument goes, between even "consenting adults" *that's* how wicked it is)

It's... fascinating.

@futurebird The idea that you should have to talk to someone rather than about their post of public importance is so batshit and contrary to the way the real world works.

Imagine if students were assigned to @ authors over and over rather than writing about their books. 🤦

@futurebird I think their hidden assumption is that there should not be things of public importance here.

That everything here should be "politics free" interpersonal spaces for hobbies and feel-good stuff and everyone should ignore that the person they're engaging with about their hobbies is a nazi as long as they don't bring it up. 😠

@dalias

I get that feeling too. Especially from one user who accused me of "dogpiling" him when I'd replied with a question and literally one other person had also replied. (and I didn't even boost his post, because while it had some pretty clear racist subtex, I wasn't certain if that was what was going on, and I wanted to ask some questions and try to understand)

But, just because the response involved the topic of race it was a "dogpile" to him.

I wasn't even being critical of the guy!

@futurebird Sometimes I feel like after some big instances get good quoting ux, we should launch honeypot "we do not support quoting and won't federate with anyone who does!" instances just to get rid of these folks. 😂

@dalias 👀

I am reading respectfully.

@dalias @futurebird Believe it or not someone did say that in the journalist thread which I thought was somewhat over the top.
@sri @futurebird Well they're basically the folks who were willing to leave Twitter (at a time it was run relatively well, even!) for a suburban platform with basically no users and nothing of public relevance on it, because they wanted a whiter/"apolitical" space. So I think they're a good chance they'd do it again, just hopping to a gated community on the fediverse.
@sri @futurebird Keep in mind not only did they run for a whiter space; they did it during a time of rapidly rising fascism (2017-2019) when Twitter was one of the main fronts of the information war to challenge that.
@dalias @futurebird It might be helpful to identify who 'they' is here? The first migration consisted of furry and LBGTQ+ who left because of Nazis.
@sri @futurebird Indeed. I don't fault them for wanting to leave that harm, but I do fault anyone who is non-intersectional and who is "knocking down the ladder" about it rather than "tossing down a rope".
@dalias @sri @futurebird As someone who facilitates spaces for a wide range of perspectives, I believe that a platform can serve and function for a wide range of ways of interacting with it and a wide range of cultures, and it can be hard for someone in 1 culture to envision the experience of others. Hoping we can make this corporate-free space work for the many in many different ways.

@futurebird @dalias on the dogpiling stuff…

It was pointed out yesterday something I’ve noticed before: I can’t see context & other replies a lot of the time, unless I go to the “original link.” Someone was saying it makes a “reply guy culture” bc we can’t tell a question has been answered 6 times already. I could definitely see this resulting in accidental/coincidental dog piles that are visible only to the person receiving it, when they’ve said something that deserves response.

@maco "Someone was saying it makes a “reply guy culture” bc we can’t tell a question has been answered 6 times already."

Dear god, you might be right about this. I do feel like I'm answering the same thing over and over and over here.

And, you know I just try to assume good faith and be patient. But this is worth thinking about further, along with the idea of threading.

@futurebird @maco
i’m glad you mentioned the idea of threading. I think the QT issue and the issue of threading are both important and both connected to tools that can be used to enhance and focus a civil discussion, the fact that they have been used by bad actors notwithstanding.

@ChrisPirillo

Opt in is exactly what everyone is proposing.

Given this is the case I have a hard time understanding the controversy.

@futurebird @ChrisPirillo The controversy seems to originate from anyone who's been on the network for more than a month shaking their canes and yelling "keep yer dang fancy bird features off mah federated farm land ye gaw durn whippersnappers"

@elyseea @futurebird @maco

embarrassed to ask but - what is QT?

@Mab

QT stands for "Quote Tweet" which is what it is called on twitter when you re-share a post with a comment appended to the top.

Here it would be called "Quote Boost" since we don't have tweets on here. We have "posts," and they get "boosted" :)

#qt #quoteboost #quotetweet

@elyseea @futurebird @maco

One can already thread. Whether one wants more threading features than yet available is another matter.

And you can quote by doing a share-to-somewhere back to Mastodon! Or by copying and pasting an URL.

I truly do not understand what the problem is with that. It is the simplest thing in the world. But it encourages people to subtoot while singling out an individual for pile-on. Just subtoot! Or think HARD, then share the URL!

Tag the person if they MUST see it.

@chemoelectric

If posting links, screenshots, tagging the person is "the same" then what's the issue with having a feature that makes it easier... if it already exists?

@futurebird Because it encourages pile-ons and targeting, so that making it too easy is purposely avoided.

You don’t have to take my word for it about the toxicity of the thing. Do an experiment. (I did just this, to prove it to myself).

Find someone who really is making you angry. (In my case, it was a Twitter developer.) Then do a quote-toot and thread virulently attacking what they say. Better yet, do it from behind a block. See what happens.

@futurebird In any case, if someone is so dependent on ease of quoting that they can’t make the small effort to paste an URL, then I certainly think they are also too quick in their reactions to be allowed to do it.

We used to do it that way on Twitter BTW, before 2015. It was no difficulty and still was necessary if the person blocked you.

@chemoelectric

And posting a screenshot and link with a tag won't have the same impact?

@chemoelectric

Also here are links to my responses to someone who had basically the same comment as you.

https://sauropods.win/@futurebird/109570276684290306

https://sauropods.win/@futurebird/109570260475891620

Each contains an example that illustrates the difference.

myrmepropagandist (@[email protected])

Attached: 1 image @[email protected] Let me give you some examples that help illustrate the difference. I've put more information in the image description. Here is an example of how #qt is useful for talking about events unfolding in real time. #MissedQuoteBoost

Sauropods.win
@futurebird Illustrates the difference between what and what?
@chemoelectric
The difference between having a quote tweet feature an just linking to or screenshotting the post.

@futurebird Perhaps, whatever it is that’s supposed to show, how a link gets displayed is the issue there.

Twitter would display a link much as it would a ‘QT’. There wasn’t really a difference that I can remember (and I am NOT going back to Twitter to test that).

@futurebird @maco
This has probably been addressed before (100x) but it seems that threading needs to get figured out then QT. I’ve finally mostly figured out how to read threads and follow offshoots, but I still make mistakes and repeat a question or response even when I’m trying to be responsible. Not sure whether I’m the best test case, but if I’m not even sure I’m following the thread correctly, QT could get messy even with the best intentions
@KatMA @futurebird @maco
If you have tips on reading threads I for one would love to hear them.

@futurebird @maco @FeralRobots
Yeah, as I tried to think of some, I realized I may not be that good at it.

Let’s see. I try to *not* reply to the first post if there’s an extended convo going on bc…confusing. Pay attention to who is being tagged on post so I know what branch I’m in before replying or…confusing. Follow as many branches as I can so I try not to repeat something said elsewhere, but that gets…confusing

So basically I kinda suck at it?

@futurebird @FeralRobots @maco
So I have inadvertently demonstrated that threading needs to get a lot better before QT is a good option. I think the goal should be to make the Fediverse/Mastodon BETTER than Twitter. Having a QT Opt-In option is also an important way.
I’ve also seen ppl say there’s an add-on or other servers that allow QT. If so, any way ppl can block those if they opt-out? (Could be wrong tho)

@KatMA @futurebird @FeralRobots as far as I know, all that's going on _visually_ in both a Twitter QT and in some clients when someone links to a post on here is that they're doing a "rich" display of the linked content, the same way you get the image, headline, and preview for a news article whether on here, the bird site, or Facebook.

If you don't generate OpenGraph tags for a given post, it can't do that, but you can still link to whatever, so…you can still drive traffic at a link.

@FeralRobots @futurebird @maco
Honestly, I’m going to have to read up on some of the things you mention so I fully understand this, but I really appreciate the explanation. I like seeing how much more I have to learn. Thank you!

@KatMA @futurebird @maco
Is it that you [we] suck, or that it's hard to follow?

(Before this discussion it hadn't occurred to me that there was a federation-related reason for it being hard: Not every server has the same conversation at any given time!)

@futurebird @FeralRobots @maco
I’ve only been on a Fediverse server for 6 weeks so I start with the assumption that it’s me. Starting to think that threads are just hard to follow in general
Thank you for the shift in perspective!
@futurebird @maco you can mute conversation once you got answer
@ChickenPwny @futurebird @maco I can mute a person, don’t see a UI here for muting a conversation. Hints?
@Supposenot @ChickenPwny @futurebird @maco
On my server at least, the three little dots under someone's reply show the option to "mute conversation."
@NoTwit @ChickenPwny @futurebird @maco weird… didn’t see it earlier today, but appears to be there now. Definitely not supported on all clients.
@NoTwit @ChickenPwny @futurebird @maco correction, only shows up on some posts as an option.

@futurebird i heard this point about this accenualting reply guy culture from @k8em0, but probably others have come to the same conclusion! https://infosec.exchange/@k8em0/109559581709013080

@maco

Katie Moussouris (she/her)🥜👋🏼 (@[email protected])

Content warning: Mastodon meta

Infosec Exchange

@jdp23 awww she didn't have to make it about ants!

But I totally agree.

@futurebird I was originally thinking about talking about the reply guy dynamics in the same post as I discussed QTs but then realized, no, it's more than long enough already. but at least that meant i had it bookmarked!
@maco @futurebird @dalias
I saw exactly this as a newbie, just today. A reply (like this one) with multiple @'s was a question for just one person, that showed up in my feed as though they were asking me. Another person on the thread who was also not intended ended up responding. Yes, there is a learning curve for any new social media, but threads can be displayed better by applying some of your suggestions to make it more of a coherent conversation.

@maco @futurebird @dalias I have at least once hit reply, written something, posted it, then realized a couple (or more) people already did similarly and so I deleted it. And that's because I go check but checking is a pretty high friction path.

I wish I could make my instance go grab updated context on demand without having to go to another...

@aaron @maco @futurebird @dalias I think that will always be an issue, because no one has the exact same followers. I see a LOT of repeat RTs, but there’s no real way to avoid those, not without more work than it’s worth I think.

So I sigh and scroll.

@bynkii @aaron @maco @futurebird @dalias a client could dedupe them, wouldn't be perfect but could cut down on it a lot
@Paxxi @bynkii @aaron @maco @futurebird @dalias The Mastodon web interface has an option to deduplicate boosts in your TLs.

@adrienne

How do I do this? Is it in that strange contextual settings menu? Like the sounds?

@futurebird (Two posts incoming, with steps.)

So if you click the little gear on your profile, you'll get a modal popup with some preferences. Click "User Preferences" and you'll get jumped to a new screen.

@futurebird From there, click "Other" under preferences, then click "Group boosts in timelines" and then Save Changes.

@adrienne

Nice! I feel like I looked for this and couldn't find it a month ago. This is a huge quality of life improvement and probably should be the default.

@adrienne @Paxxi @aaron @maco @futurebird @dalias oh coolness, thanks!

Now of all the UI experts telling is how unnecessary QTs are would apply their expertise to mastodon’s settings…

@Paxxi @bynkii @aaron @maco @futurebird @dalias

Could?? I mean there is no question it's a bug that same toot come to timeline twice.