-
Notifications
You must be signed in to change notification settings - Fork 12
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
Comments
From what we had to do previously, iirc its a matter of if |
@0xEmma so we want to able to ban users who may not be members? |
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:
|
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. |
You are storing the full infraction history together with a user. That is 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. |
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. |
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
The text was updated successfully, but these errors were encountered: