I've been thinking the privacy settings here aren't actually privacy settings (because they're full of holes) but rather *exposure* settings. I think exposure controls (i.e how many people *will likely* see things) are great, but maybe the features should be renamed to reflect that they control exposure, not privacy (i.e. how many people *can possibly* see things)?
@abgd I really like this. It's highly misunderstood how privacy works here, for example most people don't know that a rogue server could just grab your atom feed rather than politely notifying you that it's following you as mastodon does.
@geekylou@abgd But that also true to birdsite for example, right? I can download all the 3000 last tweets of a person without even get to their profile.
@geekylou@eyal I dunno about birdsite. It's just that good #infosec requires clear communication with users, and right now Mastodon is kind of misleading. It has amazing exposure controls but basically zero *privacy*.
@geekylou@abgd does that hold true for private posts (aka DM)? i guess intra-instance private posts stays within the instance (probably admin has access and could theoretically read you private posts to a user on the same instance). what is the weakest link for a private post accross two instances? can a third instance see it? or it again depends only on admin of the recepient's server?
@abgd@novadeviator thought I'd get back to you on this. So private(direct) posts are only sent to their recipients server and aren't visible on the main atom feed for a user. There is also an atom feed on the private post but that is only visible to the sender if they are logged in.
meta, privacy/exposure Afficher plus
@geekylou @abgd But that also true to birdsite for example, right? I can download all the 3000 last tweets of a person without even get to their profile.