More control over message history viewing privileges for servers and users
Server side:
Viewing message history is currently an all-or-nothing privilege. Anyone added to your server with message history permissions in a channel can see every message ever sent to that channel, years before they joined. This is a big privacy concern for servers that aren't publicly advertised/built around pulling in a lot of new members -- i.e., friendgroup/small clan servers. If you care about controlling who can go back and view years of conversations with your friends (not to mention scraping/uploading the logs elsewhere), you can't bring anyone into your server without devising convoluted tiered friendship roles.
Message history from time not spent in the server is where the problem is, I think.
So I suggest:
- Permission add: Can view message history outside of date ranges spent in the server (if you weren't in the server when the message was sent, you can't see the message)
- Permission add (optimistic goal): Can view message history from time spent without a role that could view message history
Removing the current message history permission renders Discord pretty unusable, so it's unfit for this use.
User side:
When you leave a server, your message history be there forever, viewable by anyone who ever joins the server. It'd be nice to have some granular control on those messages or at least some information regarding those messages.
Some desired features here, ranked by my estimation on importance:
- List of servers you've ever sent messages in
- View number of messages sent by you on a server by server basis
- Search among messages you've sent (across servers, within specific servers)
Everything else has been pretty great role-wise! If parts of this are duplicated, please let me know.
-
[USER SIDE]
Both features actually exist without you suggesting it except that the permission to Read Message History is only set to view-able at the time the user is online.
Its the Read Message History function that needs tweaking and adding your suggestion will just conflict the current permissions available to us.
1
Por favor, entrar para comentar.
Comentários
1 comentário