You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i personally believe that as soon as OEmbed is added to mastodon, quote tweeting should exist (maybe even before)
the reasoning behind this is that this will effectively create quote-tweeting. this means that if quote-tweeting is not supported in a way that supports notifications and discoverability for the person who posts the toot, then it is more likely to cause abuse than actually supporting a quote-tweet feature.
i would suggest making a quote tweet be noticeable as a reply to the post, that also has the link and OEmbed view of the toot. this would happen even if the user just copied a link to the toot, ideally, to make it so people can't effectively do what not implementing quote-toots would do, namely, allow people to know when people are talking about them.
i understand that this might be hard or even impossible to enforce on clients that aren't the main web-client/app you are working on, and i don't know what the solution there is
The text was updated successfully, but these errors were encountered:
i personally believe that as soon as OEmbed is added to mastodon, quote tweeting should exist (maybe even before)
the reasoning behind this is that this will effectively create quote-tweeting. this means that if quote-tweeting is not supported in a way that supports notifications and discoverability for the person who posts the toot, then it is more likely to cause abuse than actually supporting a quote-tweet feature.
i would suggest making a quote tweet be noticeable as a reply to the post, that also has the link and OEmbed view of the toot. this would happen even if the user just copied a link to the toot, ideally, to make it so people can't effectively do what not implementing quote-toots would do, namely, allow people to know when people are talking about them.
i understand that this might be hard or even impossible to enforce on clients that aren't the main web-client/app you are working on, and i don't know what the solution there is
The text was updated successfully, but these errors were encountered: