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

@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
Share
Share on Mastodon
Share on Twitter
Share on Facebook
Share on Linkedin
Simon Willison

@amyhoy @natematias @dansinker @jessamyn @danhon @ryanrandall @darius maybe there's a solution here where the original post author can sign their post with a "this is allowed to be QTd" flag of some sort, and well behaving clients can then refuse to render QTs of posts that don't have that flag

1
2y
JauntyWunderKind

@simon @amyhoy @natematias @dansinker @jessamyn @danhon @ryanrandall @darius there seems to be a significant threat to defederate, for certain forks from the expected/allowdd use of protocol. for instance this thread cautioning @hachyderm.io against potentially implementing full text search, which supposedly has earned defederation before. retro.social/@ajroach42/109531

1
2y
Replies