Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.mobile.android > #155420 > unrolled thread
| Started by | micky <NONONOmisc07@fmguy.com> |
|---|---|
| First post | 2026-08-31 09:01 -0400 |
| Last post | 2026-09-09 12:53 +0200 |
| Articles | 13 on this page of 173 — 13 participants |
Back to article view | Back to comp.mobile.android
How does whatsapp work? micky <NONONOmisc07@fmguy.com> - 2026-08-31 09:01 -0400
Re: How does whatsapp work? Maria Sophia <mariasophia@comprehension.com> - 2026-08-31 09:20 -0600
Re: How does whatsapp work? micky <NONONOmisc07@fmguy.com> - 2026-09-01 00:51 -0400
Re: How does whatsapp work? "Carlos E.R." <robin_listas@es.invalid> - 2026-08-31 20:37 +0200
Re: How does whatsapp work? micky <NONONOmisc07@fmguy.com> - 2026-09-01 01:01 -0400
Re: How does whatsapp work? "Carlos E.R." <robin_listas@es.invalid> - 2026-09-01 09:44 +0200
Re: How does whatsapp work? "s|b" <me@privacy.invalid> - 2026-09-01 12:47 +0200
Signal (was: Re: How does whatsapp work?) Nuno Silva <nunojsilva@invalid.invalid> - 2026-09-01 12:21 +0100
Re: Signal (was: Re: How does whatsapp work?) "s|b" <me@privacy.invalid> - 2026-09-01 16:30 +0200
Re: Signal Maria Sophia <mariasophia@comprehension.com> - 2026-09-01 19:15 +0200
Re: Signal "Carlos E.R." <robin_listas@es.invalid> - 2026-09-01 19:32 +0200
Re: Signal Maria Sophia <mariasophia@comprehension.com> - 2026-09-01 21:25 +0200
Re: Signal "Carlos E.R." <robin_listas@es.invalid> - 2026-09-01 21:26 +0200
Re: Signal Maria Sophia <mariasophia@comprehension.com> - 2026-09-01 21:53 +0200
Re: Signal "Carlos E.R." <robin_listas@es.invalid> - 2026-09-02 11:20 +0200
Re: Signal Maria Sophia <mariasophia@comprehension.com> - 2026-09-02 17:10 +0200
Re: Signal "Carlos E.R." <robin_listas@es.invalid> - 2026-09-02 20:37 +0200
Re: Signal Maria Sophia <mariasophia@comprehension.com> - 2026-09-02 21:23 +0200
Re: Signal "Carlos E.R." <robin_listas@es.invalid> - 2026-09-02 21:36 +0200
Re: Signal Maria Sophia <mariasophia@comprehension.com> - 2026-09-02 22:31 +0200
Re: Signal "Carlos E.R." <robin_listas@es.invalid> - 2026-09-02 22:32 +0200
Re: Signal Maria Sophia <mariasophia@comprehension.com> - 2026-09-03 02:40 +0530
Re: Signal "Carlos E.R." <robin_listas@es.invalid> - 2026-09-02 23:24 +0200
Re: Signal Maria Sophia <mariasophia@comprehension.com> - 2026-09-03 11:39 +0845
[OT/Meta] Trolling (was: Re: Signal) Nuno Silva <nunojsilva@invalid.invalid> - 2026-09-03 11:37 +0100
Re: [OT/Meta] Trolling Maria Sophia <mariasophia@comprehension.com> - 2026-09-04 03:43 +0930
Re: Signal Nuno Silva <nunojsilva@invalid.invalid> - 2026-09-03 11:28 +0100
Re: Signal Maria Sophia <mariasophia@comprehension.com> - 2026-09-04 02:31 +0930
[OT] "trolling" (was: Re: Signal) Nuno Silva <nunojsilva@invalid.invalid> - 2026-09-02 11:18 +0100
Re: [OT] "trolling" Maria Sophia <mariasophia@comprehension.com> - 2026-09-02 17:10 +0200
Re: [OT] "trolling" "Carlos E.R." <robin_listas@es.invalid> - 2026-09-02 20:25 +0200
Re: [OT] "trolling" Maria Sophia <mariasophia@comprehension.com> - 2026-09-02 22:28 +0200
Re: [OT] "trolling" "Carlos E.R." <robin_listas@es.invalid> - 2026-09-02 22:33 +0200
Re: [OT] "trolling" Maria Sophia <mariasophia@comprehension.com> - 2026-09-03 02:41 +0530
Re: [OT] "trolling" "Carlos E.R." <robin_listas@es.invalid> - 2026-09-02 23:25 +0200
Re: [OT] "trolling" Maria Sophia <mariasophia@comprehension.com> - 2026-09-03 11:35 +0845
Re: [OT] "trolling" Chris <ithinkiam@gmail.com> - 2026-09-09 20:07 +0000
Re: [OT] "trolling" "Carlos E.R." <robin_listas@es.invalid> - 2026-09-10 09:27 +0200
Re: [OT] "trolling" "Carlos E.R." <robin_listas@es.invalid> - 2026-09-02 20:24 +0200
Re: [OT] "trolling" Frank Slootweg <this@ddress.is.invalid> - 2026-09-02 18:56 +0000
Re: [OT] "trolling" Maria Sophia <mariasophia@comprehension.com> - 2026-09-02 21:18 +0200
Re: [OT] "trolling" "Carlos E.R." <robin_listas@es.invalid> - 2026-09-02 21:38 +0200
Re: [OT] "trolling" Maria Sophia <mariasophia@comprehension.com> - 2026-09-02 22:27 +0200
Re: [OT] "trolling" "Carlos E.R." <robin_listas@es.invalid> - 2026-09-02 22:33 +0200
Re: [OT] "trolling" Maria Sophia <mariasophia@comprehension.com> - 2026-09-03 05:58 +0845
Re: [OT] "trolling" "Carlos E.R." <robin_listas@es.invalid> - 2026-09-02 23:25 +0200
Re: [OT] "trolling" Maria Sophia <mariasophia@comprehension.com> - 2026-09-03 11:36 +0845
Re: Signal Andy Burns <usenet@andyburns.uk> - 2026-09-01 18:59 +0100
Re: Signal Maria Sophia <mariasophia@comprehension.com> - 2026-09-01 21:18 +0200
Re: Signal Nuno Silva <nunojsilva@invalid.invalid> - 2026-09-02 11:11 +0100
Re: Signal Maria Sophia <mariasophia@comprehension.com> - 2026-09-02 17:18 +0200
Re: Signal "Carlos E.R." <robin_listas@es.invalid> - 2026-09-02 20:28 +0200
Re: Signal Maria Sophia <mariasophia@comprehension.com> - 2026-09-02 21:25 +0200
Re: Signal "Carlos E.R." <robin_listas@es.invalid> - 2026-09-02 21:38 +0200
Re: Signal Maria Sophia <mariasophia@comprehension.com> - 2026-09-02 22:32 +0200
Re: Signal "Carlos E.R." <robin_listas@es.invalid> - 2026-09-02 23:00 +0200
Re: Signal Maria Sophia <mariasophia@comprehension.com> - 2026-09-03 02:39 +0530
Re: Signal Maria Sophia <mariasophia@comprehension.com> - 2026-09-01 19:05 +0200
Re: Signal "Carlos E.R." <robin_listas@es.invalid> - 2026-09-01 19:13 +0200
Re: Signal Maria Sophia <mariasophia@comprehension.com> - 2026-09-01 20:52 +0200
Re: Signal "Carlos E.R." <robin_listas@es.invalid> - 2026-09-01 21:27 +0200
Re: Signal Maria Sophia <mariasophia@comprehension.com> - 2026-09-01 21:50 +0200
Re: Signal "Carlos E.R." <robin_listas@es.invalid> - 2026-09-02 11:20 +0200
Re: Signal Maria Sophia <mariasophia@comprehension.com> - 2026-09-02 17:11 +0200
Re: Signal Nuno Silva <nunojsilva@invalid.invalid> - 2026-09-02 18:50 +0100
Re: Signal "Carlos E.R." <robin_listas@es.invalid> - 2026-09-02 20:30 +0200
Re: Signal Maria Sophia <mariasophia@comprehension.com> - 2026-09-02 21:34 +0200
Re: Signal "Carlos E.R." <robin_listas@es.invalid> - 2026-09-02 21:51 +0200
Re: Signal Maria Sophia <mariasophia@comprehension.com> - 2026-09-02 22:34 +0200
Re: Signal "Carlos E.R." <robin_listas@es.invalid> - 2026-09-02 23:00 +0200
Re: Signal Maria Sophia <mariasophia@comprehension.com> - 2026-09-03 06:00 +0845
Re: Signal Andy Burns <usenet@andyburns.uk> - 2026-09-03 09:42 +0100
Re: Signal Maria Sophia <mariasophia@comprehension.com> - 2026-09-04 03:13 +0930
[OT] "trolling" (was: Re: Signal) Nuno Silva <nunojsilva@invalid.invalid> - 2026-09-04 13:12 +0100
Re: [OT] "trolling" (was: Re: Signal) micky <NONONOmisc07@fmguy.com> - 2026-09-08 21:04 +0300
Re: [OT] "trolling" (was: Re: Signal) Jim Jackson <jj@franjam.org.uk> - 2026-09-08 19:32 +0000
Re: [OT] "trolling" (was: Re: Signal) micky <NONONOmisc07@fmguy.com> - 2026-09-09 08:21 +0300
Re: Signal Maria Sophia <mariasophia@comprehension.com> - 2026-09-02 21:31 +0200
Re: Signal "Carlos E.R." <robin_listas@es.invalid> - 2026-09-02 21:51 +0200
Re: Signal Maria Sophia <mariasophia@comprehension.com> - 2026-09-02 22:27 +0200
Re: Signal "Carlos E.R." <robin_listas@es.invalid> - 2026-09-02 22:34 +0200
Re: Signal Maria Sophia <mariasophia@comprehension.com> - 2026-09-03 02:37 +0530
Re: Signal Nuno Silva <nunojsilva@invalid.invalid> - 2026-09-03 11:55 +0100
Re: Signal Maria Sophia <mariasophia@comprehension.com> - 2026-09-04 02:44 +0930
[OT] "trolling" (was: Re: Signal) Nuno Silva <nunojsilva@invalid.invalid> - 2026-09-04 12:39 +0100
Re: Signal micky <NONONOmisc07@fmguy.com> - 2026-09-09 08:44 +0300
Re: Signal "Carlos E.R." <robin_listas@es.invalid> - 2026-09-04 09:56 +0200
[OT] "trolling" (was: Re: Signal) Nuno Silva <nunojsilva@invalid.invalid> - 2026-09-06 10:17 +0100
Re: [OT] "trolling" "Carlos E.R." <robin_listas@es.invalid> - 2026-09-06 13:59 +0200
Re: [OT] "trolling" Nuno Silva <nunojsilva@invalid.invalid> - 2026-09-06 13:34 +0100
Re: [OT] "trolling" "Carlos E.R." <robin_listas@es.invalid> - 2026-09-06 20:07 +0200
Re: [OT] "trolling" micky <NONONOmisc07@fmguy.com> - 2026-09-09 08:51 +0300
Re: [OT] "trolling" "Carlos E.R." <robin_listas@es.invalid> - 2026-09-09 12:49 +0200
Contacts AJL <noemail@none.com> - 2026-09-09 09:55 -0700
Re: Contacts Nuno Silva <nunojsilva@invalid.invalid> - 2026-09-10 10:16 +0100
Re: Contacts Maria Sophia <mariasophia@comprehension.com> - 2026-09-10 09:30 -0700
Re: Contacts AJL <noemail@none.com> - 2026-09-10 17:49 +0000
Re: Contacts Maria Sophia <mariasophia@comprehension.com> - 2026-09-10 21:33 -0700
Re: Contacts AJL <noemail@none.com> - 2026-09-11 06:54 +0000
Re: Contacts Maria Sophia <mariasophia@comprehension.com> - 2026-09-11 01:24 -0600
Re: Contacts AJL <noemail@none.com> - 2026-09-11 11:09 -0700
Re: Contacts Frank Slootweg <this@ddress.is.invalid> - 2026-09-11 18:23 +0000
Re: Contacts Maria Sophia <mariasophia@comprehension.com> - 2026-09-11 12:56 -0600
Re: Contacts Frank Slootweg <this@ddress.is.invalid> - 2026-09-11 19:37 +0000
Re: Contacts Maria Sophia <mariasophia@comprehension.com> - 2026-09-11 12:46 -0600
Re: Contacts AJL <noemail@none.com> - 2026-09-11 12:48 -0700
Re: Contacts Maria Sophia <mariasophia@comprehension.com> - 2026-09-11 21:59 -0230
Re: Contacts AJL <noemail@none.com> - 2026-09-11 19:12 -0700
Re: Contacts Maria Sophia <mariasophia@comprehension.com> - 2026-09-12 01:31 -0100
Re: Contacts Frank Slootweg <this@ddress.is.invalid> - 2026-09-12 13:00 +0000
Re: Contacts AJL <noemail@none.com> - 2026-09-12 08:32 -0700
Re: Contacts Maria Sophia <mariasophia@comprehension.com> - 2026-09-12 17:31 +0000
Re: Contacts AJL <noemail@none.com> - 2026-09-12 13:05 -0700
Re: Contacts Frank Slootweg <this@ddress.is.invalid> - 2026-09-12 18:00 +0000
Re: Contacts AJL <noemail@none.com> - 2026-09-12 13:05 -0700
Re: Contacts micky <NONONOmisc07@fmguy.com> - 2026-09-17 13:33 +0300
Re: Contacts AJL <noemail@none.com> - 2026-09-17 12:30 +0000
Re: Contacts Siard <saylor259@mailbox.org> - 2026-09-17 15:12 +0200
Re: Contacts AJL <noemail@none.com> - 2026-09-17 16:12 +0000
Re: Contacts Maria Sophia <mariasophia@comprehension.com> - 2026-09-17 18:48 +0200
Re: Contacts Arno Welzel <usenet@arnowelzel.de> - 2026-09-18 10:04 +0200
Re: Contacts Arno Welzel <usenet@arnowelzel.de> - 2026-09-18 10:00 +0200
Re: Contacts AJL <noemail@none.com> - 2026-09-18 10:58 -0700
Re: Contacts micky <NONONOmisc07@fmguy.com> - 2026-09-17 13:26 +0300
Re: Contacts Nuno Silva <nunojsilva@invalid.invalid> - 2026-09-11 00:30 +0100
Re: Contacts micky <NONONOmisc07@fmguy.com> - 2026-09-12 21:58 +0300
Re: Contacts AJL <noemail@none.com> - 2026-09-12 13:16 -0700
Re: Contacts micky <NONONOmisc07@fmguy.com> - 2026-09-13 05:06 +0300
Re: Contacts micky <NONONOmisc07@fmguy.com> - 2026-09-13 05:15 +0300
Re: Contacts AJL <noemail@none.com> - 2026-09-12 20:40 -0700
Re: Contacts Maria Sophia <mariasophia@comprehension.com> - 2026-09-13 11:22 +0545
Re: Contacts AJL <noemail@none.com> - 2026-09-13 06:05 -0700
Re: Contacts Maria Sophia <mariasophia@comprehension.com> - 2026-09-13 06:54 -1000
Re: Contacts AJL <noemail@none.com> - 2026-09-13 14:17 -0700
Re: Contacts Maria Sophia <mariasophia@comprehension.com> - 2026-09-15 00:50 +0000
Re: Contacts Frank Slootweg <this@ddress.is.invalid> - 2026-09-13 19:02 +0000
Re: Contacts AJL <noemail@none.com> - 2026-09-13 14:17 -0700
Re: Contacts Maria Sophia <mariasophia@comprehension.com> - 2026-09-14 21:56 -0300
Re: Contacts AJL <noemail@none.com> - 2026-09-20 00:15 -0700
Re: Contacts micky <NONONOmisc07@fmguy.com> - 2026-09-23 21:02 +0300
Application identification on Motorola Android (was: Re: Contacts) Nuno Silva <nunojsilva@invalid.invalid> - 2026-09-13 08:11 +0100
Re: Signal Nuno Silva <nunojsilva@invalid.invalid> - 2026-09-02 21:12 +0100
Re: Signal Maria Sophia <mariasophia@comprehension.com> - 2026-09-02 22:26 +0200
Re: Signal "Carlos E.R." <robin_listas@es.invalid> - 2026-09-02 22:40 +0200
Re: Signal Maria Sophia <mariasophia@comprehension.com> - 2026-09-03 02:35 +0530
Re: Signal Nuno Silva <nunojsilva@invalid.invalid> - 2026-09-03 00:03 +0100
Re: Signal Nuno Silva <user17785@newsgrouper.org.invalid> - 2026-09-03 01:00 +0000
Re: Signal Maria Sophia <mariasophia@comprehension.com> - 2026-09-04 02:47 +0930
[OT] "trolling" (was: Re: Signal) Nuno Silva <nunojsilva@invalid.invalid> - 2026-09-03 11:49 +0100
Re: [OT] "trolling" Maria Sophia <mariasophia@comprehension.com> - 2026-09-04 03:38 +0930
Re: [OT] "trolling" "Carlos E.R." <robin_listas@es.invalid> - 2026-09-04 09:26 +0200
Re: Signal "Carlos E.R." <robin_listas@es.invalid> - 2026-09-02 20:29 +0200
Re: Signal Maria Sophia <mariasophia@comprehension.com> - 2026-09-02 21:33 +0200
Re: Signal "Carlos E.R." <robin_listas@es.invalid> - 2026-09-02 21:51 +0200
Re: Signal Maria Sophia <mariasophia@comprehension.com> - 2026-09-02 22:35 +0200
Re: Signal "Carlos E.R." <robin_listas@es.invalid> - 2026-09-02 23:00 +0200
Re: Signal Maria Sophia <mariasophia@comprehension.com> - 2026-09-03 02:36 +0530
Re: Signal Nuno Silva <nunojsilva@invalid.invalid> - 2026-09-02 11:24 +0100
Re: Signal Maria Sophia <mariasophia@comprehension.com> - 2026-09-02 17:30 +0200
Re: Signal Andy Burns <usenet@andyburns.uk> - 2026-09-03 09:29 +0100
Re: Signal Maria Sophia <mariasophia@comprehension.com> - 2026-09-04 03:04 +0930
Re: Signal Andy Burns <usenet@andyburns.uk> - 2026-09-03 18:46 +0100
Re: Signal Maria Sophia <mariasophia@comprehension.com> - 2026-09-04 04:22 +0930
Re: Signal Maria Sophia <mariasophia@comprehension.com> - 2026-09-01 19:20 +0200
Re: How does whatsapp work? "Carlos E.R." <robin_listas@es.invalid> - 2026-09-01 17:03 +0200
Re: How does whatsapp work? "s|b" <me@privacy.invalid> - 2026-09-02 20:56 +0200
Re: How does whatsapp work? "Carlos E.R." <robin_listas@es.invalid> - 2026-09-02 21:04 +0200
Re: How does whatsapp work? "s|b" <me@privacy.invalid> - 2026-09-04 21:15 +0200
Re: How does whatsapp work? "Carlos E.R." <robin_listas@es.invalid> - 2026-09-05 14:14 +0200
Re: How does whatsapp work? "s|b" <me@privacy.invalid> - 2026-09-05 18:03 +0200
Re: How does whatsapp work? Frank Slootweg <this@ddress.is.invalid> - 2026-09-01 14:37 +0000
Re: How does whatsapp work? micky <NONONOmisc07@fmguy.com> - 2026-09-09 09:07 +0300
Re: How does whatsapp work? "Carlos E.R." <robin_listas@es.invalid> - 2026-09-09 12:53 +0200
Page 9 of 9 — ← Prev page 1 2 3 4 5 6 7 8 [9]
| From | Maria Sophia <mariasophia@comprehension.com> |
|---|---|
| Date | 2026-09-04 03:04 +0930 |
| Subject | Re: Signal |
| Message-ID | <117cb2h$2o6p$1@nnrp.usenet.blueworldhosting.com> |
| In reply to | #155582 |
Andy Burns wrote: >>> <https://android-developers.googleblog.com/2026/03/contact-picker-privacy-first-contact.html> >>> >>> allows selective sharing of contacts, rather than all contacts, >>> allows time-limited access to contacts >> >> Now that looks awesome, and it really should have been around for years >> already. I don't want to have to choose between all or nothing. > > What google needs to do is set a sunset date for the old contacts > sharing permission, to force WhatsApp & co to move on ... Hi Andy, There is already, kind'a sort'a, something "like that" in Android 17... But not really... Apparently, you and I seem to be the only people who are posting to this thread who actually understand the technical details of contacts access here, where I hadn't thought of that idea, but it's logical. I like it. Since I strive to add value to the topic (even as this thread has been infested by the trolls), I looked it up for both iOS and for Android Unfortunately, for iOS, limited-contacts access does not have a default expiry. It persists until the user changes the permitted contacts/access. <https://developer.apple.com/documentation/contacts/cnauthorizationstatus> <https://developer.apple.com/documentation/contacts/accessing-the-contact-store> Same for Google, even with the Android 17 contact-picker improvements. <https://developer.android.com/about/versions/17/features/contact-picker> <https://developer.android.com/reference/android/provider/ContactsPickerSessionContract.Session> The closest we can get to your rather brilliant idea on Apple iOS18+ is limited contacts access where we can give an app access to only a selected subset of our contacts. <https://developer.apple.com/documentation/contacts/cnauthorizationstatus/limited> Android 17 goes in a somewhat different direction as its system Contact Picker lets an app ask you to select particular contacts to grant it temporary, session-based access to the requested fields. <https://developer.android.com/about/versions/17/features/contact-picker> <https://developer.android.com/blog/posts/the-second-beta-of-android-17> So Android's approach is kind'a sort'a getting closer to your expiry idea, but it doesn't give us a persistent, selectively scoped permission with a configurable/default lifetime. Interestingly, since I always try to keep both mobile platforms in mind, iOS has perhaps the better implementation of persistent access to only these people, while Android has perhaps the better implementation of give the app these people for this particular operation and then take the access away. -- Privacy is a million things, of which most people only know about three.
[toc] | [prev] | [next] | [standalone]
| From | Andy Burns <usenet@andyburns.uk> |
|---|---|
| Date | 2026-09-03 18:46 +0100 |
| Subject | Re: Signal |
| Message-ID | <nftq1vF790uU1@mid.individual.net> |
| In reply to | #155597 |
Maria Sophia wrote: > Unfortunately, for iOS, limited-contacts access does not have a default > expiry. It persists until the user changes the permitted contacts/access. > <https://developer.apple.com/documentation/contacts/cnauthorizationstatus> > <https://developer.apple.com/documentation/contacts/accessing-the- > contact-store> > > Same for Google, even with the Android 17 contact-picker improvements. > <https://developer.android.com/about/versions/17/features/contact-picker> > <https://developer.android.com/reference/android/provider/ > ContactsPickerSessionContract.Session> > > The closest we can get to your rather brilliant idea on Apple iOS18+ is > limited contacts access where we can give an app access to only a selected > subset of our contacts. I meant a different type of "sunset", something like, google have rolled-out the new contacts API in android 17, but by e.g. Android 19 they'll be removing the old API that lets apps scoff all your contacts. This gives the WhatsApps of this world a reason to switch to the new API if they want their app to keep working on the newest phone models.
[toc] | [prev] | [next] | [standalone]
| From | Maria Sophia <mariasophia@comprehension.com> |
|---|---|
| Date | 2026-09-04 04:22 +0930 |
| Subject | Re: Signal |
| Message-ID | <117cflg$8ki$1@nnrp.usenet.blueworldhosting.com> |
| In reply to | #155599 |
Andy Burns wrote: >> The closest we can get to your rather brilliant idea on Apple iOS18+ is >> limited contacts access where we can give an app access to only a selected >> subset of our contacts. > > I meant a different type of "sunset", something like, google have > rolled-out the new contacts API in android 17, but by e.g. Android 19 > they'll be removing the old API that lets apps scoff all your contacts. > > This gives the WhatsApps of this world a reason to switch to the new API > if they want their app to keep working on the newest phone models. Oh. I'm sorry for not understanding fully the issues you pointed out. I thought you wanted the access itself to expire over time (which, I think, is a good idea) but you're discussing that the API itself will expire. I agree. That's a good thing for contacts privacy. What amazes me about contacts is the same thing that amazes me about what people think, in general, which is they don't understand how contacts work, and yet, when I mention anything to do with contacts privacy, they go nuts. This thread is a very unpleasant example of that phenomenon. It's like telling someone next to you putting premium in their Honda Civic that they're wasting their money. They think I'm nuts since their whole lives, they believed that premium gives them more power. Why else would it be more expensive, they reason. It's the same here with contacts. a. They have no idea how it works b. And yet, they have very strong ideas that what I say, to them, is wrong Carlos did that in spades in this thread. Sigh. It makes helping people less than pleasant.
[toc] | [prev] | [next] | [standalone]
| From | Maria Sophia <mariasophia@comprehension.com> |
|---|---|
| Date | 2026-09-01 19:20 +0200 |
| Subject | Re: Signal |
| Message-ID | <11771gt$10iq$1@nnrp.usenet.blueworldhosting.com> |
| In reply to | #155471 |
Maria Sophia wrote: > Looking up Signal in particular, apparently it does not ask to be your > default contacts or default dialer/phone app but it "can" be your default > SMS app if you set it to be so. UPDATE Looking it up further, apparently that's changed. *Can I send SMS/MMS with Signal?* <https://support.signal.org/hc/en-us/articles/360007321171-Can-I-send-SMS-MMS-with-Signal> No. You can not send or receive insecure SMS/MMS with Signal. All communication through Signal is private. Both you and your contact need to use Signal if you want to communicate privately with messages and calls. This means only those numbers stored in our contacts belonging to registered Signal users will appear in your Signal contacts list. Signal used to support SMS in the Android app but this functionality was removed. Read more on the blog post here. *Removing SMS support from Signal Android (soon)* 12 Oct 2022 <https://signal.org/blog/sms-removal-android/> -- People are remarkably careless with contacts who are supposedly friends.
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2026-09-01 17:03 +0200 |
| Message-ID | <s36jmmx81g.ln2@Telcontar.valinor> |
| In reply to | #155454 |
On 2026-09-01 12:47, s|b wrote: > On Mon, 31 Aug 2026 20:37:46 +0200, Carlos E.R. wrote: > >> The WA number is always the real phone number. However, since recently >> you can define an alias and use that instead. > > Same with Signal. But you still need the phone number to set it up, > don't you? > I assume that with WhatsApp you need a phone number to set it up, then you define an Alias. But I do not know. This alias thing is new. -- Cheers, Carlos. ES🇪🇸, EU🇪🇺;
[toc] | [prev] | [next] | [standalone]
| From | "s|b" <me@privacy.invalid> |
|---|---|
| Date | 2026-09-02 20:56 +0200 |
| Message-ID | <nfr9qqFphcpU1@mid.individual.net> |
| In reply to | #155466 |
On Tue, 1 Sep 2026 17:03:56 +0200, Carlos E.R. wrote: > I assume that with WhatsApp you need a phone number to set it up, then > you define an Alias. But I do not know. This alias thing is new. Apparently it's not active in Belgium yet. People can register a username, but they can't use it yet. -- s|b
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2026-09-02 21:04 +0200 |
| Message-ID | <ci8mmmxmsa.ln2@Telcontar.valinor> |
| In reply to | #155522 |
On 2026-09-02 20:56, s|b wrote: > On Tue, 1 Sep 2026 17:03:56 +0200, Carlos E.R. wrote: > >> I assume that with WhatsApp you need a phone number to set it up, then >> you define an Alias. But I do not know. This alias thing is new. > > Apparently it's not active in Belgium yet. People can register a > username, but they can't use it yet. > Ah, yes, I think that happens in Spain too. I don't really know because using an alias instead of a phone number is not important to me, so I have not reserved one. -- Cheers, Carlos. ES🇪🇸, EU🇪🇺;
[toc] | [prev] | [next] | [standalone]
| From | "s|b" <me@privacy.invalid> |
|---|---|
| Date | 2026-09-04 21:15 +0200 |
| Message-ID | <ng0jloFkoikU1@mid.individual.net> |
| In reply to | #155523 |
On Wed, 2 Sep 2026 21:04:12 +0200, Carlos E.R. wrote: > On 2026-09-02 20:56, s|b wrote: > > > Apparently it's not active in Belgium yet. People can register a > > username, but they can't use it yet. > Ah, yes, I think that happens in Spain too. > > I don't really know because using an alias instead of a phone number is > not important to me, so I have not reserved one. I've got one in Signal, but so far I've added people who already got my phone number, so there was no use in hiding my phone number and using that username. But it's an option... -- s|b
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2026-09-05 14:14 +0200 |
| Message-ID | <rldtmmxscp.ln2@Telcontar.valinor> |
| In reply to | #155621 |
On 2026-09-04 21:15, s|b wrote: > On Wed, 2 Sep 2026 21:04:12 +0200, Carlos E.R. wrote: > >> On 2026-09-02 20:56, s|b wrote: >> >>> Apparently it's not active in Belgium yet. People can register a >>> username, but they can't use it yet. > >> Ah, yes, I think that happens in Spain too. >> >> I don't really know because using an alias instead of a phone number is >> not important to me, so I have not reserved one. > > I've got one in Signal, but so far I've added people who already got my > phone number, so there was no use in hiding my phone number and using > that username. But it's an option... > If I contact a plumber to do some work for me, send him photos on whatsapp, it is possible that I pay him using Bizum, which is a system in Spain for direct payment person to person identified by the phone number. Just an example :-) -- Cheers, Carlos. ES🇪🇸, EU🇪🇺;
[toc] | [prev] | [next] | [standalone]
| From | "s|b" <me@privacy.invalid> |
|---|---|
| Date | 2026-09-05 18:03 +0200 |
| Message-ID | <ng2sqhF1gg4U1@mid.individual.net> |
| In reply to | #155645 |
On Sat, 5 Sep 2026 14:14:19 +0200, Carlos E.R. wrote: > If I contact a plumber to do some work for me, send him photos on > whatsapp, it is possible that I pay him using Bizum, which is a system > in Spain for direct payment person to person identified by the phone number. > > Just an example :-) Bizum. I don't know it, but Wero works in the same way. In time, Wero will replace Bancontact in Belgium. Netherlands, Luxembourg, France, Germany will also start using Wero or are already (partially) using it. That way, everybody will be giving their phone number to everybody. I haven't activated it myself, but in the future I will have no choice. -- s|b
[toc] | [prev] | [next] | [standalone]
| From | Frank Slootweg <this@ddress.is.invalid> |
|---|---|
| Date | 2026-09-01 14:37 +0000 |
| Message-ID | <1176uvv.cic.1@ID-201911.user.individual.net> |
| In reply to | #155439 |
Carlos E.R. <robin_listas@es.invalid> wrote: [...] > The WA number is always the real phone number. However, since recently > you can define an alias and use that instead. I know what you mean, but as Micky also mentioned, the WhatsApp number is *a* real phone number. It doesn't have to be the phone number of the phone WhatsApp is running on. Your WhatsApp number is an *identification* number, which, in normally most cases, is *also* *a* telephone number. Micky already gave an example where the phone is in an other country and has (only) a foreign SIM with a different phone number. In that case, WhatsApp still uses your 'home' 'phone' number. Another example: WhatsApp works perfectly fine on a Wi-Fi-only SIM-less tablet (or phone), provided that during setup, you have given WhatsApp *a* phone number which belongs to you. In the old days, such a phone number could even be a landline (non-mobile) number (That was our very first setup.). These days, that's only available for business acounts. [...]
[toc] | [prev] | [next] | [standalone]
| From | micky <NONONOmisc07@fmguy.com> |
|---|---|
| Date | 2026-09-09 09:07 +0300 |
| Message-ID | <ejt1ald847q6tm3dek8i9qg4ug9aepsssq@4ax.com> |
| In reply to | #155465 |
In comp.mobile.android, on 1 Sep 2026 14:37:34 GMT, Frank Slootweg <this@ddress.is.invalid> wrote: >Carlos E.R. <robin_listas@es.invalid> wrote: >[...] > >> The WA number is always the real phone number. However, since recently >> you can define an alias and use that instead. > > I know what you mean, but as Micky also mentioned, the WhatsApp number >is *a* real phone number. It doesn't have to be the phone number of the >phone WhatsApp is running on. > > Your WhatsApp number is an *identification* number, which, in normally >most cases, is *also* *a* telephone number. > > Micky already gave an example where the phone is in an other country >and has (only) a foreign SIM with a different phone number. In that >case, WhatsApp still uses your 'home' 'phone' number. It's been several years but I think I can elaborate on what I said in the first place . I think when I got Whatsapp I was already using a foreign SIM , and when I got home and went back to my normal phone number the Whatsapp number and the Phone number didn't match . Eventually I thought this was too confusing for me , and I found that you can change your Whatsapp number by going into the Whatsapp settings and clicking on the place where it displays your number . I didn't realize that was a data entry field . I thought it was a heading . So I changed it to my home cell phone number, and of course it accepted that . I don't know if there's any validation involved and I could have just given it any old number , maybe not but why would I want to do that ? So this left me still confused because I can't remember what my Whatsapp number is some of the time even though it's my USA cell phone number and I live in the USA.That is, I can't remember that it's my USA cell phone number . LOL > > Another example: WhatsApp works perfectly fine on a Wi-Fi-only >SIM-less tablet (or phone), provided that during setup, you have given >WhatsApp *a* phone number which belongs to you. In the old days, such a >phone number could even be a landline (non-mobile) number (That was our >very first setup.). These days, that's only available for business >acounts. > >[...]
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2026-09-09 12:53 +0200 |
| Message-ID | <sdq7nmxdmp.ln2@Telcontar.valinor> |
| In reply to | #155810 |
On 2026-09-09 08:07, micky wrote: > In comp.mobile.android, on 1 Sep 2026 14:37:34 GMT, Frank Slootweg > <this@ddress.is.invalid> wrote: > >> Carlos E.R. <robin_listas@es.invalid> wrote: >> [...] >> >>> The WA number is always the real phone number. However, since recently >>> you can define an alias and use that instead. >> >> I know what you mean, but as Micky also mentioned, the WhatsApp number >> is *a* real phone number. It doesn't have to be the phone number of the >> phone WhatsApp is running on. >> >> Your WhatsApp number is an *identification* number, which, in normally >> most cases, is *also* *a* telephone number. >> >> Micky already gave an example where the phone is in an other country >> and has (only) a foreign SIM with a different phone number. In that >> case, WhatsApp still uses your 'home' 'phone' number. > > It's been several years but I think I can elaborate on what I said in > the first place . I think when I got Whatsapp I was already using a > foreign SIM , and when I got home and went back to my normal phone > number the Whatsapp number and the Phone number didn't match . > Eventually I thought this was too confusing for me , and I found that > you can change your Whatsapp number by going into the Whatsapp settings > and clicking on the place where it displays your number . I didn't > realize that was a data entry field . I thought it was a heading . So I > changed it to my home cell phone number, and of course it accepted that > . I don't know if there's any validation involved and I could have just > given it any old number , maybe not but why would I want to do that ? I believe an application has access to the current phone number of the device. Maybe a permission is involved. Sending and receiving and SMS confirms that it works, if needed. Which is confusing because these apps ask for the number. > > So this left me still confused because I can't remember what my > Whatsapp number is some of the time even though it's my USA cell phone > number and I live in the USA.That is, I can't remember that it's my USA > cell phone number . LOL >> >> Another example: WhatsApp works perfectly fine on a Wi-Fi-only >> SIM-less tablet (or phone), provided that during setup, you have given >> WhatsApp *a* phone number which belongs to you. In the old days, such a >> phone number could even be a landline (non-mobile) number (That was our >> very first setup.). These days, that's only available for business >> acounts. >> >> [...] -- Cheers, Carlos. ES🇪🇸, EU🇪🇺;
[toc] | [prev] | [standalone]
Page 9 of 9 — ← Prev page 1 2 3 4 5 6 7 8 [9]
Back to top | Article view | comp.mobile.android
csiph-web