100% of signal scrapped - ugh
Large-Scale Abuse of Contact Discovery in Mobile Messengers [pdf]
11–20 of 206 posts
Re: Large-Scale Abuse of Contact Discovery in Mobile Messengers [pdf]
#12One which I allow to be shared with apps And another which are my contacts I use with my dialer.
People don't need their messenger apps knowing the phone number of their doctor
Re: Large-Scale Abuse of Contact Discovery in Mobile Messengers [pdf]
#13There needs to be two lists of contacts. One which I allow to be shared with apps And another which are my contacts I use with my dialer. People don't need their messenger apps knowing the phone number of their doctor
When an app requests permission to all photos the user gets the option to share only a subset of photos with the app. (This subset can be different for each app.)
Re: Large-Scale Abuse of Contact Discovery in Mobile Messengers [pdf]
#14There needs to be two lists of contacts. One which I allow to be shared with apps And another which are my contacts I use with my dialer. People don't need their messenger apps knowing the phone number of their doctor
Re: Large-Scale Abuse of Contact Discovery in Mobile Messengers [pdf]
#15Earlier quoted context omitted.
For those who want end-to-end encrypted messages, it's a feature that the server doesn't have a persistent archive of message history. Wire messages are on the server for a few weeks, long enough to relay those messages to transiently offline devices. Telegram is great at what it does, different use case from Wire.
Matrix does have end-to-end encrypted persistent history.
Re: Large-Scale Abuse of Contact Discovery in Mobile Messengers [pdf]
#16https://www.bellingcat.com/resources/how-tos/2019/04/08/usin...
Re: Large-Scale Abuse of Contact Discovery in Mobile Messengers [pdf]
#17There needs to be two lists of contacts. One which I allow to be shared with apps And another which are my contacts I use with my dialer. People don't need their messenger apps knowing the phone number of their doctor
* telegram uses an "internal" contact list for which one can add contacts via the desktop client and then works as expected.
* whatsapp let's the user freely initiate contact by phone numbers, but then only shows the number (no name).
don't know about signal.
Re: Large-Scale Abuse of Contact Discovery in Mobile Messengers [pdf]
#18I'm not saying this is good. But merely that assuming otherwise was always a bit naive. Now in terms of GDPR and similar laws in the US, leaking information via a scrapable API is of course still a problem.
Re: Large-Scale Abuse of Contact Discovery in Mobile Messengers [pdf]
#19Did not know that taking over a WhatsApp account is that easy.
Re: Large-Scale Abuse of Contact Discovery in Mobile Messengers [pdf]
#20There needs to be two lists of contacts. One which I allow to be shared with apps And another which are my contacts I use with my dialer. People don't need their messenger apps knowing the phone number of their doctor
An alternative would be to make it similar to the iOS photo gallery permissions: When an app requests permission to all photos the user gets the option to share only a subset of photos with the app. (This subset can be different for each app.)