SoniEx2
/
rust.clogsim
1
0
Fork 0
Code Issues 3 Pull Requests Releases Wiki Activity

Security considerations: Recommend user and channel modes for clogs #3

New Issue
Open
opened 2019-01-14 01:49:28 +01:00 by SoniEx2 · 0 comments
SoniEx2 commented 2019-01-14 01:49:28 +01:00
Owner
Copy Link

For better GDPR compliance, users should be able to set modes to enable/disable clogs. (opt-out is probably okay, as no data is collected until the user starts sending channel messages. do talk to a lawyer instead, tho.)

Additionally, for better spam control, channel operators should be able to set modes to enable/disable clogs for each channel user. (This would work similar to op/voice/etc.)

For better GDPR compliance, users should be able to set modes to enable/disable clogs. (opt-out is probably okay, as no data is collected until the user starts sending channel messages. do talk to a lawyer instead, tho.) Additionally, for better spam control, channel operators should be able to set modes to enable/disable clogs for each channel user. (This would work similar to op/voice/etc.)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
master
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: SoniEx2/rust.clogsim#3
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?