News for hackers. Stuff that matters.
Re:Firefox 68.0 by wtallis on Tuesday July 09, 2019 @01:58PM (#20394731)
He's not claiming that they removed it. He's referring to the fact that Google announced their intention to remove the APIs that uBlock relies on. They haven't followed through with the plan yet, but neither have they completely backtracked. See eg. https://www.androidpolice.com/2019/05/29/google-still-plans-... and reports that they'll continue to provide that functionality only to enterprise users: https://9to5google.com/2019/05/29/chrome-ad-blocking-enterpr...
Re:Firefox 68.0 by techntoke on Wednesday July 10, 2019 @12:33AM (#20399166)
Chrome devs made it clear that just because the API is changing that adblocking will still be supported and it will be faster. Sometimes APIs change.
Re:Firefox 68.0 by krageon on Wednesday July 10, 2019 @04:57AM (#20400299)
The API was crippled, not changed. There is a fairly lengthy explanation of how it is bad and why by the author of uBlock Origin: https://github.com/uBlockOrigin/uBlock-issues/issues/338#iss...
Re:Firefox 68.0 by sascha_sl on Wednesday July 10, 2019 @02:16AM (#20399541)
being able to decide for every request with code vs a limited number of patterns you can pre-populate is not an equally useful API replacement