4 ms·

This past weekend I tried Safari again when I saw it updated to version 12. I was surprised to see that Apple deactivated my uBlock Origin plugin, saying it wou

by wyclif 8y ago

This past weekend I tried Safari again when I saw it updated to version 12. I was surprised to see that Apple deactivated my uBlock Origin plugin, saying it would slow the browser down. So now Safari is unusable and filled with ads, and there's nothing Apple provides to replace uBlock Origin. This is a total show-stopper for me.

metafunctor 8y ago
It’s really just a suggestion to turn off some extensions. Haven’t bothered to figure out what triggers Safari to do that, but you can still run uBlock Origin on Safari 12 and it seems to work fine.
- saagarjha 8y ago
  > Haven’t bothered to figure out what triggers Safari to do that Safari has a new extensions model and will be deprecating the legacy one in a year. Hence the push to migrate to newer extensions.
  - sweetp 8y ago
    the new extensions model is ridiculously useless... You need to build your extension in Xcode now, and for anything other than content blocking, the APIs are non existent... for instance, you can't even close tabs! I made an extremely simple extension using the new model around 2months - before I try migrating an older "actually useful" extension. But theres just no way its possible to migrate. Apple doesn't care about browser extensions now, it seems they want everyone to move to the new model, so they can collect revenue on sales on ad blockers. :(
    - tgragnato 8y ago
      > Apple doesn't care about browser extensions now, it seems they want everyone to move to the new model, so they can collect revenue on sales on ad blockers. The web is terrible without a serious adblocker and the available alternatives (paid or not) are unable to take away the same amount of junk. People will simply start using another browser.
    - akvadrako 8y ago
      This is wrong - you can inject arbitrary scripts and styles: https://developer.apple.com/documentation/safariservices/safari_app_extensions https://developer.apple.com/documentation/safariservices/saf...
      - wild_preference 8y ago
        You didn’t reply to or contradict anything they said. You need Xcode to build extensions and Safari has a super limited API. Executing JS and CSS don’t address either.
        akvadrako 8y ago
        He didn’t say limited, he said nonexistent. More specifically, if you can inject scripts I don’t see why you couldn’t call window.close()
jurip 8y ago
I haven't tried uBlock Origin, but I'm running 1Blocker and Ka-Block! and they filter out most of the worst offenders.
euvitudo 8y ago
I just use uBlock Origin anyway (basically ignore the message). I don't see a difference in performance with the plugin when I updated to v12 on my mid-2010 MBP (it's slow anyway, so /shrug).
briandear 8y ago
Don’t use uBlock, but content blockers on Safari work really well for me. There is also quite a lot of built in privacy protection already.
deleted 8y ago
[deleted]
saagarjha 8y ago
Apple doesn't provide a replacement extension, but they do vend a replacement API, the content blocking API. There are many extensions that use this.
peterkelly 8y ago
You can turn it back on. Go to Preferences -> Extensions and check "uBlock Origin". I've been using Safari 12 since it came out and uBlock Origin works with it just fine.
akvadrako 8y ago
You can get the Adblock Plus app, which using the new API. This is a tradeoff Apple made valuing privacy and performance over user freedom. The new content blocking API is safer and faster.
therealmarv 8y ago
same happened with Adguard and this was using non deprecated APIs (uBlock Origin was and is clearly using deprecated APIs). It seems for blocking stuff Apple changed the whole SDK on the browser!
merpnderp 8y ago
You might be thankful it was deactivated - it might have not been legit. https://github.com/el1t/uBlock-Safari/issues/69 https://github.com/el1t/uBlock-Safari/issues/69

by wyclif 8y ago

metafunctor 8y ago

It’s really just a suggestion to turn off some extensions. Haven’t bothered to figure out what triggers Safari to do that, but you can still run uBlock Origin on Safari 12 and it seems to work fine.

saagarjha 8y ago
> Haven’t bothered to figure out what triggers Safari to do that Safari has a new extensions model and will be deprecating the legacy one in a year. Hence the push to migrate to newer extensions.
- sweetp 8y ago
  the new extensions model is ridiculously useless... You need to build your extension in Xcode now, and for anything other than content blocking, the APIs are non existent... for instance, you can't even close tabs! I made an extremely simple extension using the new model around 2months - before I try migrating an older "actually useful" extension. But theres just no way its possible to migrate. Apple doesn't care about browser extensions now, it seems they want everyone to move to the new model, so they can collect revenue on sales on ad blockers. :(
  - tgragnato 8y ago
    > Apple doesn't care about browser extensions now, it seems they want everyone to move to the new model, so they can collect revenue on sales on ad blockers. The web is terrible without a serious adblocker and the available alternatives (paid or not) are unable to take away the same amount of junk. People will simply start using another browser.
  - akvadrako 8y ago
    This is wrong - you can inject arbitrary scripts and styles: https://developer.apple.com/documentation/safariservices/safari_app_extensions https://developer.apple.com/documentation/safariservices/saf...
    - wild_preference 8y ago
      You didn’t reply to or contradict anything they said. You need Xcode to build extensions and Safari has a super limited API. Executing JS and CSS don’t address either.
      - akvadrako 8y ago
        He didn’t say limited, he said nonexistent. More specifically, if you can inject scripts I don’t see why you couldn’t call window.close()

jurip 8y ago

I haven't tried uBlock Origin, but I'm running 1Blocker and Ka-Block! and they filter out most of the worst offenders.

euvitudo 8y ago

I just use uBlock Origin anyway (basically ignore the message). I don't see a difference in performance with the plugin when I updated to v12 on my mid-2010 MBP (it's slow anyway, so /shrug).

briandear 8y ago

Don’t use uBlock, but content blockers on Safari work really well for me. There is also quite a lot of built in privacy protection already.

deleted 8y ago

[deleted]

saagarjha 8y ago

Apple doesn't provide a replacement extension, but they do vend a replacement API, the content blocking API. There are many extensions that use this.

peterkelly 8y ago

You can turn it back on. Go to Preferences -> Extensions and check "uBlock Origin". I've been using Safari 12 since it came out and uBlock Origin works with it just fine.

akvadrako 8y ago

You can get the Adblock Plus app, which using the new API. This is a tradeoff Apple made valuing privacy and performance over user freedom. The new content blocking API is safer and faster.

therealmarv 8y ago

same happened with Adguard and this was using non deprecated APIs (uBlock Origin was and is clearly using deprecated APIs). It seems for blocking stuff Apple changed the whole SDK on the browser!

merpnderp 8y ago

You might be thankful it was deactivated - it might have not been legit. https://github.com/el1t/uBlock-Safari/issues/69 https://github.com/el1t/uBlock-Safari/issues/69