XPost: comp.mobile.android, alt.comp.freeware   
   From: arlenholder@newmachine.com   
      
   On Thu, 4 Jun 2020 00:00:12 +0700, JJ wrote:   
      
   >> As for "something to hide", what on earth are you intimating?   
   >   
   > Basic concept of privacy. What were you thinking, anyway?   
      
   Hi JJ,   
      
   You don't seem to be a troll so I will spend energy answering you.   
      
   I'm trying to accomplish something _difficult_ here, which is to design a   
   system _outside_ of google, that does two very important things:   
   1. It keeps the sqlite file empty (because of known privacy flaws), and,   
   2. Yet, it allows for caller ID to work for the users' known contacts.   
      
   You are either aware of the known sqlite privacy flaws, or you're not.   
   o I was trying to ascertain, from you, whether you are aware of them.   
      
   I _still_ can't tell from your answer whether you're aware of them.   
   o Are you?   
      
   Note: It doesn't matter to the question whether you're aware of them; but   
   you were responding to a known ignorant troll with the line:   
    "> Because sqlite databases on your phone aren't private, Arlen?   
    "It's not, if one has something to hide."   
      
   Usenet is useful for purposefully helpful adults...   
   o That's two things: (a) purposefully helpful, and (b) adults.   
      
   You were responding to a troll who is not an adult, which isn't important   
   because that troll is clearly ignorant of the sqlite privacy holes.   
      
   I don't care about that ignorant troll... but I do care about you.   
      
   Assuming you're (a) purposefully helpful, and (b) an adult...   
   o I simply ask you a single question which is relevant to your post:   
      
   Q: Are you aware of the known sqlite privacy holes, JJ?   
      
   NOTE: If you are, then why did you respond the way you did to the troll?   
   If not, then all I ask is you try to _understand_ them; that's all.   
      
   And _then_, we can get back to the TOPIC of this thread, which is:   
   Q: How does incoming caller ID work - and more specifically - can caller ID   
   source data be controlled?   
      
   Note this is a TECHNICAL question which affects multiple cascaded levels:   
   1. carrier CNI information   
   2. sqlite db contacts lookup   
   3. caller id app interception   
   4. personal privacy database lookup   
      
   The goal is to freely attain caller ID display _without_ #2 above.   
   o That's a technical question which the trolls can't possibly help with.   
   --   
   Usenet is a medium which requires a bit of clarification in each post.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)