Arch Linux User Repository

I'd like to ask everyone to please refrain from discussing Discord TOS in the comments.

There is nothing in the Discord TOS mentioning (never mind forbidding) third-party clients like Ripcord, while there is wording against hacks of the official ones, like BetterDiscord. Some Discord employees have made off-hand remarks in fora, tweets and support email chains asserting otherwise but have always either failed to follow up with exact information when pressed or retracted their statements. We believe they mistook Ripcord for the likes of BD in good faith.

That said, while Discord Inc. isn't intent on preventing the use of Ripcord, accessing the service through it may increase your likelihood to get flagged for automatic bans in certain conditions. As of early 2021, there is anecdotal evidence of increased false positives for all users of the service, including Ripcord users. If your account is particularly valuable, you may wish to stick to the official clients for extra precaution.

Please allow this comment section to remain dedicated to technical issues with the package.

PGP KEY

The SKS infrastructure should not be considered secure and it is strongly advised to refrain from using it to retrieve any kind of information.

Instead of importing the PGP key for the package as usual by gpg --recv-keys, new users should access the developer's profile on Keybase, check his identity and follow the instructions shown by clicking on the key signature.

(the final command is omitted from this comment on purpose)

That's a good point. However, mucking about with it a little, it seems to me it should then be enough to set both Plugins = /usr/lib/qt/plugins and Libraries = /usr/lib without the need to touch any other files at all. This doesn't work, do you know why? I'm not familiar with how Qt handles loading at large.

On the wiki, as an alternative to setting the env variable, you can also mention you can edit qt.conf in the ripcord folder and change the plugins path entry.

Yup, I've been able to replicate. I've added a few notes on the wiki page, thanks :)

Cinnamon DE, fcitx , Mozc

That's interesting, what is your setup? I've been using ibus and libkkc with the bundled libs without issue.

For reference: you also need to use system QT if you want to use an IME.

I did rather extensive testing, libsodium doesn't need to be linked at all from what I can tell, it was resolved simply by using only system qt libraries. Regardless, the comment may be useful for future viewers, I have no interest in maintaining a package as I'm not regularly on my computer :P

Actually, the only library you need to simlink is libsodium (just to create an alias to circumvent a naming mismatch), you can just delete all others and the dependencies will be resolved anyways. You can also simply delete the plugins folder if you set QT_QPA_PLATFORM_PLUGIN_PATH=/usr/lib/qt/plugins.

Sorry, but I will not integrate this workaround in the package. Qt has a record of suddenly breaking ABI compatibility and I am not willing to do the work necessary to maintain ripcord working against arbitrary versions of the library. It works easily now, but at a certain point it will not anymore.

I do invite you to make a second package either patching this or in conflict with it that uses system libs :) But please do make sure you can maintain it for a while if you do.

So there's a bug if you use certain emoji sets with the font rendering. https://dev.cancel.fm/tktview?name=d2dc78360c This can be fixed by just using the system QT, it's worked fine for me and was suggested to me by the dev. Basically you softlink

libQt5Concurrent.so.5
libQt5Core.so.5
libQt5DBus.so.5
libQt5Gui.so.5
libQt5Multimedia.so.5
libQt5MultimediaWidgets.so.5
libQt5Network.so.5
libQt5OpenGL.so.5
libQt5Svg.so.5
libQt5WebSockets.so.5
libQt5Widgets.so.5
libQt5X11Extras.so.5
libQt5XcbQpa.so.5

in /usr/lib/ripcord/lib to the system ones, then replace the plugins dir in /usr/lib/ripcord with a softlink to /usr/lib/qt/plugins, this would require adding a few qt packages to the depends. I did actually have a patch for the PKGBUILD but lost it unfortunately.

Would be nice if we could somehow hack this to use KDE's File Open dialog instead of the barebones Qt one.

And while you're at it, devendoring all the libraries from the AppImage may be a good idea too.