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

Moderation controls #41

Closed
8 tasks
garbados opened this issue Jul 5, 2018 · 7 comments
Closed
8 tasks

Moderation controls #41

garbados opened this issue Jul 5, 2018 · 7 comments
Assignees

Comments

@garbados
Copy link

garbados commented Jul 5, 2018

Users should have some control over the content they see:

  • A user may set rules to mute keywords, optionally per user. Ex: /mute [keyword] [username]
  • A user may mute another user, such as with a /squelch command.
  • A user may mute another user and any mention of them, ex: /shadowban [username] such that it is functionally equivalent to /mute [username] and /squelch [username]
  • A user may print their muting and squelching rules. Ex: /rules

Further, moderation controls should be stored as dat archives so that they can also be distributed. Consider:

  • A user may print the discovery key of their muted keywords.
  • A user may add keyword mutes by discovery key.
  • A user may print the discovery key of their squelched usernames.
  • A user may add squelched usernames by discovery key.
@garbados
Copy link
Author

garbados commented Jul 5, 2018

[Moved to first comment]

@cblgh
Copy link
Member

cblgh commented Jul 5, 2018

yes yes yes! this is a great issue, thankyou @garbados 🔥

@cblgh
Copy link
Member

cblgh commented Aug 24, 2018

I was thinking a bit about this the other day and come up with a few subtleties that would be really nice wrt muting

  • Mute user in a specified set of channels /mute [username] [channel1 channel2 channel3]
  • Unmute a user in a specified set of channels /unmute [username] [channel1 channel2 channel3]

I guess it describes a kind of subjective Access Control List for chatting

This allows for filtering your content in a way that doesn't impose restrictions on others. (Since channels act as a classifier for content.) If a person e.g. is great at technical topics, but spams a lot in the other channels then they can be muted globally and unmuted in the technical channels.

@hackergrrl
Copy link
Member

Client-side moderation would be a great fit for cabal-client!

@cblgh
Copy link
Member

cblgh commented Jan 30, 2020

hey @garbados just wanted to say that this issue inspired & informed my master's thesis, which goes into the area of networks of trust for moderation. i'm on the last leg of the thesis and will probably be done by early spring this year!!

(also we've got some stuff already done on moderation in the core but we need to bubble it up to the clients https://github.com/cabal-club/cabal-core/#moderation)

@garbados
Copy link
Author

garbados commented Mar 2, 2020

I've seen the progress on this issue and I'm really pleased and impressed! Thanks for the followup. I look forward to reading your thesis!

@hackergrrl
Copy link
Member

Closing this for now, since we have the first version of moderation released, and other tracking issues around specific tasks.

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