signalapp / signalapp/Signal-Android

Persistent silent registration failures especially in Russia (alternate registration/validation flows desperately needed) + Censorship circumvention basically fully suppressed

Open
#14,767 5 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

wontfix
Dominant language
Kotlin
Stars
29.4k
Forks
6.9k
PR merge metrics
No merged PRs in 30d

Description

Guidelines
  • I have searched open and closed issues for duplicates
  • I am submitting a bug report for existing functionality that does not work as intended
  • This isn't a feature request or a discussion topic
Bug description

I understand there is a balance to be struck between resilience to spam and various hijack attempts and friendliness to VPNs but at this point of time registering to a Russian number to a VPN is borderline impossible

The userbase most desperately in need of secure comms solution is also being drastically underserved by Signal as a result

As a separate but related issue, censorship circumvention in-built Signal solutions are at this point being reliably detected by russian state censors and suppressed (VLESS+ based VPNs still work and are good at their job, but using VPN massively aggravates the registration problems, likely due to "dirty" IPs)

Signal users in authoritarian countries like russia desperately need

  1. better registration flow (this is, dare I say, critical, because at this point I can't even onboard new moderately technical users who know how to use a VLESS VPN, they can get to "internet at large" but not register Signal, because, well, the registration flow stalls or rejects them)

  2. better censorship circumvention (alternatively, a closer integration to powerful VLESS+ and similar VPN providers who have a solid track record of breaking out from under technologically powerful authoritarian regimes like russia and china)

Screenshots

No response

Device

No response

Android version

No response

Signal version

No response

Link to debug log

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file, test, entry point, device details, version, or debug log is named. Start by reviewing the Android registration and censorship-circumvention flows, then reproduce registration with a Russian number and VPN; done would require an agreed scope and evidence that the selected flow works reliably.

Written by the indexing model from the issue text.

Assessment

Tech stack
kotlin
Domain
authentication, mobile, networking, security
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.