Shame that they've seemed to start banning users that use alternative clients. There are some being built in Linux-native technologies, like gtkcord4, but I'm not sure I feel comfortable enough...
Shame that they've seemed to start banning users that use alternative clients. There are some being built in Linux-native technologies, like gtkcord4, but I'm not sure I feel comfortable enough touching them with my main account. I don't know how to get in contact with all of my servers, and some of them don't have living invites still out there. Wouldn't solve all the problems, gtkcord for example is against implementing calls since they're apparently complex and poorly documented. But it'd at least get you away from the known-vulnerable Electron attack surface.
For a long time it was thought that that line in the ToS was targetted at people who self-bot, who use alternative clients to do things that ordinary users can't do, but I guess that stopped being the case, if it ever was. The main developer of my favorite alternate client got banned for using it, I guess for touching an API endpoint in a way inconsistent with the official client?
But it's a shame cause alternative clients are often a huge win for Linux and people with needs/preferences that aren't quite mainstream, while the user spam bots that caused the rule in the first place are still running relatively rampant. Seems like a more effective strategy against those bots would be to block behavior. Like accounts that DM/friend request many strangers or momentarily join many servers to send a/many messages before dipping back out. Or like IPs that create many accounts. Or like blocking known datacenter IPs from registering accounts. It wouldn't entirely solve the problem, finding a new, clean-ish IP isn't too difficult, but it does add a new difficulty floor in a few ways. Heck, maybe they already try to do all that, too, I don't know.
My tiny tiny nitpick about Discord on Linux that enrages me every time that it happens is that, at some point, the version of Electron they used didn't properly implement mouse-button-back on...
My tiny tiny nitpick about Discord on Linux that enrages me every time that it happens is that, at some point, the version of Electron they used didn't properly implement mouse-button-back on Linux, so they implemented it themselves. At some later point, they upgraded to an Electron version that did support mouse-back, so now every time you press the "back" button, it goes back twice.
Came across this recently as a result of searching for ways around the problems this causes. I switched to Linux Mint just last month and while most things have worked just fine, Discord remains...
Came across this recently as a result of searching for ways around the problems this causes. I switched to Linux Mint just last month and while most things have worked just fine, Discord remains one of the few areas where I still have to deal with issues.
Unfortunately I've little reason to believe this'll be fixed soon. It got asked about last year and this was the response. Steam Deck might change the variables some, but I'm not particularly confident it'll be enough.
I wonder if their Linux user share is only 0.1% precisely because it's a bad experience? I'm pretty sure the share of Linux users in desktops and laptops more widely is a little higher than that,...
I wonder if their Linux user share is only 0.1% precisely because it's a bad experience? I'm pretty sure the share of Linux users in desktops and laptops more widely is a little higher than that, and I would've thought your average Linux user would be more likely to use Discord than your average Windows user.
As someone interested in urban design, this is the exact same excuse often used against bike lanes. No-one uses bike infrastructure because it's inconsistent and unsafe, so no effort is put into improving it because no-one uses it and it's worthless, even though many more people would choose to use it if it were better.
Personally, I just use it in the web, even on mobile. I don't trust their apps and don't need notifications, so just check in every now and then.
I've found redirecting audio input/output with Helvum to work well as a bandaid fix for audio sharing. (Thanks to @knocklessmonster for pointing me to it)
I've found redirecting audio input/output with Helvum to work well as a bandaid fix for audio sharing.
Shame that they've seemed to start banning users that use alternative clients. There are some being built in Linux-native technologies, like gtkcord4, but I'm not sure I feel comfortable enough touching them with my main account. I don't know how to get in contact with all of my servers, and some of them don't have living invites still out there. Wouldn't solve all the problems, gtkcord for example is against implementing calls since they're apparently complex and poorly documented. But it'd at least get you away from the known-vulnerable Electron attack surface.
For a long time it was thought that that line in the ToS was targetted at people who self-bot, who use alternative clients to do things that ordinary users can't do, but I guess that stopped being the case, if it ever was. The main developer of my favorite alternate client got banned for using it, I guess for touching an API endpoint in a way inconsistent with the official client?
But it's a shame cause alternative clients are often a huge win for Linux and people with needs/preferences that aren't quite mainstream, while the user spam bots that caused the rule in the first place are still running relatively rampant. Seems like a more effective strategy against those bots would be to block behavior. Like accounts that DM/friend request many strangers or momentarily join many servers to send a/many messages before dipping back out. Or like IPs that create many accounts. Or like blocking known datacenter IPs from registering accounts. It wouldn't entirely solve the problem, finding a new, clean-ish IP isn't too difficult, but it does add a new difficulty floor in a few ways. Heck, maybe they already try to do all that, too, I don't know.
My tiny tiny nitpick about Discord on Linux that enrages me every time that it happens is that, at some point, the version of Electron they used didn't properly implement mouse-button-back on Linux, so they implemented it themselves. At some later point, they upgraded to an Electron version that did support mouse-back, so now every time you press the "back" button, it goes back twice.
Came across this recently as a result of searching for ways around the problems this causes. I switched to Linux Mint just last month and while most things have worked just fine, Discord remains one of the few areas where I still have to deal with issues.
Unfortunately I've little reason to believe this'll be fixed soon. It got asked about last year and this was the response. Steam Deck might change the variables some, but I'm not particularly confident it'll be enough.
I wonder if their Linux user share is only 0.1% precisely because it's a bad experience? I'm pretty sure the share of Linux users in desktops and laptops more widely is a little higher than that, and I would've thought your average Linux user would be more likely to use Discord than your average Windows user.
As someone interested in urban design, this is the exact same excuse often used against bike lanes. No-one uses bike infrastructure because it's inconsistent and unsafe, so no effort is put into improving it because no-one uses it and it's worthless, even though many more people would choose to use it if it were better.
Personally, I just use it in the web, even on mobile. I don't trust their apps and don't need notifications, so just check in every now and then.
I've found redirecting audio input/output with Helvum to work well as a bandaid fix for audio sharing.
(Thanks to @knocklessmonster for pointing me to it)