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

Reapply roles when a user leaves and joins again the server #61

Open
MarcAnt01 opened this issue Jul 7, 2020 · 5 comments
Open

Reapply roles when a user leaves and joins again the server #61

MarcAnt01 opened this issue Jul 7, 2020 · 5 comments

Comments

@MarcAnt01
Copy link

No description provided.

@Arlodotexe
Copy link
Member

We delete all user data when the user leaves the server for easy privacy protection. This is also protection to deter people from leaving and re-joining to avoid a mute.

We previously discussed adding a 30-day deletion window, where it would only delete if a user was gone for 30 days, and restore your roles (including mutes and strikes) if you rejoined.

This requires new tables in the database, which in turn requires us to wait for the ASP.NET version of the backend so we can keep EF Core in sync as much as possible.

@sylveon
Copy link

sylveon commented Dec 27, 2021

We delete all user data when the user leaves the server for easy privacy protection. This is also protection to deter people from leaving and re-joining to avoid a mute.

I don't see how this is a deterrent. If somebody leaves and rejoin, at the moment all their strikes and mutes are gone.

Information about strikes and mutes should be treated specially kept all the time even when the user leaves.

@MarcAnt01
Copy link
Author

Yes, totally agree with the point brought by @sylveon

@Arlodotexe
Copy link
Member

I don't see how this is a deterrent.
It's a soft deterrent for anyone with data they don't want deleted.

But yes, ideally we need to track all roles, infractions, etc, in the database, and restore them if someone re-joins within 30 days of leaving.

This will need to wait until after the new backend is complete.

@Arlodotexe Arlodotexe added the needs-vnext Feature can't be built on the current repo label Dec 28, 2021
@Arlodotexe
Copy link
Member

Once we complete #144, this feature can be added.

@Arlodotexe Arlodotexe removed the needs-vnext Feature can't be built on the current repo label Apr 20, 2023
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

3 participants