@slondr his public key is available on keybase (https://keybase.io/cancel/pgp_keys.asc). Try adding it from there.
Search Criteria
Package Details: ripcord 0.4.29-1
Package Actions
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) |
Dependencies (11)
- expat (expat-gitAUR)
- freetype2 (freetype2-qdoledAUR, freetype2-macosAUR, freetype2-gitAUR)
- gcc-libs (gcc-libs-gitAUR, gccrs-libs-gitAUR, gcc11-libsAUR, gcc-libs-snapshotAUR)
- glib2 (glib2-gitAUR, glib2-selinuxAUR, glib2-patched-thumbnailerAUR)
- glibc (glibc-gitAUR, glibc-linux4AUR, glibc-eacAUR, glibc-eac-binAUR, glibc-eac-rocoAUR)
- harfbuzz (harfbuzz-gitAUR)
- libdrm (libdrm-gitAUR)
- libgl (libglvnd-gitAUR, amdgpu-pro-oglp-legacyAUR, amdgpu-pro-oglpAUR, nvidia-340xx-utilsAUR, libglvnd)
- libx11 (libx11-gitAUR)
- libxcb (libxcb-gitAUR)
- zlib (zlib-ng-compat-gitAUR, zlib-gitAUR, zlib-ng-compat)
Required by (0)
Sources (3)
Latest Comments
« First ‹ Previous 1 2 3 4
rasputin commented on 2018-08-14 22:38 (UTC)
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.
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)