Right click on the channel icon and go to 'Notification Settings' rather than clicking on 'Server Mute'. From there you can choose whether a mention (inc./ex. @everyone/@here) counts and whether mobile notifications are enabled.
As for the client you may want to try Ripcord[0]. It uses less memory though I'm not sure you can mute people the same way. While I don't think it's ever enforced, technically using other clients is against the Discord ToS.
Either way there are plenty of reasons not to use Discord if you can.
That is one of my main gripes with Discord, in addition to:
1. Uploading photos/videos through the mobile app stops if you lock your phone or background the app. No other modern app exhibits this behavior.
2. Blocking users shows a large "BLOCKED" message, with no option to truly block them.
As far as server/channel mute - believe me, I have tried every option, including your suggestions. It works for most servers but I have 2 that I can't mute no matter what I try.
This does not solve my mute issue, but great to know that this might be the cause! Thanks for this.
The desktop client had issues with FPS drop in games. You can disable Hardware Acceleration in the Appearance section and your FPS returns to normal. I guess you'd have to find the browser setting, maybe you can do it per tab?
I'm in about 20+ channels and memory on windows is 135MB
My Discord is sitting at about half a gig and I'm in 12 or so servers.
I did some brief testing and it looks like the usage is depending on your servers activity. If people are posting lots of gifs the memory goes up. I got up to 300 going to some of the communities I just follow, rather than actively participate in daily. When I went back to my "main server" where my close friends are (we dont gif much) it slowly droppped back down to ~110. I guess eventually once it releases the in memory fluff it will drop back down.
Does doing this help your memory usage? https://support.discordapp.com/hc/en-us/articles/206342858--...
I'll be honest and say I've never used roles so I'm sure you are right. That is unfortunate
It's been open in a tab for a week, on a fairly high-volume server (dozens of channels, thousands of users) and FireFox reports (about:memory) 150MB usage for that tab.
Your experience seems to mirror my Slack experience though, I have to kill that tab about every other day due to live leaks.
IRC had issues but at least the clients were decent.
Sure people will rush to say the IRC clients of old opened in .02 nanoseconds after you thought about checking your channels, but that's not useful compared to the fact Discord out of the box has more functionality than an IRC client could ever hope to provide, and looks pleasing to the eye while doing that.
- persistent chat history
- mobile client
- a sane registration / nickname reservation method
Perhaps requests like those don't match your own priorities, but I don't think they're wrong.
That's kind of misleading. "Server-side chat history" is more accurate.
IRC logs are more persistent. It's possible to go back and check them at any time. If I've read the messages, I know they've been logged, and I know they'll still be there.
Discord history, on the other hand, can be deleted from the servers at any time. Often when you go back to double check something that was written previously, it's not there any more.
[1] - https://thelounge.chat/
[2] - https://github.com/thelounge/thelounge
[3] - https://convos.by/
FWIW, there are also shiny front-ends to NNTP. That would actually be a great way to have a threaded messaging system and attachments.
- I can't mute some channels completely. I have raised bug reports, tried all the various options, researched everything I could find in Google about this issue. Bottom line is that "mute" is taken by Discord to be "only mute, unless I think you need to hear this", with no way to fully mute a channel.
- I only use Discord in browser and it now has a complete and very distracting screen refresh every few seconds.
- It is a memory pig in browser and my browser seems to become unstable after a short time, while running Discord in one of the tabs.