-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Private" Posts / Visibility Settings #33
Comments
"we can't implement private posts like on twitter" - why is this? It's a basic safety feature all other social networks have. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The equivalent to Twitter's private account or Circles has been requested by a lot of users. While we can't implement private posts like those of Twitter, we can at least ask servers and clients to comply with visibility settings, like on Mastodon.
This has to be implemented before federation opens, as we should expect this to work immediately without having to wait for other servers to update.
Implications
A user can add friction to minimize the chances of unintended audiences seeing their posts.
Details
Feasibility
We should be able to filter out private posts that should not be visible to a users on multiple levels, including Feed Generators and Clients. This would hopefully ensure that visibility settings remain valid even if a layer doesn't comply. It would be better if people are able to report and block servers that do not comply with the visibility settings.
Basically, if we can implement Opt-In Hashtags, this could work as well.
Perhaps also related to #28.
The text was updated successfully, but these errors were encountered: