Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Anonymous conversations - proposal: hidden phone number agreement procedure #4068

Closed
1 task done
2072 opened this issue Mar 20, 2020 · 2 comments
Closed
1 task done

Comments

@2072
Copy link

2072 commented Mar 20, 2020

  • I have searched open and closed issues for duplicates

Feature request

It's currently not possible to hide our phone number when making a Signal call but in some cases this can be useful as long as the person receiving the call agrees to receive this specific call in the first place.

This is particularly useful in the following situation:

  • The emitting party is a psychologist or a physician who needs to practice remotely, and thus will discuss intimate and private matters with their patient, while still needing to prevent their phone number from being abused by the same patient (future unsolicited calls and messages...).
  • Any situation like the above where involved parties need to preserve their identities or their futur privacy (in most countries, cellular phone numbers are tied to the individuals' identity. ie: you can't get a phone number without giving your official identity to the network provider)
  • Completely anonymised groups (if one of the group's participant is compromised, no data in the phone would reveal the other members identity)
  • There are probably more unforeseen applications, but I find this feature is really missing in the current circumstances, where most people are resorting to standard post-card-phone calls with their physicist...

To make this possible one of the parties would initiate the procedure by generating a random string of characters (easy to type or prononce, maybe a list of words?) and the other parties, knowing this string would join (this procedure prevents invite spam).

The initiating party would be able to define the following:

  • They would be able to define the maximum number of participants
  • The duration of the agreement
  • The direction of the agreement ie: send and receive - send only - receive only, etc...
  • The type of the agreement (chat only, voice, videos, file attachements, etc...)
  • Group type (static - where group members can't change, dynamic, etc...)
  • Temporary revocability ('disable' the agreement once the counselling session is over for example...)
  • etc...

All of these parameters would be made part of the random string, which would be communicated to the other parties using another mean of communication. The fact of the parameters being part of the string would ensure their immutability and allow the involved parties to review the terms of the agreements without the need to communicate further.

The emitter will trigger the acceptance of new participants voluntarily (a bit like bluetooth pairing works) preventing unexpected guests from joining in the future.
The fact that the number of participants is encoded in the "agreement string" also guaranties the stability of the group to all parties....

Well, many other (great) features and application could come from this but for now my main concern is for private one to one conversation (physician to patient)

I'm not sure if this is at all possible given Signal's protocol but this would really be useful in many ways we can't even imagine right now...

@scottnonnenberg-signal scottnonnenberg-signal changed the title Hidden phone number agreement procedure - Anonymity preserved conversations Anonymous conversations - proposal: hidden phone number agreement procedure Mar 20, 2020
@ybabel
Copy link

ybabel commented Apr 29, 2020

I strongly agree and think that full anonymity is required for widespread adoption of signal.
I my case I immediately stopped using Signal when I saw my phone number displayed on top of a group chat. And many people told me the same.

@stale
Copy link

stale bot commented Sep 26, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

4 participants