Skip to content
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

Open
skobkin opened this issue Sep 27, 2023 · 7 comments
Open

[Feature] Synchronization settings and mapping #133

skobkin opened this issue Sep 27, 2023 · 7 comments
Labels
feature New feature

Comments

@skobkin
Copy link

skobkin commented Sep 27, 2023

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):

Fediseer list instance sanctions strategy
Censured suspend overwrite
Hesitated limit overwrite
Suspicious no sync
Some other list no sync

Sync setting 2 (custom)

Fediseer list instance sanctions strategy
Censured limit merge / append only
Hesitated no sync
Suspicious no sync
Some other list no sync

Sync setting 3 (custom)

Fediseer list instance sanctions strategy
Censured limit merge with deletion
Hesitated reject media overwrite
Suspicious no sync
Some other list limit overwrite

Explanation

Strategies

  • overwrite - completely synchronizes all data with fediseer by overwriting existing list entries on the instance
  • merge / append only - adds entries which do not currently exist in the list on the instance
  • merge with deletion - adds entries which do not currently exist in the list on the instance, but also removed entries which were previously synchronized from fediseed, but removed after that
  • some other strategies with another direction priorities for example

Instance sanctions

  • Limit - removed content from such instances from public timelines, but allows users to follow users from limited instance
  • Suspend - completely disables any interaction with users from suspended instance
  • Reject media - do not sync media from remote instance
  • Other domain block options which are currently present
@RikudouSage RikudouSage added the feature New feature label Sep 28, 2023
@RikudouSage
Copy link
Collaborator

Something like this is pretty much the end-goal for synchronization, though it's gonna take a while.

@github-actions
Copy link

This issue hasn't seen any activity for 30 days.
Please comment (or remove the stale label) within 5 days,
otherwise this issue will be closed.

@github-actions github-actions bot added the stale Automatically added to stale issues label Oct 29, 2023
@skobkin
Copy link
Author

skobkin commented Oct 29, 2023

Should feature request be automatically closed?

@RikudouSage RikudouSage removed the stale Automatically added to stale issues label Oct 29, 2023
@RikudouSage
Copy link
Collaborator

Well, I use it more as a reminder that says "hey, you either forgot about this issue, or it's no longer relevant".

Copy link

This issue hasn't seen any activity for 30 days.
Please comment (or remove the stale label) within 5 days,
otherwise this issue will be closed.

@github-actions github-actions bot added the stale Automatically added to stale issues label Nov 29, 2023
Copy link

github-actions bot commented Dec 4, 2023

The issue has been closed due to inactivity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 4, 2023
@RikudouSage RikudouSage reopened this Dec 4, 2023
@RikudouSage RikudouSage removed the stale Automatically added to stale issues label Dec 4, 2023
Copy link

github-actions bot commented Jan 4, 2024

This issue hasn't seen any activity for 30 days.
Please comment (or remove the stale label) within 5 days,
otherwise this issue will be closed.

@github-actions github-actions bot added the stale Automatically added to stale issues label Jan 4, 2024
@RikudouSage RikudouSage removed the stale Automatically added to stale issues label Jan 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature
Projects
None yet
Development

No branches or pull requests

2 participants