Re:Chrome extension manifest v3 proposal: comment from uBloc...
by dr0verride on Thursday May 30, 2019 @08:49AM
(#20050589)
Thanks for mentioning this. I had no idea Firefox Mobile supported add-ons even though I've been using it for a year.
[ Parent
| on HN ]
Re:Chrome extension manifest v3 proposal: comment from uBloc...
by StavrosK on Thursday May 30, 2019 @08:57AM
(#20050649)
Yeah, just browse to the addon page (e.g. https://addons.mozilla.org/en-US/firefox/addon/ublock-origin...) and click "add to Firefox", it works as usual. Not on iOS, though, since Apple doesn't allow real third-party browsers.
Re:Chrome extension manifest v3 proposal: comment from uBloc...
by ronjouch on Thursday May 30, 2019 @09:35AM
(#20050942)
iOS / Safari / Content Blockers are not as full-featured as Android / Mobile Firefox / uBlock Origin, but I'm quite content with https://1blocker.com/ , it provides several lists (with a less stringent limit than the crippled webRequest API discussed here) of rules to pick from, and the possibility to create your own rules through a Safari extension.
Re:Chrome extension manifest v3 proposal: comment from uBloc...
by warp on Thursday May 30, 2019 @09:34AM
(#20050940)
Apple does allow real third-party ad blockers though.
Re:Chrome extension manifest v3 proposal: comment from uBloc...
by saagarjha on Thursday May 30, 2019 @10:47AM
(#20051712)
Depending on your opinion of content blockers, not on iOS.
Re:Chrome extension manifest v3 proposal: comment from uBloc...
by msbarnett on Thursday May 30, 2019 @02:15PM
(#20054265)
The content blocking API it allows on iOS is significantly less restrictive than Chrome’s proposal
Re:Chrome extension manifest v3 proposal: comment from uBloc...
by sudo_rm on Thursday May 30, 2019 @08:52AM
(#20050604)
I think add-ons only work on Android though, not iOS.