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

Suggestion: replace Dyno's dead chat snippet with an informational warning #115

Closed
lost-in-action opened this issue Nov 25, 2021 · 5 comments
Labels
content-filter enhancement New feature or request wontfix This will not be worked on

Comments

@lost-in-action
Copy link

image

Personally, the "dead chat" no one asked for is already annoying, and having the big Dyno message pop up looks even more annoying as it clutters the chat a little bit.

Just my suggestion, is to integrate it to cliptok: so it deletes the "dead chat" message and shows an informational warning! Informational, then auto-warn like mass-emojis. Unless it looks too restrictive for you lol (I can understand)

I believe tracking "ded chat" and "dead chat" should be enough (of course you already have the full list in Dyno).
However I understand the concern if it's harder to implement than mass-emoji detection, like anyone could just say something like "why people say dead chat?": so maybe as a reminder, you could do a full message comparison and add more sentences, or just play on chances of it to happen, by still continuing to check for messages containing those keywords.

@Erisa Erisa added content-filter enhancement New feature or request labels Nov 25, 2021
@Erisa
Copy link
Owner

Erisa commented Nov 25, 2021

This is one that would need further discussion with the mod team, I'll try and remember to relay here if we decide anything.

@dongle-the-gadget
Copy link
Contributor

dongle-the-gadget commented Nov 25, 2021

Just my suggestion, is to integrate it to cliptok: so it deletes the "dead chat" message and shows an informational warning! Informational, then auto-warn like mass-emojis. Unless it looks too restrictive for you lol (I can understand)

I think that we shouldn't just formally warn them for the first time if they don't meet a tier.
For example if the user isn't Tier 3+ and hasn't said the sentence once, send a message saying that "This violates rule 16".
If the user has Tier 3+ or has said "dead chat" once, formally warn them for rule 16.

@lost-in-action
Copy link
Author

lost-in-action commented Nov 25, 2021

I think that we shouldn't just formally warn them for the first time if they don't meet a tier.

like mass-emojis as I mentioned

@Erisa
Copy link
Owner

Erisa commented Nov 25, 2021

Mass emojis only don't warn if a) you're Tier 0 and b) haven't been pardoned before.
Anything past that one pardon will always warn, though the first infringement will also give information if its the first one (if youre not Tier 0).

@Erisa Erisa added the internal-discussion-open An internal thread is open for discussing this issue! Awaiting a conclussion from moderators... label Nov 27, 2021
@Erisa Erisa added wontfix This will not be worked on and removed internal-discussion-open An internal thread is open for discussing this issue! Awaiting a conclussion from moderators... labels Nov 29, 2021
@Erisa
Copy link
Owner

Erisa commented Nov 29, 2021

After some discussion we don't think there is anything more that can be done here, and generally would not like the idea of warning for "dead chat" messages even after pardon, since it is situational and would require moderator investigation for each case.
Deleting the message is also kind of a pain because not all of the mentions of "dead chat" are the intended recipients of the message. There are other cases where it's mentioned, and deleting those can have unreliable results.

Closing this in favour of #97 because the conclusion I came to is that we can log these to #investigations to allow moderators to more easily find and deal with these situations, and if it's decided that we want to delete the message too, that will be possible with the system proposed in #97

If you have further commeents, feel free to voice them still

@Erisa Erisa closed this as completed Nov 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content-filter enhancement New feature or request wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

3 participants