Re: How does incoming caller ID work - and more specifically - can caller ID source data be controlled?

On 09/06/2020 01:04, Arlen Holder wrote:
> On Sat, 6 Jun 2020 22:30:21 +1000, Gary R. Schmidt wrote:
> 
>>> But if you have a _better_ working solution to the problem, I'm all ears.
>>>
>> Sure, you have to write a "call application" that does all that you want
>> securely, it cannot be done using the existing components of an Android
>> handset.
> 
> Hi Gary,
> 
> Thank you for clarifying the situation, where I don't disagree with you.
> o Both you & I are well meaning, intelligent, purposefully helpful adults.
> 
> As such, you hit the nail on the head.
> o If you're an expert, you can write your own apps that do have privacy;
> o But if you're a general user, you need to rely on privacy-based apps.
> 
> The only workable solution is to either write your own app, or simply use
> apps that don't rely on the inherently poorly designed default sqlite
> contacts database use model (designed, of course, by Google).
> 
> To have _anything_ in the default contacts sqlite db, is to NOT be private!
> o I didn't design it that way... Google did.
> 
> To my knowledge, nobody has suggested a better solution (e.g., your
> solution is fine to write your own app, but it's not workable for the
> general user).
> 
Ah, I didn't mean that 'you' qua 'you' would have to write the 
application, but that a secure application would have to be written.

Possibly one or more already exists, if I wanted secure[1] 
communications I would be looking for such a replacement application, as 
  I said, it cannot be bolted-on to the existing one.

	Cheers,
		Gary	B-)

1 - Of course, secure in this, or any,  context is a wibbly-wobbly concept.

-- 
Waiting for a new signature to suggest itself...