Oh for fuck's sake

Arch supremacy. My package manager handles everything.

Yeah, I'm really glad I ignored everyone's advice and went straight to Arch.
- Nowadays Arch is pretty straight forward. You have gui installers like any other distro. I never broke my Arch install in 3+ years using it.
And if it doesn't, yay does. While also triggering pacman updates at the same time.

Use the flatpak. Or 2. Use the web app (discord.com/app) Or 3. Don't use discord

I'd say webcord, iff the last option doesn't work, ofc.
- yea webcord is cool
- +1 for WebCord
At least on arch it'll tell you there's an update and prompt you to install the deb file but you can just update it with pacman and you're good to go. Usually end up doing my pacman -Syu when discord yells that it needs an update
- And on the holy Arch wiki there's a way to disable the update prompt, so you don't get locked out of discord when it has update but it hasn't arrived into the repos yet.

It has an official flatpak now

Me, running the flatpak: "Y'all are uninstalling and reinstalling .Deb files over and over?"

fuck discord

I really hope Revolt decentralizes someday (plus gets remotely relevant by usercount, no offense)
- Not gonna happen, the developer made it quite clear from the get-go. Also, their community are quite hostile against it and pretty much most FOSS stuff for some reason.
  
  I can see a fork taking what is useful about it (UI/UX) and adopting solid backends (federation, proper VoIP with screen sharing, etc.)
- I wish that would happen, or maybe if someone forked their client and hooked it up to connect to matrix home servers. The client looks great.
Use teamspeeeeeeeeee
- Let's actually not advocate for a different proprietary software, and instead advocate for FOSS solutions like Mumble.

I've used the flatpak version for years and never have any issues with updates.

Except when discord won't start because you don't have the latest version of the package(launcher that needs to be updated I think) and there is no update for your system for a while.
- This sucked, but shouldn't happen anymore now the the flatpak is official.
Launcher's broken again

the flatpak is the official distribution of the app now, so you might just want to move to that instead

EDIT: as for how well it works for those who doubt flatpak and discord in general, it works well! I've streamed video and received video streams on x11 and Wayland with no problems. Not sure if audio streaming worked in either case though.

Just use discord from the browser, the Linux app sucks anyways

The snap sucks
Or WebCord, it's the Discord web app packaged as a native application. It has pretty good support for screen sharing on Wayland and some minor privacy improvements through blocking the telemetry APIs.

I've just told mine to not check for updates.

~/.config/discord/settings.json

And change "SKIP_HOST_UPDATE" to true

That's probably a bad idea if you're not concerned about security updates?
- I'm on arch, so the package manager will update it
  
  But sometimes there is a delay between the update coming out and it hitting the repos. This just stops me having any issues inbetween
- Nah. What could possibly go wrong?
Neat! IDK why they cannot just have a APT repo.

Don't use that shit.

and if thats the only way you can talk to your friends, you can just use the web client and have at least a choice to not run chromium and have an adblocker
- Matrix bridges.
Unfortunately Mumble and TeamSpeak aren't as feature complete and user friendly

But they're the only other alternatives I've checked out
- Have you tried Matrix?
- I was there on TeamSpeak over a decade ago. It was good for its time

I've heard there's going to be an offical flatpak soon

I think it's here.
- I haven't tried flatpacks yet. How do they compare to, say, snaps in terms of storage/redundancy?

You can bump the version number in it's build_info.json file and it'll work just fine. It's weird like that. That file is in /opt/discord/resources/ for me.

I moved my non-techie friend to Kubuntu and this was one of the speedbumps we ran into. I had to set .deb files to open with something other than the KDE get new software app. I think we're using qapt-something. I wish discord didn't treat us Linux users like 2nd class citizens. They coded support for capturing OS sound for Windows, but not Linux or Mac for that matter.

As an aside, I think this situation is a microcosm for different OS's and it's users:

Windows users: We're the biggest group so sound works fine for us.

Linux users: Discord doesn't support our needs so we implemented it ourselves with discord-screenaudio.

Mac users: Discord doesn't support our needs and there's no solution to purchase so I guess we're just fucked.

