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

[Bug]: Actions on Members who left Failing #19

Closed
0xEmma opened this issue May 6, 2023 · 9 comments · Fixed by #28
Closed

[Bug]: Actions on Members who left Failing #19

0xEmma opened this issue May 6, 2023 · 9 comments · Fixed by #28
Assignees
Labels
bug Something isn't working

Comments

@0xEmma
Copy link
Collaborator

0xEmma commented May 6, 2023

Describe the bug

When trying to add a note/ban users who have left the server, this action fails

To reproduce

User leaves server
try to add note / ban / whois / history

Expected behavior

Note gets added / user gets banned & command should accept INT input

Also should be able to run /whois on an HTB ID, or a user who has left the server, which is not possible.

same with history not allowed to be run on left users

Relevant log output

No response

Additional context

No response

@0xEmma 0xEmma added the bug Something isn't working label May 6, 2023
@0xEmma
Copy link
Collaborator Author

0xEmma commented May 6, 2023

From what we had to do previously, iirc its a matter of if get_user fails for the guild, just use their UID to insert into the database, or get the user object instead of member object

@dimoschi
Copy link
Contributor

dimoschi commented May 6, 2023

@0xEmma so we want to able to ban users who may not be members?

@0xEmma
Copy link
Collaborator Author

0xEmma commented May 6, 2023

Correct, we should be able to ban/pull history/add notes/whois on non-members. This can be useful is several cases and is an urgent issue.

This is needed because:

  • User spams and leaves: cant ban(this is the issue that prompted this, we're unable to ban a user who spammed DM's soliciting illegal services)
  • User files a ban appeal: unable to pull up history
  • User joins on new account, unable to whois or pull history to remove token
  • Unable to add note on user who left

@dimoschi dimoschi linked a pull request May 10, 2023 that will close this issue
7 tasks
@daanbreur
Copy link

Personally also find that pretty useful. But how does that work with GDPR?

@0xEmma
Copy link
Collaborator Author

0xEmma commented May 23, 2023

Personally also find that pretty useful. But how does that work with GDPR?

GDPR has no effect with this. We're not storing any PII afaik, this is just standard discord bot functions.
Feature is not just useful, it is needed for core functionality.

@daanbreur
Copy link

You are storing the full infraction history together with a user. That is PII.
Even Ubisoft and others have to delete in-game saves after 2 years cause GDPR, and save games really don't have much PII.

@0xEmma
Copy link
Collaborator Author

0xEmma commented May 23, 2023

You are storing the full infraction history together with a user. That is PII. Even Ubisoft and others have to delete in-game saves after 2 years cause GDPR, and save games really don't have much PII.

Open a separate issue for that, please. This ticket just adds the ability to add/ban data from left users, data is still stored on users who had data attached when joined.

@daanbreur
Copy link

True, I just was asking about the part of adding to left users. Which you might to think twice about if this really is against GDPR, else this feature is fine and useful

@0xEmma
Copy link
Collaborator Author

0xEmma commented May 23, 2023

True, I just was asking about the part of adding to left users. Which you might to think twice about if this really is against GDPR, else this feature is fine and useful

As i said, please raise a separate issue for this. While i agree that GDPR can be a concern on users who have left, this PR doesnt change the fact we store infractions on users who have left if that data was added while theyre in the server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants