▲ | kccqzy 8 days ago | ||||||||||||||||||||||||||||
I agree with you regarding how Apple can do the bare minimum and barely get called out. But the fact is, I don't know of anything who's using declarativeNetRequest on Safari. The ecosystem of Safari blocking is centered around the legacy technology of content blockers from 2015. And the legacy technology works well enough that there's no pressure for either Apple or adblocker developers to adopt the new thing. | |||||||||||||||||||||||||||||
▲ | radicaldreamer 8 days ago | parent | next [-] | ||||||||||||||||||||||||||||
The legacy technology is also privacy-protecting in the sense that normal ad-blocking on iOS doesn’t use any third party JS filtering or reading of data on the page. It breaks down because there are a ton of workarounds sites and ad-networks implement so it’s not super effective compared to MV2 ublock-origin | |||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||
▲ | xattt 7 days ago | parent | prev [-] | ||||||||||||||||||||||||||||
> legacy technology … 2015 If there’s anything that makes you feel old, it’s this. |