Live data from Hacker News

UBlock Origin 1.17.4 released

github.com

81–90 of 158 posts

Re: UBlock Origin 1.17.4 released

#81
post #69

Earlier quoted context omitted.

Interestingly, my numbers are completely different relative to each other when compared with yours... I wonder how the number of runs is determined and if this affects the results. Benchmarking, the higher ops/sec the better. Firefox 63.0 on Fedora 64-bit. Test 100 needles against 16 dictionaries of hostnames - Set-based x 1,707 ops/sec ±1.93% (60 runs sampled) - Regex-based x 4,078 ops/sec ±0.88% (25 runs sampled) -…

For some reasons, I found that Firefox's results for WASM are always better after a first run -- i.e. clicking "Lookup" again without reloading the page. I don't know what is the explanation of this.

Firefox can cache the compiled WASM. So perhaps your benchmarks include compilation warm-up on the first run.

Re: UBlock Origin 1.17.4 released

#82

Sorry to burst everyone's bubble, but in this test uBlock Origin failed miserably, to say the least. https://avlab.pl/test-web-browser-extensions-protection-agai...

uBlock Origin + Google's Safe Browsing (or SmartScreen if you're an Edge user) should be enough for just about anyone. Furthermore one of the strengths of uBO is the ability to use dynamic filtering[1] which bypasses the filter list problem entirely.

[1] https://github.com/gorhill/uBlock/wiki/Blocking-mode:-medium...

Re: UBlock Origin 1.17.4 released

#83
> The original prototype was to develop an idea I had about using jump indices in a TypedArray for quickly matching hostnames (or more generally strings)[1]. Once I had a working, un-optimized prototype, I realized I had ended up with something formally named a "trie": " rel="nofollow">https://en.wikipedia.org/wiki/Trie>, hence the name. I have no idea whether the implementation here or one resembling it has been done elsewhere.

So I heavily experimented with squeezing performance out of a JS-based trie-implementation for LZString[0]. Back then some early experimentation suggested that using TypedArrays was likely to be slower than using objects with numerical keys, and for non-degenerate input using a trie based on plain arrays and indexOf calls was the fastest[1]. However, it's been a while since I looked at those numbers (and I suspect that with uBlock's use case look-up performance matters more than insertion performance, which makes it very different from LZString's).

But it should be obvious that HNTrie's implementation[2] is something I'm very interested in ;).

[0] https://github.com/pieroxy/lz-string/pull/98

[1] https://github.com/pieroxy/lz-string/blob/ba8988028d78962eba...

[2] https://github.com/gorhill/uBlock/blob/2a91a685ce3d2dae5d3c2...

Re: UBlock Origin 1.17.4 released

#85

UBlock Origin is more than an ad-blocker. Some usecases other than being ad-blocker 1. Hide Quora notification icon 2. Hide YouTube notification icon 3. Hide stackoverflow questions you might be interested section(right bottom section) How do you use other than ad-blocker?

Example: I use default-deny 3rd party scripts and frames + disable javascript everywhere by default. I temporarily enable these only on a per-site basis only if really needed (permanently for the few sites I visit regularly).

Re: UBlock Origin 1.17.4 released

#86

> The original prototype was to develop an idea I had about using jump indices in a TypedArray for quickly matching hostnames (or more generally strings)[1]. Once I had a working, un-optimized prototype, I realized I had ended up with something formally named a "trie": " rel="nofollow">https://en.wikipedia.org/wiki/Trie> , hence the name. I have no idea whether the implementation here or one resembling it has been do…

Addendum: to clarify, with "non-degenerate input" I mean that for the vast majority of nodes in the resulting trie we have a handful of charCodes to search through at most. This holds true for most normal types of text. It is however trivial to create string that breaks this assumption: make one that features every legal UTF16 charCode. Throwing this at lzstring-unsafe.js will freeze it. So this could be another assumption that does not hold for uBlock's use case.

Re: UBlock Origin 1.17.4 released

#87
post #61

Earlier quoted context omitted.

He writes in his FAQ [1]: > I don't want the administrative workload coming with donations. I don't want the project to become in need of funding in any way: no dedicated home page + no forum = no cost = no need for funding. I want to be free to move onto something else if ever I get tired working on these projects (no donations = no expectations). > Have a thought for the maintainers of the various lists. These list…

Dude could still do a monthly patreon and cancel it if he didn't want to work on it anymore

The maintainer of Ublock Origin does not want to make money from this. He does not want Ublock to turn into Adblock Plus.

If there is no money involved the project cannot be bribed by ad tech. The only acceptable ads are the ones the user white lists.

Re: UBlock Origin 1.17.4 released

#88

UBlock Origin is more than an ad-blocker. Some usecases other than being ad-blocker 1. Hide Quora notification icon 2. Hide YouTube notification icon 3. Hide stackoverflow questions you might be interested section(right bottom section) How do you use other than ad-blocker?

Hide gmail's quick-reply suggestions

Re: UBlock Origin 1.17.4 released

#89

Earlier quoted context omitted.

I've got this list in my favs, I think it was posted on HN a while ago: https://gist.github.com/0XDE57/fbd302cef7693e62c769 I had some problems with sendRefererHeader, so it can definitely break some websites

See, there are some good ideas in that list, but then it gets to disabling Safe Browsing without any explanation. There's a lot of false information around about what Safe Browsing sends to whom, and you should make sure you know what you're doing when disabling it. Also, the DNS cache size explanation is a bit backwards. "Number of cached DNS entries. Lower number = More requests but less data stored." Where do you…

> don't blindly apply settings from this list.

Unfortunately, there is no real documentation of the various about:config parameters. So one has to trust doubtful sources on what settings would be useful, or spend many hours reading the source code of Firefox.

I don't understand why each setting is not documented on the about:config page. It would bind the documentation to the release, providing the info suitable for the FF version. I can't see any drawback, except that developers would have to provide a small description of every setting they introduce, which I hope they already do somewhere.

Here is my own frustrating experience with about:config. I sometimes hit Ctrl-q when I meant Ctrl-w. So instead of closing a tab in FF, I close the application and loose my input on some pages. I tried to restore the (previously default) behavior of asking for confirmation before quitting. I had 2 settings in "about:config" named "browser.warnOnQuit" and "browser.showQuitWarning". Only the former one is documented in the mozillaZine wiki. It seems the latter was the old name of this setting, which FF updates never migrated.

So I changed the config, and nothing happened. After several variations, I headed for the source code of FF, and saw this setting was ignored when "restoring sessions" was active. There is no way to ask for confirmation in modern FF.

Re: UBlock Origin 1.17.4 released

#90
post #71
post #68

Earlier quoted context omitted.

Is that income uniquely difficult to explain?

How would you explain that you're making money from a project summary of UBlock?

Patreon sends a 1099-K if you get more than $20K in a year.

https://support.patreon.com/hc/en-us/articles/207099566-Will...

Post reply on HN