Bring back preset rules

[gorhill]

In a different, more flexible form. For example, we want regions to be able to create their own rules, and for users to import community-contributed rules, with no dependency on the Github repository.

Not sure if I will wait for this before shipping though, it's a big item.

I believe this could be accomplished later to appeal to a wider audience when you're close to a 1.x release, though I must state that this is just my opinion.

By the way, excellent work @gorhill! Loving the changes thus far!

[nyanpasu64]

New idea: Some sites integrate with Google Drive or Github. Is it possible to "inherit" rules from other domains? So if a web-app integrates with Drive, you can have it inherit Google Drive privileges and communicate unhindered?

This is just an idea, I haven't fully thought it out yet (how it interacts with global or 1st-party rules, etc.)

[WagnerGMD]

I believe too that uMatrix could be better. Like said a lot of website integrate YouTube (etc). So, via one click on the button, uMatrix should be eable to create (directly) the right rules for the media (etc). Only a few rules are enough.
It would be useful because one user simply need somtimes to create temporary rules. By default, it sould be temporary. After, the user confirm (save).
I block everything. Then, no I don't want to create a global rule like :
* ytimg.com image allow
Also, it will simplify the process when a user start from scratch. I think about regulary, since a very long time (>6 months). It could be nice as a new (or back ? Recipes ?) feature and perhaps gorhill the day to be brave is not far...

One example below :

malwaretips.com s.ytimg.com css allow
malwaretips.com ytimg.com image allow
malwaretips.com s.ytimg.com script allow
malwaretips.com www.youtube.com script allow
malwaretips.com www.youtube.com xhr allow
malwaretips.com www.youtube.com frame allow
malwaretips.com googlevideo.com xhr allow
malwaretips.com redirector.googlevideo.com * block
-----------------------------------------
## Comment 
## It's works fine
* * * block
* redirector.googlevideo.com * block
-----------------------------------------

Perhaps there's also something about (the damn) Recaptcha :

https://www.google.com/recaptcha/
## By the past : https://www.gstatic.com/recaptcha/
## To complete one day...
## Recaptcha doesn't figure on the url, it's loaded by two websites (google.com and gstatic.com).
* www.google.com frame allow
* www.google.com image allow
* www.google.com script allow
* www.google.com xhr allow
* www.gstatic.com image allow
* www.gstatic.com script allow

[Penguin-Guru]

I've been using an extension called Stylish lately to adjust C.S.S. It has a "style template" sharing interface that is very convenient since it is only two clicks and provides a nice preview. Perhaps this could provide a good reference? I have described what I imagine below. This would be designed for quick adjustments and sharing, not for bulk scope management. Bulk scope management is basically already provided by the "Options>My rules" page, although it might be useful to separate imported rules to be committed, at least temporarily.

A single button, perhaps left of Refresh in the drop-down, could open a dialogue or simply change the drop-down panel to review/edit the current scope before uploading. This would ensure users know what is being submitted, doubling as confirmation, and allow them to add comments and name/describe the rule set.

For those installing, they could select from a list of names or use arrow buttons to preview the new rule set before applying and refreshing (one button). If rules are previewed in the normal matrix panel, comments could be displayed above, or floating below or to the side depending on the display size. This would allow users to read the notes, or any other non-matrix rule information without opening the settings menu; perhaps they should only display when previewing.

Theoretically, I don't think it would be necessary for templates to be explicitly named or described since the scope and rules would clearly identify them and comments could be used to indicate the rules' purpose. The only problem I imagine would be those rules for domains that have not yet been referenced by the active page, which would have to be added to the matrix for preview and might be a bit confusing. Realistically, I don't know how many users would properly comment their scopes so it might be worth providing a blank name field "## Name: " in the header to encourage good practice, or just requiring a name before uploading to be safe.

[gorhill]

For translators:

[TonnesM]

@gorhill

1. Are you sure you don’t need to invalidate the 3 additional (changed) ubiquitousRulesPageName, hostsFilesAutoUpdatePrompt & hostsFilesExternalListsHint strings for locales on Crowdin to to prevent them from remaining unnoticed?
2. While at it, can you please remember not to include trailing periods for option text strings such as "Auto-update assets" and fix it?