Live data from Hacker News

When Discord is open in the background, NVIDIA card will not reach full speed

nvidia.custhelp.com

51–60 of 241 posts

Re: When Discord is open in the background, NVIDIA card will not reach full speed

#51
post #23

Earlier quoted context omitted.

wow had no idea there were good native apps for discord. im totally gonna try this once im home :))) thx again :)))

This apparently breaks their TOS, but I don't know if anyone got in trouble over it yet

Can you show where in the TOS third-party clients are disallowed?

(The Discord TOS does not even mention third-party clients.)

Re: When Discord is open in the background, NVIDIA card will not reach full speed

#52
post #42

Earlier quoted context omitted.

> 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…

I believe the discord app has some weird limitations around global shortcuts and push-to-talk when you use the browser tab instead of the desktop app. One use case also used to be that you would use a browser tab for one discord account and the desktop app for another, but container tabs + browser profile switching made that less necessary. And then discord eventually added support for multiple accounts.

Discord chat works fine in a browser. It is only call options (audio and video codecs?) that give headache.

Re: When Discord is open in the background, NVIDIA card will not reach full speed

#53

Earlier quoted context omitted.

I keep trying to use ripcord, but the reality is a workplace expects you to be able to jump on board every new feature that Slack adds within moments of it's release. Whether that be huddles, threads, recordings, etc. If we could pare our use of Slack down to just text, it would be a great alternative - but until them I'm stuck using the official client.

This is a real question: what are Slack huddles supposed to do? I run the native client. While anyone can start a huddle with me, I never see any UI for a huddle. All I get is the audio coming across. To end the huddle I have to force stop Slack and relaunch it.

What should be happening is a small window opens at the bottom of the left sidebar (under your channels/direct messages/apps)

The tiny window is sorta useless except for mute/hangup, but you can undock it from the sidebar and make it much larger for video chat or screensharing.

Re: When Discord is open in the background, NVIDIA card will not reach full speed

#54
post #51
post #23

Earlier quoted context omitted.

This apparently breaks their TOS, but I don't know if anyone got in trouble over it yet

Can you show where in the TOS third-party clients are disallowed? (The Discord TOS does not even mention third-party clients.)

https://twitter.com/discord/status/1229357198918197248?lang=...

> All 3rd party apps or client modifiers are against our ToS, and the use of them can result in your account being disabled. I don't recommend using them.

Re: When Discord is open in the background, NVIDIA card will not reach full speed

#55
post #42
post #19

I 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…

> The only things I can come up with are apps requiring access to outside hardware or files

That's not even 100% true either [1]. For instance, you can flash Android devices from the browser. The example in [2] talks to an attached Arduino device.

[1]: https://support.google.com/chrome/answer/12576972

[2]: https://developer.chrome.com/articles/usb/

Re: When Discord is open in the background, NVIDIA card will not reach full speed

#56
post #54
post #51

Earlier quoted context omitted.

Can you show where in the TOS third-party clients are disallowed? (The Discord TOS does not even mention third-party clients.)

https://twitter.com/discord/status/1229357198918197248?lang=... > All 3rd party apps or client modifiers are against our ToS, and the use of them can result in your account being disabled. I don't recommend using them.

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.

Re: When Discord is open in the background, NVIDIA card will not reach full speed

#57
post #18

Earlier quoted context omitted.

It's because a) people want high resolution, and b) software development is cutting corners like building on electron. Lastly, Discord has absolutely the worst software engineering behind it.

It's not about cutting corners. It's about time to effect change. It's about cross device and platform support. It's about it being easier to find developers familiar with the browser stack then native app developer. That being said I would love to have less memory allocation on my devices when effectively idle too.

Most of this is false. Ripcord achieves near-feature-parity with the official Discord and Slack apps using cross-platform desktop technologies with a fraction of the resource usage with a single developer.

Ripcord's very existence contradicts most of the claims you've made above.

Re: When Discord is open in the background, NVIDIA card will not reach full speed

#58

Discord can definitely do some strange things to your machine. I can't play DayZ when it's open, the game will not connect to any servers and errors out with this "player auth login state" message. I thought it was my internet connection but running a server locally also resulted in the same error. It took me a few months of on-and-off searching, but I eventually found a comment on a message board where someone had e…

Howdie fellow DayZ brother.

Re: When Discord is open in the background, NVIDIA card will not reach full speed

#59
post #8
post #4

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…

So then I guess the advice is, if you have to use Discord, stick to the web version?

One sticking point for people might be the way push-to-talk works for the in-browser version; the shortcut to trigger it will only work when you have the browser window focused (I think due to limitations in how browsers can capture inputs when not focused, which is a pretty reasonable policy in general). Not only does this mean you'd need to alt-tab over whenever you want to push to talk (which isn't super easy for a lot of potential use cases, like gaming), but if I remember correctly from trying this out once, you can have even more jarring bugs like "alt-tab over to the browser to hit push-to-talk shortcut, hit the shortcut, alt-tab back before releasing so you can keep talking, and then having the push to talk never deactivate because the browser didn't detect the key-up event due to a different window having focus when it happened".

Re: When Discord is open in the background, NVIDIA card will not reach full speed

#60

Earlier quoted context omitted.

We went wrong with Electron in particular: https://www.electronjs.org/ . I am convinced this framework alone is responsible for more performance loss on the desktop than any other single thing.

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…

JavaScript isn't bad. But if only it were used with native toolkits, instead of running a whole browser instance.
Post reply on HN