All adblockers can see your data, but by you saying "they" you are implying somehow the Adguard company is seeing your data, and have not seen any evidence of that.Adguard extension can Reed,modify...your data
All adblockers can see your data, but by you saying "they" you are implying somehow the Adguard company is seeing your data, and have not seen any evidence of that.Adguard extension can Reed,modify...your data
Other Adblockers like Wipr,Better,...can´t reed, modify...your dataAll adblockers can see your data, but by you saying "they" you are implying somehow the Adguard company is seeing your data, and have not seen any evidence of that.
Yes they can.... that is exactly how all these extensions work.Other Adblockers like Wipr,Better,...can´t reed, modify...your data
Yes they can.... that is exactly how all these extensions work.
These content blockers have to be able to read (see) the data to be able to tell what to block. How would it work otherwise. I think what they are saying there is nothing is saved or transmitted, but the extension has to see the data.I just installed Ka-Block to see what Safari Preferences display about the data security.
You have a point as usual.These content blockers have to be able to read (see) the data to be able to tell what to block. How would it work otherwise. I think what they are saying there is nothing is saved or transmitted, but the extension has to see the data.
This is not accurate. Ad-blockers that use (only) the official content-blocker API install a set of rules that tell Safari which objects should be blocked. Such blockers never see your actual traffic.These content blockers have to be able to read (see) the data to be able to tell what to block. How would it work otherwise. I think what they are saying there is nothing is saved or transmitted, but the extension has to see the data.
To block an object (in some cases including whole webpages and not only parts of the content) you have to identify it as per set of rules installed, i.e. read data. And that is what Weasel was talking about.This is not accurate. Ad-blockers that use (only) the official content-blocker API install a set of rules that tell Safari which objects should be blocked. Such blockers never see your actual traffic.
I don't think there is a huge difference among them. I have liked the Adguard extension because it allows whitelisting of sites and custom blocking rules. Also they have a staff member who has been fairly active here on the forum answering questions, and I have not seen anybody else do that.Then,...which is the best content blocker? In my opinion is Adguard
That's not what was said. When using an ad blocker that only uses Apple's content blocker API (such as e.g. Wipr), only Safari sees the actual browsing data and does the blocking. The blocker only installs the rules, but does not see the data.To block an object (in some cases including whole webpages and not only parts of the content) you have to identify it as per set of rules installed, i.e. read data. And that is what Weasel was talking about.
Apple's phrasing sounds "scary" for a reason."Your browser may require AdBlock to ask for permission to "read and change all your data on the websites you visit." This sounds scarier than it is. All it means is that AdBlock needs to be able to:
- See every page you open so that it can work on any website you visit.
- Read the data on the web page to find the ads.
- Change the data on the page to block or hide the ads."
Can you point to some documentation on this? I read Apple's dev info on content blockers and it hints at nothing like what you are saying.That's not what was said. When using an ad blocker that only uses Apple's content blocker API (such as e.g. Wipr), only Safari sees the actual browsing data. The blocker only installs the rules, but does not see the data.
https://developer.apple.com/library...onceptual/ExtensibilityPG/ContentBlocker.htmlCan you point to some documentation on this? I read Apple's dev info on content blockers and it hints at nothing like what you are saying.
It's not that difficult to understand. The ad blocker describes what objects to block in a rule language specified by Apple (for example, a rule could state that all URLs that contain the string "tracker" should be blocked). Safari interprets the rules and does the actual filtering.If you think about it, how would an adblocker or content blocker know what to filter unless it looks over all the urls that makeup the display of a web page.
If you see something like "Wipr does not have permission to read or transmit content from any web pages" in Safari, you know that the ad blocker is not getting access to your data (this message is generated by Safari based on the permissions granted to the extension).Without seeing source code on any of these blockers, we don't really know what they are doing, so there is a certain amount of trust involved.
I think we might be arguing over semantics. I agree the content blocker can't do anything with your data, but what you are posting does not negate my earlier point. For the content blocker to work it has to parse the site urls, so in that way it can see your data.It's not that difficult to understand. The ad blocker describes what objects to block in a rule language specified by Apple (for example, a rule could specifiy that all URLs that contain the string "tracker" should be blocked). Safari interprets the rules and does the filtering.
I really don't know how else describe it. When using the content blocker API, *Safari* applies the rules and filters objects as it loads the web page. The extension never sees any of your data or where you are browsing. It only provides the filtering rules, but is not involved in the actual web browsing in any way. There is a significant difference compared to traditional ad blockers which insert themselves into the interpretation of the web page.I think we might be arguing over semantics. I agree the content blocker can't do anything with your data, but what you are posting does not negate my earlier point. For the content blocker to work it has to parse the site urls, so in that way it can see your data.
From the site you have linked, Apple's dev info:https://developer.apple.com/library...onceptual/ExtensibilityPG/ContentBlocker.html
"In addition to blocking unwanted content, a Content Blocker extension protects privacy. For example, the extension doesn’t have access to users’ browsing activity and it can’t report activity to your app"
It's not that difficult to understand. The ad blocker describes what objects to block in a rule language specified by Apple (for example, a rule could state that all URLs that contain the string "tracker" should be blocked). Safari interprets the rules and does the actual filtering.
If you see something like "Wipr does not have permission to read or transmit content from any web pages" in Safari, you know that the ad blocker is not getting access to your data (this message is generated by Safari based on the permissions granted to the extension).
And how does that contradict anything said above?From the site you have linked, Apple's dev info:
"... The extension tailors your content by hiding elements, blocking loads, and stripping cookies from Safari requests..."
From Wipr's website you have mentioned as an example:
"...Wipr blocks all ads, trackers, EU cookie notices, and other annoyances, so you can focus on the content that matters to you. It works in Safari and all apps that use Safari to display web pages.
Can you explain more please? (I'm having trouble wrapping my head around this)I really don't know how else describe it. When using the content blocker API, *Safari* applies the rules and filters objects as it loads the web page. The extension never sees any of your data or where you are browsing. It only provides the filtering rules, but is not involved in the actual web browsing in any way. There is a significant difference compared to traditional ad blockers which insert themselves into the interpretation of the web page.
Exactly.Can you explain more please? (I'm having trouble wrapping my head around this)
So the blocker is telling Safari to block the URL and does not parse any data at all
Not sure what you mean by "listed URLs".even the listed URLs?
Well, of course the blocker knows blacklisted URLs since that's part of the rules it provides to Safari. But again, when using only Apple's API it does not see if the user actually visits the blacklisted or any other URL, since it is not involved in the page loading process.The blacklisted URLs.
Thanks for the link. I'll check out the video.If you want to know more technical details, here's a video from the 2015 WWDC. The first 20 minutes or so are about content blockers:
To answer your question, uBlock Origin is hands down better than any other blocker. It's lighter, faster, uses less memory/CPU, blocks tracking and many other content types. It also has anti-blocking functionality. It's a HUGE deal that the creators are independently run and passionate about their product and won't be bought out or try and make money off your browsing. Every day another adblocker gets bought out by a marketing company.