To be fair, Apple made audio sharing an absolute nightmare. I have never gotten my remote control software audio to work on Mac and have tried multiple non-Crapple solutions.

Discord won't even make it as painless as possible though, and getting it set up requires downloading a third party thing now (from outside the app, before I could at least click a button inside the app).

I totally gave up a few months ago on Discord on Mac because I was sick of booting into safe mode. I'm not sure who is to blame for this but I imagine it's Apple.

I used this every time (with sudo):

#!/bin/sh
[ "$USER" != root ] &amp;&amp; { sudo "$0" &amp;&amp; exit; }
latest_version=$(
  curl -sI 'https://discord.com/api/download?platform=linux&amp;format=deb' \
  | grep '^location:' \
  | grep -m 1 -oP '\d[\d.]+\d' \
  | head -n 1
)
sed -i.bak 's/\(version.*\)[0-9]\+\.[0-9]\+\.[0-9]\+/\1'"$latest_version"'/' \
  '/usr/share/discord/resources/build_info.json'

Let's see how good the Flatpak version will be.

just fyi I moved Discord, GIMP, Obsidian, and OBS over to flatpak and my root partition jumped from 19GB to 23GB. I'm kinda sad about it tbh
- Most storage space viewers get confused by Flatpak's heavily deduplicated and compressed files, leading to them reporting way larger space than what's actually occupied on the hard drive.
- 4GB ain't to cry over, you already saved so much not using Windows :p
- First of all, stop using legacy SI units for the size of information, they only bring confusion, instead use IEC/binary units like GiB. https://en.m.wikipedia.org/wiki/Binary_prefix
  
  Second of all, I know that with Flatpak's ease of installation/runtime comes great size hit. It's great that some layers are reusable, so it's not a huge hit. Besides, with big disk size it's not really a concern now is it?
Can you break the sed command down for us sed newbies? The '-i.bak' thing is throwing me off
- Normally sed just passes along the edited text to STDout (printing in the terminal usually).
  
  With the -i option it actually changes the input files. If you add an extension immediately after the -i it apparently makes a backup of the original with that extension.

If you're on Arch, the hack where you change the version number in the build_info.json file to the current version works this time. Sometimes that hack doesn't work but this week it does.

If you're on Arch, why don't you just use the discord package from extra repositories and have discord simply update with pacman?
- The discord pacman package sometimes takes up to 2 days to update to the newest version. I'm sure if I really wanted to get into it I could use wireshark to find out which ip addresses to block with the host file to make it stop refusing to let me use it without being on the latest version but that's a lot of effort for something that only might work.

I just tried opening discord a minute ago and got that lmao. Since I am on fedora I can't use the deb file. Often pointing around on my system I found where all the discord files are and I made a script that downloads the discord .tar.gz file and moves all the files to the right places. Every time I get the prompt I run the script and it updates discord for me (:

#! /usr/bin/sh

wget -O discord.tar.gz "https://discord.com/api/download/stable?platform=linux&amp;format=tar.gz"
tar -xvf discord.tar.gz
rm -rf discord.tar.gz
sudo rm -rf /lib64/discord
sudo mv Discord /lib64/discord

Permanently Deleted

In this day and age there's still no repo for that? O_o

I use the flatpak version on my laptop and version from the repositorys on my main pc. So i either have to just update a flatpak or just do a full system update.

Use deb-get to install third party debs.

https://github.com/wimpysworld/deb-get

Seconding this, deb-get needs more love. We are using it as an official distribution for a project im in and it has been working flawlessly for me.

I just use the flatpak and it updates just fine

and i thought i was losing features by using the web version...

you can use openasar for discord and it gives you the option to not update.

One more strike for the deb monoculture (read complacency).

This isn't a deb problem. Discord just can't deb right.
- It's 100% a cultural (deb) issue. Discord wouldn't distribute deb files if users were not accustomed to downloading package installation files like savages do in Windows. As many other software vendors do with their "Linux" packages.

Armcord is better anyway

webcord

Flatpak Webcord*

install Webcord from Flatpak