Package Details: ripcord 0.4.29-1

Git Clone URL: https://aur.archlinux.org/ripcord.git (read-only, click to copy)
Package Base: ripcord
Description: Qt-based Discord and Slack client
Upstream URL: https://cancel.fm/ripcord/
Licenses: custom
Submitter: 2xsaiko
Maintainer: Aanok (rasputin)
Last Packager: Aanok
Votes: 39
Popularity: 1.27
First Submitted: 2018-04-12 13:36 (UTC)
Last Updated: 2021-10-16 12:45 (UTC)

Pinned Comments

Aanok commented on 2020-03-17 09:15 (UTC) (edited on 2021-02-28 13:59 (UTC) by Aanok)

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.

Aanok commented on 2019-06-29 19:46 (UTC) (edited on 2020-02-01 07:59 (UTC) by Aanok)

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)

Latest Comments

Aanok commented on 2021-10-16 12:45 (UTC)

@lmartinez-mirror none other than my oversight. It's fixed now, thank you.

lmartinez-mirror commented on 2021-10-16 04:02 (UTC)

Is there a reason why git tracks this package's metadata (.BUILDINFO, .MTREE)?

hugojmaia commented on 2020-09-10 11:15 (UTC) (edited on 2020-09-10 11:39 (UTC) by hugojmaia)

OK. If anyone comes with a similar problem of pacman not reading the keys correctly, here's how I got it working: Assuming keys were imported. Git clone with the link provided above. cd ripcord makepkg After it's done go to ripcord folder and double click the .tar.xz file so pacman can install it. I've never had this much headache getting generic errors.

Aanok commented on 2020-09-10 10:32 (UTC)

@hugojmaia The import command works fine on Arch. Maybe Manjaro doesn't use gpg's keyring?

Push come to shove you can always build by hand passing --skippgpcheck to makepkg. But you should try not to.

hugojmaia commented on 2020-09-09 11:56 (UTC)

So I did the instructions on Keybase to add the keys from Cancel and Pamac still errors out with: Ripcord-0.4.26-x86_64.AppImage ... FAILED (the public key ABBAD1CB484F53024CF5868B69332F9203F21F5C is not trusted) Which is Cancel's fingerprint.

I'm running manjaro btw.

Aanok commented on 2020-03-17 09:15 (UTC) (edited on 2021-02-28 13:59 (UTC) by Aanok)

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.

shaybox commented on 2020-03-16 14:09 (UTC)

This does violate the TOS just in the way it authenticates, the only way it would be allowed was if it used oauth, which doesn't provide enough access to an account to act as a client.

Sentry commented on 2020-01-31 23:55 (UTC)

btw this Software does not violate the Discord Terms of Service, though they reserve the right to ban you at any time so you aren't safe (ever)

LothaireFR commented on 2020-01-29 09:54 (UTC)

Illegal piece of software as it's against Discord's ToS.

Aanok commented on 2019-12-05 08:16 (UTC)

@ilikenwf Sure. It's done :)

ilikenwf commented on 2019-12-04 21:52 (UTC)

Could you please sed the Ripcord.desktop file to remove the full path? I use firejail and have /usr/local/bin/ripcord setup but have to manually remove the path to the bin itself so that my firejailed binary is run instead.

madmalkav commented on 2019-07-16 17:25 (UTC)

Sorry for my late reply. Unfortunately, I also unfamiliar with QT inner workings.

Aanok commented on 2019-06-29 19:46 (UTC) (edited on 2020-02-01 07:59 (UTC) by Aanok)

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)

Aanok commented on 2019-06-27 07:25 (UTC)

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.

madmalkav commented on 2019-06-24 17:26 (UTC)

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.

Aanok commented on 2019-05-15 13:16 (UTC)

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

madmalkav commented on 2019-05-12 21:02 (UTC)

Cinnamon DE, fcitx , Mozc

Aanok commented on 2019-05-12 19:34 (UTC)

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

madmalkav commented on 2019-05-12 13:25 (UTC)

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

raku-cat commented on 2019-05-06 03:20 (UTC)

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

Aanok commented on 2019-05-05 09:33 (UTC)

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.

raku-cat commented on 2019-05-05 02:57 (UTC)

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.

CounterPillow commented on 2018-12-24 16:24 (UTC)

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.

rasputin commented on 2018-08-14 22:38 (UTC)

@slondr his public key is available on keybase (https://keybase.io/cancel/pgp_keys.asc). Try adding it from there.

slondr commented on 2018-08-14 22:32 (UTC)

Version 0.3.1-1 fails integrity verification. Seems the PGP signature changed or was added or something. The public key with the signature 69332F9203F21F5C fail to be received from gpg or pacman-key using --recv-key(s).

Aanok commented on 2018-06-16 19:57 (UTC)

It did :) Thanks!

2xsaiko commented on 2018-06-16 19:41 (UTC)

I'm not using this anymore, you can take it over. I hope this worked, haven't done this before

Aanok commented on 2018-06-12 16:37 (UTC)

@therealfarfetchd Are you still around? If you're having trouble I can volunteer to take over the package from you.