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

Option to prioritize sync source? #449

Closed
Browsit opened this issue Mar 4, 2024 · 3 comments
Closed

Option to prioritize sync source? #449

Browsit opened this issue Mar 4, 2024 · 3 comments

Comments

@Browsit
Copy link

Browsit commented Mar 4, 2024

We have observed the following scenario for over a year now:

  1. New user joins our Discord (has no role), then
  2. user creates new website account, verifies email (has post-validation Member group), then
  3. when user links Discord, their [lack of] role appears to take priority (website gets downgraded to Unconfirmed Member group)

It seems most users have an opposite workflow, whereas they want Discord to be the deciding source. Still, we'd like to suggest a checkmark in the Group Sync page of Nameless which lets us choose which source should take priority.

@Derkades
Copy link
Member

Derkades commented Mar 5, 2024

There is currently no preferred source, it depends on whatever order syncing happens to be done in. Bidirectional sync is a hard (impossible?) problem to solve if the timestamp of each group change is not known. For example, Nameless-Link does not know that the Member role being present is more "recent" than it not being present, and thus probably preferred.

Previously, Discord groups were only synchronized as roles were added or removed. But that left people unsatisfied that roles weren't synced when a user links their account. I don't know if there is a solution...

@Browsit
Copy link
Author

Browsit commented Mar 10, 2024

@Derkades We were thinking something along the lines of letting administrators select the preferred source themselves. Here's a graphic example with radio buttons where selecting one disables the other(s):

radio

If that's something you think could work, we'd be glad to sponsor your addition of such a feature.

@Browsit
Copy link
Author

Browsit commented Oct 25, 2024

Resolved without the need for specifying source, huge thanks to @Derkades ❤️

@Browsit Browsit closed this as completed Oct 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants