home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   alt.privacy      Discussing privacy, laws, tinfoil hats      112,125 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 110,849 of 112,125   
   Carlos E.R. to Andrew   
   Re: RCS is not more private and secure t   
   18 Dec 24 21:18:26   
   
   XPost: comp.mobile.android, misc.phone.mobile.iphone   
   From: robin_listas@es.invalid   
      
   On 2024-12-18 18:47, Andrew wrote:   
   > Carlos E.R. wrote on Wed, 18 Dec 2024 08:37:04 +0100 :   
   >   
   >>> The only reason RCS is in iPhones is the EU demanded Apple add it.   
   >>> RCS encryption isn't there only because the EU didn't demand that too.   
   >>   
   >> The EU did not think Apple would be that stupid as to not implement it.   
   >   
   > I agree with you and I disagree with Frank who had chastised you.   
   >   
   > What appears to be transpiring are the following events:   
   >   
   > 1. Apple said in court the last thing they'll ever want to do   
   >    is to interoperate with Android. That's a fact, paraphrased.   
   >   
   > 2. The EU forced Apple to interoperate (a little bit) with Android.   
   >   
   > 3. Unfortunately, the EU didn't force Apple to handle encryption.   
   >   
   > 4. So nobody gets interoperability (with encryption) because   Apple   
   > execs decided interoperability is a threat to their profits.   
   >   
   > 5. And it is.   
   >   
   > 6. Meanwhile, most people are completely clueless that the problem is   
   >    that Apple has no intention of ever interoperating with Android.   
   >   
   > 7. Hence, the FBI warned people that, essentially, there is no   
   > encryption when Apple messages are involved with Android devices.   
   >   
   > The FBI doesn't take sides so they don't mention Apple is the problem.   
   > But anyone with half a brain is well aware that Apple is the problem.   
      
   It is, however, reasonable for a company to say that they will only   
   implement the approved standard. However, I don't know for what reasons,   
   the standard will not be expanded for some reason I don't know, either   
   temporarily or permanently. That company should push hard for the   
   standard to expand. Maybe this can not be. And say clearly when the   
   standard is expected to be ready. IF.   
      
   In that case, said company should implement instead the existing   
   proprietary method, which perhaps, I do not know, has been offered free   
   of charge. Even as a temporary measure while the standard is developed,   
   for the benefit of all users.   
      
   --   
   Cheers, Carlos.   
      
   --- SoupGate-DOS v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca