Private posts is planned, but it’s not trivial. Mastodon can’t exactly brag about their nonintuitive technically just not broadcasted posts, where multiple implementations keep making private messages publicly discoverable due to bugs.
What kind of implementations do you mean? The last time I heard of such a thing (a few years ago), it was fixed within a few hours, and was on a dev instance
Federation requires openness and that goes badly with secrecy. You can argue that one has to trust instance owners anyway, but knowing the users and not just the tallies makes uncovering manipulation easier.
It’s doable with E2E encryption, but lots of social stuff in large groups requires coordination which is incredibly hard to with a server that has no knowledge of what the data is because it can’t index anything, etc.
Private posts is planned, but it’s not trivial. Mastodon can’t exactly brag about their nonintuitive technically just not broadcasted posts, where multiple implementations keep making private messages publicly discoverable due to bugs.
What kind of implementations do you mean? The last time I heard of such a thing (a few years ago), it was fixed within a few hours, and was on a dev instance
Currently Lemmy is leaking likes via the API even if they only should be available to the user’s host and community host server
Federation requires openness and that goes badly with secrecy. You can argue that one has to trust instance owners anyway, but knowing the users and not just the tallies makes uncovering manipulation easier.
It’s doable with E2E encryption, but lots of social stuff in large groups requires coordination which is incredibly hard to with a server that has no knowledge of what the data is because it can’t index anything, etc.
How?
https://peergos.org/