News for hackers. Stuff that matters.

A comment on Explanation of the state of uBlock Origin and other blockers for Safari. Parent comment

Re:Explanation of the state of uBlock Origin and other block... by tyingq on Friday September 20, 2019 @09:37AM (#21026506)
They are already familiar with how to run a comprehensive review of apps. They could just replicate that for extensions.
[ Parent | on HN ]
Re:Explanation of the state of uBlock Origin and other block... by pwinnski on Friday September 20, 2019 @11:47AM (#21027999)
They can do that for apps because apps are compiled and submitted. The expressly do not allow for dynamic code execution within apps to keep functionality from changing after their review.

That cannot be "just replicate"d for javascript extensions.

[ Parent | on HN ]
Re:Explanation of the state of uBlock Origin and other block... by wmp56 on Friday September 20, 2019 @11:33PM (#21033329)
> That cannot be "just replicate"d for javascript extensions.

This is false too. If extensions aren't allowed to communicate with the internet and can't auto-update themselves, then they also can't run arbitrary code without the user's consent.

[ Parent | on HN ]
Re:Explanation of the state of uBlock Origin and other block... by rwiggum on Friday September 20, 2019 @02:30PM (#21029815)
> The expressly do not allow for dynamic code execution within apps to keep functionality from changing after their review.

This is false. You can deploy a react native app with dynamic code downloading and execution to the apple app store.

[ Parent | on HN ]
Re:Explanation of the state of uBlock Origin and other block... by ChrisLTD on Friday September 20, 2019 @04:41PM (#21031069)
Apple is doing reviews for extensions, and also tightening up the APIs at the same time. At least on the Mac you've got alternatives if you're willing to make a different trade off. iPhone users and ChromeOS users are stuck.
[ Parent | on HN ]