Not an issue: just a place to drop images for doc

[gorhill]

Used in https://github.com/gorhill/uBlock/wiki/Tips-and-tricks-waterfall#why-using-a-blocker-is-very-important

[gwarser]

Maybe use project page for this? https://help.github.com/articles/creating-project-pages-manually/

[gorhill]

Maybe use project page for this?

I'm too lazy to start yet another side project for now.

[gorhill]

Reference for translators:

[smed79]

Why 41% of Arabic translation is not approved?

[0xBRM]

@SMed79 I'm pretty sure you need to vote on the translations. Just hit the plus button.

[gorhill]

@SMed79

Why 41% of Arabic translation is not approved?

A proofreader needs to validate the non-validated entries. There are so many translators now that I can't keep track anymore of who is a proofreader or not. I just gave you proofreader status in Crowdin.

[smed79]

@gorhill Thank you for the new status!

[gorhill]

[gorhill]

[gorhill]

For translators:

This is the UI for creating static filter from the logger:

The goal was to stick as much as possible to natural language to create a filter: So what you see above was built using a template, which is as follow for the English version:

{{action}} network requests of {{type}} {{br}}which URL address matches {{url}} {{br}}and which originates from {{origin}},{{br}}{{importance}} there is a matching exception filter.

This templating means you can re-order the parts of the sentence as you wish, to what makes the most sense in your language.

For all {{...}}, this will be replaced by one string.

There are two exceptions, which are the {{type}} and {{origin}} placeholders. These will be replaced by another template, the loggerStaticFilteringSentencePartType and loggerStaticFilteringSentencePartOrigin in messages.json: type “{{type}}” and from “{{origin}}” respectively.

In these sub-templates, {{type}}/{{origin}} will be replaced by the language-independant type/origin of the request (image, css, arstechnica.com, etc.), and the result will be used in the main sentence to replace {{type}}/{{origin}}.

{{br}} forces a new line in the UI. It's optional, you do not have to use it, use it if you think it make the whole thing look better.

I am not a linguist, so I am not sure the current main template fits all languages, hopefully it does. The goal is not to find the perfect sentence -- that would grow code complexity exponentially, but more like to get something which is much easier to read and interact with than the plain and stern syntax of static filtering (i.e. ||cdn.arstechnica.net/wp-content/themes/arstechnica/assets/images/social-icons.png$image,domain=arstechnica.com).

Edit: It was brought to my attention that {{origin}} should also use a sub-template (from {{origin}}) just like the {{type}} one. So I will fix this and re-upload. I modified the text above to reflect this.

[gorhill]

Used in https://github.com/gorhill/uBlock/wiki/Dashboard:-Settings.

[gorhill]

Used in https://github.com/gorhill/uBlock/wiki/The-network-request-logger.

[gorhill]

Used in https://github.com/gorhill/uBlock/wiki/Dashboard:-Settings.

[gorhill]

For translators:

[gorhill]

For translators:

[gorhill]

[gorhill]

Reverse lookup worker in Nightly: the filter lists need to be kept in live memory while the reverse lookup service is alive.

[gorhill]

[gorhill]

[gorhill]

[gorhill]

[gorhill]

[gorhill]

Background info: https://www.privateinternetaccess.com/forum/discussion/8204/how-to-stop-webrtc-local-ip-address-leaks-on-google-chrome-and-mozilla-firefox-while-using-private-i

Test case: https://diafygi.github.io/webrtc-ips/

[gorhill]

Some reality check is in order.

[gorhill]

[seanrand]

@gorhill: Maybe not the right place to discuss this, but what does the </> button do and what does the eye icon indicate? Unless I'm blind, it's not documented on the wiki.

Edit: I'm blind, apparently. The eye indicates "behind-the-scene network requests", almost figured as much - just didn't look in the right place.

[0xBRM]

@seanrand The </> button is used to access uBlock's DOM inspector.

[seanrand]

@CrisBRM Oh, thanks for clearing that up. I only clicked it on the "All" tab, so I was slightly confused as all it seemed to do was collapse/hide the network log. There's no DOM to inspect on the "All" and "Behind the scene" tabs, obviously.

[gorhill]

For translators:

Experimental feature: new dynamic filtering type: 3rd-party passive content, for css/images. Allows to un-break rendering of a page when using default-deny for 3rd parties, without enabling 3rd-party active content, i.e. scripts/frames. Using techcrunch.com as an example:

[gorhill]

[gorhill]

[gorhill]

[gorhill]

Globally blocking 3rd-party frames.

[gorhill]

[gorhill]

[gorhill]