Conversation

✨saleem✨ ⍼
@saleemrash1d
wait WHAT, this is the "issue" people are talking about? that's ridiculous, you literally cannot defend an Android device against apps which can use system permissions
Quote Tweet
henry 🌘
@hdevalence
this isn’t a contact tracing problem, and painting it as one does a huge disservice to the privacy engineering that went into getting that protocol built and deployed
Show this thread
Image
Image
2
8
✨saleem✨ ⍼
@saleemrash1d
fwiw, "apps which can use system permissions" are not the same as "preinstalled apps" — there are plenty of preinstalled apps that aren't privileged in any way
2
5
Daniel Micay
@DanielMicay
Replying to
@_QuickNET_
and
@saleemrash1d
As long as it's disabled, it's essentially uninstalled with the apk still present in the OS images. They could auto-install apps for their partnerships as part the initial setup wizard and then users would be able to opt-out, and it wouldn't waste space in the OS images.
1
QuickNET
@_QuickNET_
Replying to
@DanielMicay
and
@saleemrash1d
My issue is I don't want it "essentially" uninstalled, I want it gone, it should've never been pre-installed and it should've never been made such that it can't be uninstalled. Basically it's the principle.
1
Daniel Micay
@DanielMicay
Replying to
@_QuickNET_
and
@saleemrash1d
What I mean is that the OS has a package manager and it's possible for the app to be uninstalled. The apk is still present in the OS images though, and the package manager will still be aware of that and able to install it from there again.
1
Daniel Micay
@DanielMicay
Replying to
@DanielMicay
@_QuickNET_
and
@saleemrash1d
The better approach is what I said: offering a list of recommended apps in the initial setup. They don't have to download them for the initial setup after boot since they can use the standard system_other approach to have them cached there before an update has been installed.
2