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

Filter all UWP apps by default #1647

Closed
ameshkov opened this issue Mar 31, 2017 · 7 comments
Closed

Filter all UWP apps by default #1647

ameshkov opened this issue Mar 31, 2017 · 7 comments

Comments

@ameshkov
Copy link
Member

Why don't we do it?

@ameshkov ameshkov added this to the 6.2 milestone Mar 31, 2017
@BooBerry
Copy link

BooBerry commented Apr 7, 2017

Because it might break some apps? I thought it broke connectivity with the Facebook/Messenger apps or something like that, if I recall correctly? Assuming, of course, the Facebook/Messenger apps are UMP in the first place (I mean they've got to be, right?).

@ameshkov
Copy link
Member Author

ameshkov commented Apr 7, 2017

Yeah, you're right:)

@ameshkov
Copy link
Member Author

ameshkov commented Apr 7, 2017

Delayed for v6.3 then

@Bluscream
Copy link

Can we have this optional please? It's really annyoing to search UWP binaries after updates

@stale
Copy link

stale bot commented Aug 1, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Aug 1, 2019
@mbc07
Copy link

mbc07 commented Aug 1, 2019

What about a whitelist method? E.g. filter all UWP apps except those specified on the list. AdGuard could come with a pre-populated list of apps that are known to break, similar to what it already does for HTTPS filtering...

@stale stale bot removed the wontfix label Aug 1, 2019
@ameshkov
Copy link
Member Author

ameshkov commented Aug 1, 2019

Actually, this is a duplicate of #1286

AdGuard could come with a pre-populated list of apps that are known to break, similar to what it already does for HTTPS filtering...

Yeah, either this or we could have HTTPS filtering disabled for non-browsers by default (unless we're 100% sure that it does not break things).

@ameshkov ameshkov closed this as completed Aug 1, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants