-
Notifications
You must be signed in to change notification settings - Fork 9
Command proposal: !watch #91
Comments
I don't think the time stuff would be that good. You don't really know when a user will stop behaving in a certain way, so manual closing is pretty much the only way. |
I think the best way to handle the channel name would be to make the name like “watch-x” x being a number (maybe increment, doesn’t really matter) and then set the channel topic to the user since that is not public via the API |
@clbx Actually, it is. Both the audit log and custom clients. |
I guess then a pinned topic or embed the messages directly to make it obvious where they are coming from. It’s also possible to “spoof” where the messages are coming from right? As if that user was saying it in the channel |
Kind of, yeah. You can use webhooks to change the pfp and username, however it won't have the correct person when you click the name/pfp. |
I think embedding the messages would be better since then you could jump to them in conversation. There's no way for a user to see if their messages are being embedded elsewhere via the API is there? |
No, I don't think so. Webhooks also support hyperlinks, so you could use their pfp + their name and have a (source) hyperlink at the end. |
Is there a specific goal about the user not being able to know he's being watched? If not, what's wrong with just doing it for hard to moderate users, or another role with a similar purpose? |
Personally I think it doesn't matter, but to quote ElKowar: "I'd rather have people misbehave while I'm active than when I'm not". |
If people know they're being watched they often change their behaviour. But honestly, I'm unsure if that's a pro or con. It's on a fine line. |
!watch <user> [time]
would create a hidden channel where all actions of the given user are logged. This would make it easier for the mod-team to keep an eye on people, reducing moderation effort.
Watching would stop either after the time ran out, or after a mod runs
!watch stop
in the given channel.The channel should stay existant until the mod runs
!watch close
.Possible, major issue
Thanks to discord being rather weird, hidden channel names are still visible to the API as well as the audit-log. This would mean that anyone using a customized client could see the hidden channels, which would in many cases cause people to behave very differently and is also likely to cause regular discussions and complaints by community members.
Possible solutions
The text was updated successfully, but these errors were encountered: