Change read message history permission

Comments

60 comments

  • NotKyon

    I'd like it if denying users the "read message history" permission didn't actually disable their ability to read messages that they already saw. What I want is for them to not see any messages from before they joined, wherever that permission applies.

    86
  • HDBox

    Can confirm, I'm having the same issue.

    "Read message history" should only include messages from before someone joined the server. Once joined it should show all messages (including history after the join date) which the read message permission allows to.

    32
  • MCBtv

    I showed up here because I have the same ideals. I would rather Read Message History only except message before users arrival but still can see pinned messages such as Rules, Welcome, and things of that nature.

    29
  • Yoriden

    This should definitely be a thing. It's annoying to my server's guests that they can't see messages that have been there since they joined the room, but we don't want them to be able to see the whole log of everything that was ever posted in there.

    Can we please get a change to this setting asap?

    28
  • [UNÍХ]Londongal

    I’d like the exact same functionality as above - don’t show messages before joining on a channel by channel basis please

    23
  • Cerav

    I'm also here with the same issue. There should be an option for people to see messages they already witnessed, but not the entire chat history from before they joined

    23
  • Ideally there should be two separate permissions: one that allows users to read all messages since they joined the channel, and one that allows users to read all messages from the channel's history

    Actually Discord desperately needs more permissions granularity in general. Maybe categorized into sub-permissions and such if it would help for organizational purposes.

    11
  • iwsfg

    Current implementation is pure garbage and whoever designed it had obviously never tried to use it. Because it's basically unusable.

    On desktop app if there's a channel for which you're not allowed to see message history of, it will always be marked with white dot as "has unread messages" from the startup of the app. And because of this one channel whole server also getting marked with the same white dot as well even if you read every other message in every other channel.

    You can click on it and it will go away but doing so every time you start the app is quite annoying. I found myself simply muting such channels in the end but that goes against the point of having access to a channel in the first place. Now imagine you have 3 such channels and you have to go through each one. This is pretty bad UX but even that is not the biggest issue.

    If you did not disable notifications and still pay attention to them you also have to remember to visit that channel once after launching the app just to be able to see new messages posted in the channel. Every time you launch Discord. You have to do this so discord properly loads channel into memory and subscribes to new messages with their content, not just to the event of a new messages being posted in a channel. Otherwise you get notified of the fact that new message were posted, but when you navigate to the channel discord will try to load them from history along with older messages and that request will get denied. If you didn't open channel before conversation started - you missed it.

    This permission does no good in its current form and solves no problem, it just breaks stuff. Please, either just remove it completely or redesign the darn thing. It has been suggested to you numberous times here and in other places - best you can do is to replace it with a dropdown "Access to message history" with options "from the dawn of time", "since joining the server", "for messages posted within recent X hours/days".

    And then teach your unread messages service or client to play nicely with messages outside that range so it wouldn't mark channels as unread due to the messages from the past that user won't be able to see anyway.

    And while we're on that note, please split "Enable Unread Messages Badge" setting in two so it would be possible to keep it enabled for unread @mentions and Direct Messages but disabled for general unread messages (those marked with white mark in the app). Tired of seeing red dot on the tray icon all the time. Desired behavior is how taskbar icon already works on Windows10 when that setting is off and if icon overlays can be used but people rocking "small taskbar icons" don't get icon overlays and icon in tray just never gets marked with the red dot.

    11
  • Type-R

    Why there are no comments from discord support here? And why this issue is still not adressed? Biggest problem with app is not getting fixed for years?

    8
  • Rui Santos

    This is the most annoying "BUG" on discord right now! This is unbeliavable and doesn't make sense for anyone! Please fix it as soon as possible!

    7
  • ShaltNotProsper

    Permissions changes recomnended from the perspective of a System Administrator:

    (note that the server permissions are separate, but consolidated for brevity, and generally are a no/yes, which corresponds to deny/allow)

    Primary permission:
    Read Chat History of channel or server (allow/inherit/deny)

    granular permissions:
    1. Read chat history since beginning of channel or server history (deny/inherit/allow)
    2. Read pinned messages since permission granted to channel (deny/inherit/allow, becomes active only after 1 is allowed/inherited)
    3. Read history since permission granted to channel (deny/inherit/allow)
    4. Read pinned messages since beginning of channel or server history (deny/inherit/allow, becomes active only after 3 is allowed/inherited)

    6
  • ShayminPlays

    Maybe they should also make it so you can see pinned messages even if Read Message History is disabled.

    5
  • Darth_Vader

    Are they coming out with a fix for this soon? 

    4
  • Kota

    It's ridiculous that this isn't a thing. I keep running into these stupid little issues with Discord that I can't believe haven't been addressed yet. 

    4
  • Yoriden

    It's not that this thread is assuming anything, it's that what we are requesting would be more useful and that the way it functions now is notably broken for reasons that others have touched upon.

    4
  • iwsfg

    > Is there a way I can fix this?

    Either wait for eternity until Discord Staff notices this topic or ask server owners to allow access to Message History. As I explained above it's pretty much broken by design.

    3
  • iwsfg

    You all are asking for the stupidest thing ever. I just want users without access to history to see pinned messages 

    Then go create your own suggestion and comment on it how it's the greatest feature ever.

    This one is about "Message history" permission being essentially broken by design in many many ways and pretty much useless

    3
  • jarieljimenez

    I'd love to see this change implemented; the feature as it is right now seems useless and this just makes far more sense to me.

    2
  • Hedius

    Yeah, it is not possible for me to hide the previous chat from new clan members. We do not want to expose our full chat history to new members. Especially our admin chats need special care. That's the point of this thread...

    2
  • Sool

    been 2 years and there's still nothing...
    support team or whatever lol they only care about fixing some useless nitro features, meanwhile this one right here has been bugging people for like 3 years and made so many problems for people.

    2
  • RobotPenguin

    Its been like 3 years and nothing has changed what

    2
  • River

    It's honestly weird that this topic has had little to no attention from anyone from discord's team, it has been an issue in multiple servers I've been a part of. With how Discord works, the current setting makes no sense except for a select few people. Most users have multiple servers that they are part of, and at times will balance multiple conversations between channels and servers.

    The issue I'm running into now is that I have a server that is trying to implement a vetting channel because there have been issues with things like raids in the past, as well as just wanting to ensure some people that join the server genuinely want to be a good part of the community. We don't want anyone just to be able to scroll through everyone else's vetting questions, because we have a measure to make sure people respond a certain way if they have read the rules, so we don't want any new member seeing that, and just copying it rather than going to read the rules. So the chat history should be turned off for them, but then if they click out of the channel, they won't see if a mod tells them that they need to answer something better or read the rules. The other option is for us to purge the channel every time someone is vetted, but we would like to keep track of the answers for record keeping. 

    The point that I'm getting is that the setting just does not make sense for how discord works. The app is made for users to chat in multiple communities, and if that chat history is turned off, it isn't possible for someone to partake in an ongoing conversation in any productive way... I don't imagine it would be a tremendous undertaking to implement the setting people have described here... Discord's indifference upsets me, especially after three years of complaints made here over something that honestly feels like it should be common sense. If they can make all sorts of additions to profile customization for nitro users, then surely they should be able to implement something like this that improves the user experience for all of its users.

    2
  • Query

    i would really like this change!!

    1
  • The Gold DJ1

    This NEEDS to be a thing. I admin many discord servers and its quite a pain when new users join into the server and can view messages made months ago about specific topics. On top of this, simply because especially in admin channels we make decisions in my gaming groups which we dont want people to be a part of but when they get added to the admin voting group they can see the entire chat log unless we purge it every time. 

    1
  • JRMBelgiumTwitch

    Please add this feature!

    1
  • OppressorB

    Same issue here. I think an option underneath the "Can't see message history" which allows you to setup how long messages in that channel will be visible for that role would solve the problem. Please implement this feature as this is essential for limited permissions.

    1
  • Bellustrious

    Any update from support regarding whether this feature will be adjusted as requested? Timeline regarding implementation?

    1
  • Puny

    I just tried to use this permission on my discord but I had to turn it off again.  Even if they were existing members all the previous history blanks and every time they leave and return it is blank, so any conversations that happened between when they left and when they join are gone.

    Surely this should just work that from the point of joining they have no history and from then on they can see everything.

    1
  • Aoiro

    DISCORD WHY ARE YOU NOT LOOKING AT THIS AND LISTEN TO ALL THESE PEOPLE IT'S BEEN OVER A YEAR SINCE IT WAS BROUGHT UP, FIX IT ASAP PLEASE!

    1
  • Erudian

    In certain channels, it may be appropriate for new members to be able to see all of the history - for example, "help" or "FAQ" channels. Being able to search through "years and years" of posts to find an answer to your own question would be beneficial. In other channels - such as those for server mods, guild "officers", etc. - you may not want new members to be able to see the discussions that took place prior to them joining the channel (maybe some of those discussions were about the new arrival). I can definitely see applications for both of these use-case scenarios.

    What I don't think is at all intuitive is the current implementation of the "Read Message History" permission (see my "rant" above).

    1

Please sign in to leave a comment.