The operator decides which apps can interact with a given esim.
Wasn't this supposed to be a general purpose computer? Why can a service decide which apps I can use to access which features of my own device?
nesterenkopavel [3 hidden]5 mins ago
I guess Google introduced it for security reasons. You still can install eSIM within your own android or in operator’s app by just giving permissions. Unfortunately service cannot decided by its own so you are as a user staying in safety while using random app.
wolvoleo [3 hidden]5 mins ago
Hmm I don't really want apps to be able to be messing around with my esims. Just give me a QR to scan. Simple enough.
nesterenkopavel [3 hidden]5 mins ago
System uses the same mechanism under the hood. If the app has their own Mobile Operator, it can be more smooth to work with eSIM - without QR scanning at all
metalman [3 hidden]5 mins ago
fuck esims, and ALL the survielance tech
personaly I have decided to match(best I can), asymetry with asymetry, and reduce my dependencys to a minimum.
but who the fuck is kidding who? it's not the back doors, or adversurvielence, it's the fucking FRONT door now!
zero control or agency is the plan
fuck off
Wasn't this supposed to be a general purpose computer? Why can a service decide which apps I can use to access which features of my own device?