Ripcord Dev Logo Ripcord Development — View Ticket Login or Create Account
Ticket UUID: a76b00adde861d7ede2fac45d164a38e20ef2baf
Title: Discord verification trigger list and oddities
Status: Closed Type: Feature_Request
Severity: Minor Priority: Low
Subsystem: Discord Resolution: Not_A_Bug
Last Modified: 2021-07-05 01:08:28
Version Found In: 0.4.29
hatediscord2021-07-01 23:07:28

This is a list of oddities noticed while running Ripcord WRT Discord's phone verification triggers. It seems Discord has changed its triggers to be far more sensitive and effectively operate in a SHUT DOWN EVERYTHING mode. As giving any phone number to Discord is a major privacy concern, I would like to document a list of things to avoid while using Ripcord.

List of phone verification triggers confirmed by at least one user

  • Accepting the Discord token on Ripcord while any Discord client (both inside and outside a web browser) is running on the same external IP.
  • Sending a DM to someone outside your friend list from Ripcord.
  • Accepting a server invite (documented in 0.4.29 but notice-worthy IMHO)

This list should be expanded upon discovery of future triggers and documented accordingly.

What still works while your account is flagged for verification:

  • Receiving messages from Ripcord startup
  • Voice chat

What doesn't work:

  • Receiving message history
  • Sending messages to any party

I would like to express my gratitude to Cancel for developing this wonderful client.

cancel2021-07-05 01:08:28

This doesn't happen for everyone, or even most users. There is no way to predict how this works, and attempts to document it will end in failure or incorrect and misleading information, because it's based on some kind of heuristics and possibly machine learning and is updated and changing all the time. The only thing that is known to cause problems for more than a tiny number of users is accepting invites. Keep in mind that most people using Ripcord can still accept invites without a problem. Phone verification is very common even for people using only the Discord web or mobile clients.

I don't know why you are having so many problems. I can't predict how Discord's system works, because it's an anti-spam system, and if they documented how it worked or stopped changing it constantly, it would allow spammers to get past it. My guess is that your device fingerprint or IP address is disliked by their system for some reason.

I exchange DMs with people not on my friends list every day. I am often signed in from both my phone and Ripcord and a web browser tab all at the same time. I'm not saying this will be everybody's experience, but attempting to keep running documentation on some behavior of Discord's anti-spam system in the various regions around the world under different circumstances does not seem to me like it will lead to something useful.