3 ms·

You have a point but are also mistaken. XPrivacy does way more granular access checks than Android or iOS provide. The downside is, it's not casual user-friendl

You have a point but are also mistaken. XPrivacy does way more granular access checks than Android or iOS provide. The downside is, it's not casual user-friendly. With XPrivacy you're able (or used to be able - I'm not sure if it works on recent Android versions) control things like how apps can use WebViews (e.g. what URLs they are allowed to open there), or whenever app is allowed to read or write (all separately) clipboard data. Etc etc.

scarface74 8y ago
I’m looking at a list of permissions here: https://github.com/M66B/XPrivacy/blob/master/README.md https://github.com/M66B/XPrivacy/blob/master/README.md Most of these permissions either require individual consent after you run the app (and can be revoked in settings) or aren’t allowed under any circumstances. The exceptions I see are: Clipboard Internet access (you can block cellular internet access on iOS and 3rd party keyboards can be blocked from allowing any network access) Prevent links from opening in a view - depending on which type of web view that an app uses, the native content blocking framework that third party ad blockers use for Safari also work in the WebView. For instance, the ad blocker I have installed works with Feedly - my RSS reader. The only sensor I think that can be blocked is the GPS.
- snaky 8y ago
  XPrivacy is not about blocking, it's about faking. PrivacyGuard in LineageOS is about blocking.
  - scarface74 8y ago
    How is “faking” it better than just not allowing it all? iOS Developers have had to handle being denied permissions gracefully since 2008.
    - DrJaws 8y ago
      some apps don't work if the permissions are blocked. With xprivacy you can tell them My phone number is 000 000 000 and my email is fuck@you.com and they work fine then
      - scarface74 8y ago
        And iOS doesn’t need that bandaid. App developers have been developing with the expectation that their apps could be denied permissions they request since day one.
        drdaeman 8y ago
        Except for stuff that iOS doesn't ask and even implement a permission for. Like UIDevice.identifierForVendor.

scarface74 8y ago

I’m looking at a list of permissions here: https://github.com/M66B/XPrivacy/blob/master/README.md https://github.com/M66B/XPrivacy/blob/master/README.md Most of these permissions either require individual consent after you run the app (and can be revoked in settings) or aren’t allowed under any circumstances. The exceptions I see are: Clipboard Internet access (you can block cellular internet access on iOS and 3rd party keyboards can be blocked from allowing any network access) Prevent links from opening in a view - depending on which type of web view that an app uses, the native content blocking framework that third party ad blockers use for Safari also work in the WebView. For instance, the ad blocker I have installed works with Feedly - my RSS reader. The only sensor I think that can be blocked is the GPS.

snaky 8y ago
XPrivacy is not about blocking, it's about faking. PrivacyGuard in LineageOS is about blocking.
- scarface74 8y ago
  How is “faking” it better than just not allowing it all? iOS Developers have had to handle being denied permissions gracefully since 2008.
  - DrJaws 8y ago
    some apps don't work if the permissions are blocked. With xprivacy you can tell them My phone number is 000 000 000 and my email is fuck@you.com and they work fine then
    - scarface74 8y ago
      And iOS doesn’t need that bandaid. App developers have been developing with the expectation that their apps could be denied permissions they request since day one.
      - drdaeman 8y ago
        Except for stuff that iOS doesn't ask and even implement a permission for. Like UIDevice.identifierForVendor.