search

el1t / uBlock-Safari

uBlock Origin - An efficient blocker for Chromium, Firefox, and Safari. Fast and lean.
GNU General Public License v3.0
2.75k stars 97 forks source link

Is the Safari port dead? #130

Closed georgeperez closed 4 years ago

georgeperez commented 6 years ago

Describe the issue

Is the Safari port project dead? There's been no contributor activity since April 23 and the only pull request is stale. Is the project dead?

One or more specific URLs where the issue occurs

N/A

Screenshot in which the issue can be seen

N/A

Steps for anyone to reproduce the issue

N/A

Your settings

Your filter lists

N/A

Your custom filters (if any)
ykqmain commented 6 years ago

I also want to know.

Flenville commented 6 years ago

el1t, the guy behind the safari port, seems to take a break from coding, at least here on GitHub. As far as I understand, most work in the past has been done by him. I wouldn't go as far as saying the port is dead, but its main developer seems at least to be on a break. So, time to update that Firefox of yours ;)

screen shot 2018-07-20 at 13 05 59

vassudanagunta commented 6 years ago

Yes, clearly @el1t has a life besides this project. I hope he is happy!

There are other issues such as #124. Apple makes it hard to do open source Safari Extensions.

But perhaps the key thing is this discussion: #112. I'd love for both @el1t and @gorhill to give us their thoughts.

georgeperez commented 6 years ago

@Flenville Yeah I noticed that when I read the release notes for the latest version (which is broken, unfortunately). That's mainly why I asked, since the issue of uBlock whitelisted/blacklisted states being permanently stuck on one setting after whitelisting/blacklisting a site quickly came up in the issues page but no hot fix came.

(To better explain the issue, if you were on a site that you whitelisted and then go to a blacklisted site that site would be whitelisted instead, or vice versa by going to a site that has its elements blocked and then when you go to a website that should be whitelisted but had its elements blocked)

I would update my Firefox if it worked on Mojave at the moment! Currently crashing on launch. I'm using a Safari Content Blocker for the time being.

Freida-Moo-Goo-Gai-Pan commented 6 years ago

Suddenly the current port doesn't block disqus comments for me anymore, pages load slower, etc... I finally went back to AdGuard.

The Chrome version still works perfectly fine, but I prefer Safari.

ykqmain commented 6 years ago

If this project stops maintenance, I will choose AdGuard instead of changing the browser. Safari is easy to sync between macOS and iOS, I also have Chrome as the second browser.

rnemec commented 6 years ago

Are there any forks that seem to pick up the good work?

vassudanagunta commented 6 years ago

@gorhill only links to this one. I doubt there are any others, as I don't think it is easy work, it is a thankless job (people only complain, even though the maintainer is doing the work for free, with no help from any of the complainers), and Apple makes it even harder by requiring Developer Program membership (perhaps for good reason, I'm just stating fact).

LesterJitsi commented 6 years ago

@vassudanagunta That's exactly what I think too. I'd just say that letting us know the port is dead would be much easier work.

michael1900 commented 6 years ago

Why no more release? Alternatives?

NeXrom commented 6 years ago

Nothing new, sad sad

adrianmihalko commented 6 years ago

What is the best alternative?

NeXrom commented 6 years ago

AdGuard

Vertux commented 6 years ago

@NeXrom

AdGuard

Thats no alternative, that's just a very commercial product - I would be happy to support uBlock if it would keep the project alive, but not a product like AdGuard.

adrianmihalko commented 6 years ago

I keep uBlock Origin. It does not slows down browser, it's just a warning.

freediverx commented 6 years ago

Next year’s MacOS update will kill it for good.

On Sep 22, 2018, at 11:56 AM, adrianmihalko notifications@github.com wrote:

I keep uBlock Origin. It does not slows down browser, it's just a warning.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

monster4lif commented 6 years ago

I for one would be willing to donate to keep getting updates. Maybe it would be worth setting up a GoFund or something of the sort, so the dev can afford to spend more time on it?

p-eh commented 6 years ago

would also donate happily.

sporkman commented 6 years ago

I'll give $40.

tohuw commented 6 years ago

I'd also donate. The extension no longer properly functions for me (when I switch tabs, references from the previous tab appear in the advanced window, and some settings don't lock in when clicking the lock icon). I'm not going to bother opening new issues for these given what's discussed here, but I would donate to a revival of efforts on this project.