Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign up[Feature Request] Instance-level whitelist #3880
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
nightpool
Jun 22, 2017
Collaborator
Searched for a while but couldn't find an issue for this, which feels weird to me—this code has been around for a while.
|
Searched for a while but couldn't find an issue for this, which feels weird to me—this code has been around for a while. |
nightpool
added
admin support
suggestion
and removed
admin support
labels
Jun 22, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Gargron
Jul 2, 2017
Member
Whitelists go against the spirit of decentralization. If you can't start your own server and join in, but have to go through some kinda review process with every single other node, then you can't really start your own server. So whitelists will never be in the upstream repository.
|
Whitelists go against the spirit of decentralization. If you can't start your own server and join in, but have to go through some kinda review process with every single other node, then you can't really start your own server. So whitelists will never be in the upstream repository. |
thedeadparrot commentedJun 20, 2017
•
edited
Edited 1 time
-
thedeadparrot
edited Jun 20, 2017 (most recent)
It would be nice for the admins of instances that are more concerned about privacy/leaking information to be able to choose between using the instance blacklist and an instance whitelist. This is already implemented for awoo.space, the code of which is publicly available.
vahnj/mastodon@2cf7a09
vahnj/mastodon@2fca7e8
I am sure it needs to be cleaned up, have tests added, and so on, but I would love to see this feature more widely available for admins.