Package Details: ripcord 0.4.26-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: 19
Popularity: 0.83
First Submitted: 2018-04-12 13:36
Last Updated: 2020-06-21 07:20

Pinned Comments

Aanok commented on 2020-03-17 09:15

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. Notably, a number of such bans happened in late 2018 but, to my knowledge, were always rescinded upon appeal from the affected users. However, if your account is particularly valuable you may wish to stick to official clients to be safe.

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

Aanok commented on 2019-06-29 19:46

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

1 2 3 Next › Last »

Aanok commented on 2020-03-17 09:15

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. Notably, a number of such bans happened in late 2018 but, to my knowledge, were always rescinded upon appeal from the affected users. However, if your account is particularly valuable you may wish to stick to official clients to be safe.

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

ShayBox commented on 2020-03-16 14:09

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

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

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

Aanok commented on 2019-12-05 08:16

@ilikenwf Sure. It's done :)

ilikenwf commented on 2019-12-04 21:52

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

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

Aanok commented on 2019-06-29 19:46

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

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

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.