Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Determine which apps are broken by which rules #16

Open
ThatIsAPseudo opened this issue Aug 29, 2020 · 1 comment
Open

Determine which apps are broken by which rules #16

ThatIsAPseudo opened this issue Aug 29, 2020 · 1 comment
Labels
enhancement New feature or request

Comments

@ThatIsAPseudo
Copy link

It would be very useful to have a table in a md file listing what each rule / group of rules will break in iOS / maxOS, with details of what is not working so that each user can choose between privacy and usability.
There could also be various information on the role of each connexion.

Anyone can test the rules, so there would just need PR to update the rows.

For instance (not for real, that's an example) :

Domain Role Concerned applications Broken
*.itunes-apple.com.example.net  Retrieves albums' cover iTunes Albums' covers won't show
*.randomstuff.net Untested Untested Untested
*.app-store.something.com ? App Store, iTunes, Podcast Display a blank screen, installed apps won't update
iTunes Display a blank screen, play random music will play at 2:00 AM
Podcast Display a blank screen

Otherwise we could also just have 3 levels of inconvenience (2 = app does not work, 1 = some features are broken, 0 = everything works but privacy-killing connexions are blocked) which could be easier to read :

Domain Application Level
*.itunes-apple.com.example.net iTunes 1
App Store 0
*.randomstuff.net ? ?
*.app-store.something-1.com App Store 1
*.app-store.something-2.com App Store 2

I guess this file could be updated everytime a new line is added to the domains list.

@cedws cedws added the enhancement New feature or request label Aug 30, 2020
@cedws
Copy link
Owner

cedws commented Aug 30, 2020

The main reason I haven't done this is that determining which features are broken by blocking certain domains is very tedious. It's also subject to software updates to Apple of course, so it requires constant maintenance.

I think I said somewhere in the README that the path of least resistance is just disabling the blacklist when you need to do something that requires Apple servers. Not ideal, but that's privacy in the 21st century 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants