You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The main idea here is to give to the people a way to mute someone without active admins in the chat at the time.
The /cancel command should be available to non-admin users.
The /cancel command should be a reply to controversial message of ban-candidate (like a /mute command).
The /cancel command should make a Poll with some funny title and question like We must mute the toxic! Shall we? with two options: yes or no. And post it Poll like a replay to controversial message (if it's possible).
We need to figure out when we can know the decision was made. >50% votes when got more than 10 votes? IDK
We need a way to avoid abusing and flood by this new powerful tool. (Trusted list #244)
We need choice a default ban duration.
For example:
Alice: girls can't code!
Bob: wtf??? girls can everything!
Bob (reply to Alice msg): /cancel
Nyan: *post a poll with two variants: ban or not ban Alice*
... *ppl are voiting...*
Alice has been banned for 1 hour \ 1 day \ 1 week
To avoid misunderstanding, I believe we should make in like a mode. So, if smth goes wrong, we just turn the cancel mode off.
The text was updated successfully, but these errors were encountered:
Macht dem Volk!
The main idea here is to give to the people a way to mute someone without active admins in the chat at the time.
/cancel
command should be available to non-admin users./cancel
command should be a reply to controversial message of ban-candidate (like a/mute
command)./cancel
command should make a Poll with some funny title and question likeWe must mute the toxic! Shall we?
with two options: yes or no. And post it Poll like a replay to controversial message (if it's possible).For example:
To avoid misunderstanding, I believe we should make in like a
mode
. So, if smth goes wrong, we just turn the cancel mode off.The text was updated successfully, but these errors were encountered: