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.
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.
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.)
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.
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.
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
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.
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.
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.
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?
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.
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 (:
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.
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.