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)

@SaltRockLamp Sorry it took a bit. Here you go: https://keybase.io/cancel/sigchain

How can I get the GPG key for this? It seems gone from SKS and I can't see anywhere on the Keybase profile page to get the author's key: https://keybase.io/cancel. The Ripcord website only has a link to the author's Keybase profile page.

If somebody has installed ripcord and is experiencing an issue that keeps you stuck in a "Routing..." state when you connect to a voice channel ... here is the solution

https://github.com/geniiii/ripcord-audio-hook/tree/linux#ripcord-audio-hook-linux

But you will have to build and install funchook manually (there is no AUR package unfortunately) and then extract the appimage file for ripcord and run the binary with that hook.so preloaded.

According to people in Discord channel for ripcord ... this fix will be included in the source code but not sure when.

Thanks! I pushed some changes.

@txtsd Hi, sure thing. A backup maintainer can't hurt : )

Can I have co-maintainer on this, please? I maintain ripcord-arch-libs.

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

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

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.

@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.