@numist @film_girl honestly at that point its just playing silly games, hydrate the Post and add a option to Quote from the Boost button and call it a day.
At this point the only reason I haven't done it is because I have concerns of how to do it without causing a height changing timeline, which I try to avoid as much as possible.
@paul @film_girl Totally, but I'd argue silly games are good; they're how these things become real—like how Twinkle caused location tagging to become part of Twitter.
wrt height-changing do you mean because the cells would load previews asynchronously? Definitely seems like care would be needed to avoid weird scroll offset woe.
@numist @film_girl yes Twitter had an API that allowed you to load up to 100 Tweets at a time, that'd be really good for something like this as we could hydrate the Posts at load time and base layout, etc.. on that.
Here you can only load one post at a time by ID, which makes that kind of technique very problematic. What if there's 20 quotes in your timeline.
@paul Well, previews don't have to be restricted to toots, as long as you can determine whether there are social card tags in the head then you're good (quote-tooting a tweet being the most obviously useful possibility).
Unless the site is too slow but in the incremental model you'd need heuristics on when to give up on a preview regardless.
@film_girl @paul If this was twitter, I'd probably QT this post and say something like...'mastodon avoided QT for reasons'...maybe address those reasons and stop trying to recreate twitter. It really was horrible.
We have an opportunity to rethink all of that, here, now. And build something so much better, together.
@film_girl @paul 2012 was 11 years ago! Why should mastodon jump to support it after just a few months of migrations?
You can still do a QT here, you just have to go through the step of getting the link to the post you want to comment on.
The tech isn't the problem.
@kristinHenry @film_girl @paul The primary value I see in quote-posts, is the ability to add commentary/context. If I really need to, I can "copy link" and paste it.
Like this:
https://mastodon.social/@film_girl/109759044241043089
So I get the primary value, commentary, for two addition taps.
But while I see the utility, I agree with the current Mastodon way, that twitter-style quote-tooting, on balance, is a net negative.
Engage and reply to the original poster is better.
@paul @film_girl I kinda like an idea I saw a while ago, that we should replace QTs with a RT of the original with a specific reply in-line below it.
That'd give the original post more prominence and would hopefully encourage people to read the original neutrally *before* they see the reply of the re-poster.
@uliwitness @paul @film_girl Here’s a proposal for a #QuoteReply (or Boost-and-Reply) function: https://fediphilosophy.org/@keithwilson/109456249890156614.
This avoids some of the worst aspects of QTs while remaining compatible with the existing Mastodon API since you can already boost a reply along with the original toot. All that’s needed from clients is to display both together in the timeline (which @elk already does) and a way to boost-and-reply to a toot as a single action; e.g. via a long press on the ‘boost’ button. Bingo!
The negative aspects of #QuoteTweets could be fixed by making them work more like replies. A #QuoteReply, if you will. Instead of appearing as a new toot unconnected with the original, the original toot would be boosted with a comment added that is shown both to followers and, crucially, the original poster. Subsequent replies would then go to both in the usual way so that the conversation is not forked. (The same should also happen with regular boosts IMO.) #Mastodon #UX #QuoteToot #noxp
@paul @film_girl I’ve been messing with a userland alternative using open graph/oEmbed tags. Real QT’s would be better, but it’s something.
I’m still messing with the right tag combo to make it render best across the most clients. Looks great in ivory, but not everywhere else.
https://qt.any.dev/https://mastodon.social/@film_girl/109759044241043089
@paul I think a potential client-side solution for now would be to render links to other posts as one would have rendered a quote post. Current link preview to other Mastodon posts isn’t great.
And add a button that composes a new post with the link already added.
Edit: oops just saw this has already been suggested
@MikeBeas @film_girl I think it would actually prevent some abuse.
In the abusive cases at hand, quoting is a coward move at best. With a direct reply, you have to own your words. What is more abusive? Saying something to someone in their back or saying it to their faces?
@rmondello @film_girl @cdf1982 same. that’s it exactly!!!
i get the whole big thing about QTs — and i’m happy for many of the strong mastodon opinions. those opinions are saving our collective asses from the fascist billionaire hellsite right now. but, like… babies and bathwater, you know???!!!
i hope we somehow find a nice balance.
:-)
@film_girl Near as I can tell the whole “quote-tweeting is a significant driver of abuse” thing is taken as a given but has never been quantified.
It’s not clear to me that the kinds of people who’ve received abuse-by-QT wouldn’t have received similar abuse without it, all other things being equal.
Re: Toot turns Mastodon posts into images that are suitable for quote posts. Images are accompanied by attribution to the original author and an alternative text. Images created by Re: Toot can also be shared to other social networks and messaging services. To create an image from a Mastodon post,…
@film_girl not building the feature because it’ll be abused is nonsensical. In that case we shouldn’t have boosts or replies either.
Instead of worrying if QT’s will be used for abuse, we should focus on building better moderation tools (like opting out of being quoted)