{"p":"","h":{"iv":"ROXSYW+cfvEbFHu5","at":"ocxplSQjdRC3tXEtB/9/wg=="}}

@natematias @dansinker @jessamyn @danhon @ryanrandall @darius and even when QTs are vehicles for harassment (which i’ve seen), being able to control who can QT you or turning QTs off is a pretty solid solution. one twitter never offered.

twitter never was big on preventing harassment; you can’t even opt out of being put on lists, which are definitely an abuse vector worse than QTs.

1
Share
Share on Mastodon
Share on Twitter
Share on Facebook
Share on Linkedin
Simon Willison

@amyhoy @natematias @dansinker @jessamyn @danhon @ryanrandall @darius I've been having trouble imagining how a permission-based mechanism for quote tweeting could work on Mastodon though, given its federated nature

Once the ability to render QTs is added, how could the software prevent rogue forks from transmitting a message with a QT without first gaining permission from the quoted user?

2
2y
Replies