| 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: | LicenseRef-ripcord |
| Submitter: | 2xsaiko |
| Maintainer: | Aanok (rasputin, txtsd) |
| Last Packager: | txtsd |
| Votes: | 43 |
| Popularity: | 0.000003 |
| First Submitted: | 2018-04-12 13:36 (UTC) |
| Last Updated: | 2024-11-08 17:03 (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.
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.
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.
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)
Illegal piece of software as it's against Discord's ToS.
@ilikenwf Sure. It's done :)
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.
Sorry for my late reply. Unfortunately, I also unfamiliar with QT inner workings.
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)
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)