#QT #Mastodon #HowTo

People wanting QTs for "good" reasons, so they can add a comment to what they're boosting, just haven't learned how we've been doing it here all along, without the need for a QT function.

How it works:
1) Reply to the post you want to QT with a comment, such as "Boosting so my followers can also respond to this!" My opinion is ..."

2) Boost your REPLY. Your followers will see it in their timeline. When they click on it they'll see the OP above your reply.

Done! 🙂

Comments about not wanting to clutter the OP's thread with a side-discussion or tangent are making a good point!

What we do on Mastodon in these cases is we boost their post, then immediately make a new post of our own starting with "LB:" meaning we are referring to our last boost. It's a little more effort for your followers to scroll up to your last boost, but that's one way to handle this.

Sorry I didn't have space in my OP to mention that!

I should also mention another thing we can do if things start going off on a side tangent in someone's thread, is remove their name from any additional posts we make in that side-thread so they stop getting notifications of OT posts.

All these things may be a little more effort, but I think it's worth these work-arounds to avoid potentional QT toxicity, until we may come up with something that works even better than QTs in future releases.

@leadore

I think I like this method! Thanks for pointing this out as an option! 😎

(Boosting the above thread for my followers.😉)

#5ciFiGirl

@leadore I think the biggest problem with that (and one of the things that led to the development of QT vs just “LRT…”) is that separating the post from the context gets a little sticky in places, especially once your “LB:” post gets boosted by someone else which means the context gets further separated and harder to track down if you have a posting spree

To keep the context, you could screenshot, but that breaks all the post/user security so eww no, or include a link to the original

@leadore and a post with the link to the original in it is basically a poorly formatted / bad UX quote boost
@winnie @leadore @fade Plus, well... a QT is just a link with a comment. I'm not sure why "I liked this toot, check it out: <QT>" is so different than tooting something like, "I liked this article, check it out: <link>" - both give credit to the original author, give new readers a path to the original content, allow the author to maintain ownership of their words/edit them (as a screenshot would not!)... and both allow the QT'er to add context for their own followers.
@emery @winnie @leadore They're quite different in the places I browse. A link with a comment requires click-through, loading, often takes to a separate page where one can't favorite/boost/reply to the original, etc.; and it doesn't show what was said /until/ the click-through is done, which makes the casual browsing of microblogging experience difference. Also, there's no notice to the person being linked; a QRT let you know you /had/ been QRTed, so you could see how/by whom.
@emery @winnie @leadore Because attention/energy/focus are my heavily limited resources, the more friction gets in my way between 'a person says a thing' and 'I see a thing with its context' (or between 'I wish to share this' and 'I have shared it in a polite and context-giving way'), the more I get shaken out of being able to participate in a space. So I am probably more sensitive about friction-adding aspects than many people, for sure!

@emery @winnie @leadore For lack of a better analogy... low-friction interaction is my equivalent to alt text on images.

And I don't expect the fediverse to cater to me, just as some people don't do alt text for their own disability or mental health reasons. That's fair! But the higher friction caused by the lack of easy QRT tools is a thing that reminds me repeatedly that the local space isn't designed for people like /me/, deliberately or otherwise.

@emery @winnie @leadore (Still better for interaction than Tumblr, though. That's still the worst interface I've ever seen for a social site in a place I actually stick around.)
@fade @emery @leadore this was the “poor UX” bit I was mentioning, though I may have undersold it. It has all of the weakness of a QT and none of the strengths

@fade @winnie @leadore Ah yeah, I see what you mean and I completely agree - I just meant in terms of being able to both comment and refer to what you're commenting about at the same time, without any of that "re my last boost..." fuss.

ETA: and yes, I never got the hang of tumblr... at all.

@leadore Both are hacks to make a broken system work somewhat. Neither will work with the many non-Mastodon Fediverse implementations, neither will work within the standard, and neither will have any level of technical feasibility.
Moreover, that those things work shows one thing: the "Quote Posts cause..." debate is bullcrap. You can, in a roundabout way, do the same now. Why not have it in a clean, non-cluttering, non-falsifiable, way?
There is no reason not to have them, especially if anyone can violently hack their way around the restriction.
@leadore The problem with "LB" or "last repost" is that it can be ridiculously _difficult_ to find that last boost/repost. And by difficult I mean sometimes I fail to find it even going into the booster's timeline and searching. It gets even worse if the search starts with a later boost of your comment, or a boost of a reply to that. I'm going to give up pretty quick in those situations.

@leadore whenever you do an LB, please, *please* link back to the referenced post

because if your LB shows up on our home column, but the boost doesn't (either because someone else boosted it recently, or because our instance blocks the instance it's from), it's really confusing and disorienting
-F

@leadore thank you. Didn’t know that. Will try to do this

@leadore since quotes aren't arriving any time soon, this handy technique gets the job done in the interim.

Yes, you the reader have to click (once) to see what on earth I'm talking about, but once you do, you get to see the post, its thread and surrounding context.

It works for me!