There are many problems with discord, and GPU is not the worst one. Discord Snap has to block many unusual activities, but I still see these: * attempt to `ptrace` processes all the time; * using 99% CPU; * to work Discord needs some non-standard interfaces to be connected; * Discord tries to track which other programs you run by default and shares it. * too frequently restarting desktop integration snap until the lo…
I yarn for the simpler days of IRC, Pidgin and Skype where these apps ran fine on a 1GHz Pentium 3 chip with 256MB of RAM. Now you need a quad core 3GHz chip and 8GB RAM just to run a chat app reliably. Where did we go wrong?
When Discord is open in the background, NVIDIA card will not reach full speed
111–120 of 241 posts
Re: When Discord is open in the background, NVIDIA card will not reach full speed
#112Earlier quoted context omitted.
Agreed and I’d go a step further and say that this was inevitable with the advent of JavaScript. Humans are lazy (efficient?) and will always gravitate to the easiest tool for the job. If “the job” is just to make a functional chat app, it becomes wildly efficient to simply wrap your web app in electron. I’ve done it to an existing web app and it took less than a day to suddenly have “native” .dmg and .exe to distrib…
Alright so I gotta ask, now that two people are saying they yarn for the days of IRC. I thought maybe it was a different idiom I was missing, but searching for "idiom yarn for" doesn't get me anywhere. Just a typo/misspelling of "yearn"?
Re: When Discord is open in the background, NVIDIA card will not reach full speed
#113Earlier quoted context omitted.
That's not the TOS. That's a 3 year old tweet with multiple people in the replies asking to cite where in the TOS it says that, and no further reply from the official account.
Keeping it vague means they can simply shrug and refer to being able to ban accounts at their own discretion
like reddit, bans are entirely meaningless
Re: When Discord is open in the background, NVIDIA card will not reach full speed
#114Earlier quoted context omitted.
I yarn for the simpler days of IRC, Pidgin and Skype where these apps ran fine on a 1GHz Pentium 3 chip with 256MB of RAM. Now you need a quad core 3GHz chip and 8GB RAM just to run a chat app reliably. Where did we go wrong?
Skype was always a bloated mess. My gaming/friend group started off with it, but between the hard cutoff at 8? 16? people in a call, Skype taking up approximately half of our typically 4 GB of RAM, and people discovering you could crash people's clients by sending them several GB of ;) emoticons which, when rendered into smiley images, would overwhelm most anybody's computer, we ended up switching to Mumble, where we…
It used p-2-p over port 80 so it would always reach its destination no matter the firewall rules on your network, and it allowed file transfers up to 2GB(!) in size, in 2005(!).
There were no better alternatives at the time.
Re: When Discord is open in the background, NVIDIA card will not reach full speed
#115There are many problems with discord, and GPU is not the worst one. Discord Snap has to block many unusual activities, but I still see these: * attempt to `ptrace` processes all the time; * using 99% CPU; * to work Discord needs some non-standard interfaces to be connected; * Discord tries to track which other programs you run by default and shares it. * too frequently restarting desktop integration snap until the lo…
Re: When Discord is open in the background, NVIDIA card will not reach full speed
#116Re: When Discord is open in the background, NVIDIA card will not reach full speed
#117Earlier quoted context omitted.
I use ripcord for discord and slack bonus it's a native app and uses about 20mb of ram.
I would love to use Ripcord but I can't find any information on noise suppression/voice focus and that's a requirement for me as I play without push to talk and on mouse and keyboard so all those key presses get sent through to those in my channel. With the 1st party app, despite other issues, none of my key presses come through for people in my channel.
https://www.nvidia.com/en-us/geforce/broadcasting/broadcast-...
Re: When Discord is open in the background, NVIDIA card will not reach full speed
#118I work at discord and specifically have been tracking this issue. We recently released support for AV1 hardware encoding for go live streams. However, the process of probing the GPU for what codecs it supports has triggered a latent nvidia driver bug. We are releasing a workaround some time today, and nvidia is releasing a driver update to address this issue as well.
Apologies for any inconvenience this has caused.
Re: When Discord is open in the background, NVIDIA card will not reach full speed
#119I exclusively use Discord in a browser tab. I simply won't use a dedicated app for anything that can be done in a web browser.
> I simply won't use a dedicated app for anything that can be done in a web browser. In 2023, what app experience is still impossible to do in the browser? The only things I can come up with are apps requiring access to outside hardware or files. There are now several entirely unique ways in which a AAA gaming experience could be delivered to a client browser. If we can ship resident evil frames to a Chromebook at 30…
Re: When Discord is open in the background, NVIDIA card will not reach full speed
#120Earlier quoted context omitted.
I used to be able to do that on my 25MHz Amiga with 10MB of RAM. Static absolute task priority scheduling is actually a very good way to ensure your MP3 will play without stuttering.
Some of those more-obscure operating systems simply felt like magic. Refresh a webpage on Windows or Linux, mp3 you're playing pops and skips about half the time. Mouse just seemingly-randomly becomes unresponsive. BeOS on the same machine? Hard to load the system enough that playback isn't smooth, and input was only rarely anything other than instant-feeling. Closest I've seen to that recently is iOS, but it cheats…
Not my experience. Windows (and IIRC MacOS too) always had a great disk I/O scheduler that prioritized audio related tasks so I never had mp3s pop or skip on me, no matter how hard I was thrashing my spinning rust disks back then.
Linux was the one where I noticed this issue intensely back then as the schedulers used by mainstream distros were all tuned for server/mainframe workloads.