[continued from previous message]   
      
   > Subscriptions   
      
   Which you can decline to use.   
      
   > Apple Pay   
      
   Which you can decline to use.   
      
   > Screen Time   
      
   Which you can decline to use.   
      
   > Family Sharing   
      
   Which you can decline to use.   
      
   > Photos sync   
      
   Which you can decline to use.   
      
   > Notes sync   
      
   Which you can decline to use.   
      
   > Safari sync   
      
   Which you can decline to use.   
      
   > Password autofill   
      
   Which you can decline to use.   
      
   > Two-factor prompts   
      
   Which you can decline to use.   
      
   > System services that check entitlement status   
      
   Such as?   
      
   > etc.   
   >   
   > When you're signed out, each of these tries to initialize, fails, and   
   > triggers a prompt. So the frequency I am describing is rational and   
   > predictable given the architecture.   
      
   Wrong.   
      
   >   
   >>> [1] This is possible on an Android phone - via "Google Password Manager"   
   >>> in Chrome. Eeeeeiiii ! What a stinkin' plop of proposition that is!   
   >   
   > The fact is that iOS devices are designed around the assumption that the   
   > cloud account is always present. That is why the experience feels like a   
   > dumb terminal when you decline to participate in that model.   
   >   
   > Any OS can behave like iOS if you are willing to log into the mothership   
   > servers constantly. The difference is that on iOS, the design makes that   
   > model unavoidable, and if you refuse to sign in, you see the underlying   
   > mechanics exposed all day, every day, forever.   
      
   You can log in only when you want to install or update apps.   
      
   Period.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)