|
Top-level
 It's important to think about security features from the perspective of how they work in reality, in addition to worst case scenarios. Worst case scenario for a quote post is exactly as bad as just a link, and not quite as bad as a screenshot. In reality, quotes are more likely to be read than links; they're most fun to post than links; and they're easier to post than either links or screenshots. 9 comments
@me Yes. He originally didn't want them because they were pretty widely used for being mean on Twitter, but since committing to them he's wanted to address these issues. But also, it does not actually seem like there's a way to do that without making it worse. If he adds all these security features that only fully-updated Mastodon servers will recognize, then people will think they're safer than they are.  @fedilore calling non-Mastodon users could be solved by a forced "DM" from the quoter @me If the contents of the post are pulled through ActivityPub and the notification is sent out as a reply with a forced tag, the risks are pretty low. But only if everybody is doing it that way. I worry that a forced tag in Mastodon-to-Mastodon quotes will give a false sense of security that it works the same way for all fedi quotes. @fedilore but quote posts are already here - and Mastodon has no power to limit how those work I could have sworn Elk Zone parsed quotes for Mastodon users, but that doesn't actually seem to be true. Does anybody know of a front-end that will allow Mastodon users to see quotes send by Akkoma and/or Misskey users? It's WelshPixie flipping me the bird that started a broader conversation about how instance-to-user moderation on fedi is basically fake, and that you should never do a user-level suspend from your instance. (I am very grateful that I have an example of this that's both so funny and relevant, while also being almost uniquely ethical for me to screenshot.) |
Gregory's Server
@fedilore maybe that's why Gargron wants to take time to do this the right way