-
Notifications
You must be signed in to change notification settings - Fork 7
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
[Feature] Synchronization settings and mapping #133
Comments
Something like this is pretty much the end-goal for synchronization, though it's gonna take a while. |
This issue hasn't seen any activity for 30 days. |
Should feature request be automatically closed? |
Well, I use it more as a reminder that says "hey, you either forgot about this issue, or it's no longer relevant". |
This issue hasn't seen any activity for 30 days. |
The issue has been closed due to inactivity. |
This issue hasn't seen any activity for 30 days. |
Introduction
Synchronization feature is a very good tool for many instances. But it has some flaws.
For example, not every instance blocks any other which is considered "bad", but still wants to use benefits of community-driven moderation lists. Some just limits them leaving their users a freedom of information and ability to still manually follow users from the "bad" instance.
So here's an idea: list mapping.
Examples
So for example you can set your own sync profile by selecting sanctions and strategies for fediseer list. For example:
Sync settings 1 (default):
Sync setting 2 (custom)
Sync setting 3 (custom)
Explanation
Strategies
Instance sanctions
The text was updated successfully, but these errors were encountered: