- JavaScript 80.6%
- CSS 6%
- WebAssembly 6%
- HTML 5.8%
- Shell 1.1%
- Other 0.5%
newMatrix
This is a fork of nuMatrix by arek.sh (https://codeberg.org/arek/nuMatrix). This fork is best-effort and time-allow only.
I found it more straightforward to fork his repo since he hasn't been active for months. If my updates & changes get incorporated, then I might drop this fork.
How to install ? Manually : -Download "Firefox for developpers" -In about:config, set xpinstall.signatures.required to false
- In about:addons, click on the settings wheel and select Install addon from file.
- Select the .zip file from the Releases tab
Firefox Add-on store :
(削除) The add-on is curently waiting approval. (削除ここまで)Mozilla not going to approve since changes not big enough.
Changes from nuMatrix :
Current :
- Updated native filter lists
- Removed cloud storage support for security reason.(Use manual backups)
- Update some recipes
- Updated screenshots to reflect changes made by Arek and Me.
Planned:
- The extension has been submitted to the AMO.
- Fix certain 1st-party websites unfairly being blocked (google, quora, reddit, etc).
HOW TO BUILD FROM SOURCE :
-
Run ./tools/make-firefox.sh from the home directory. DO NOT go into the tools directory because it will make the script fail sine it can't access all resources.
-
In dist/build you now have "newMatrix.firefox". Go into the folder, and select all files and folders. Then, compress all into a .zip file.
-
In a Firefox developper build, with the right flag in about:config, you should be able to drop the zip file directly into the about:addons page.
uMatrix and NuMatrix README's below
nuMatrix
Fork of uMatrix by Raymond Hill (https://github.com/gorhill/uMatrix).
Downloads
Download Firefox extension here: https://addons.mozilla.org/en-US/firefox/addon/numatrix/
I won't publish chrome builds until I'm happy with the state that the extension is in. You can clone the repo and run . ./tools/make-chromium.sh all to make a local unpacked.
The plan?
Not sure. Currently I'm adding little features here and there while I get comfortable with the code base.
Some things that have been added:
- Keyboard navigation
- Font column in the matrix
- 'Temporarily Allow' button when visiting a blocked URL
- Added new default blocklists
- Handling beacons as part of hyperlink auditing
- Display ambigious punycode URLs as ASCII
- Fixed a few bugs here and there
uMatrix
Definitely for advanced users.
Keep Github issues for actual bugs. User support is /r/uMatrix.
Forked and refactored from HTTP Switchboard.
You may contribute with translation work:
- For in-app strings, on Crowdin: uMatrix on Crowdin.
- For description (to be used in AMO, Chrome store, etc.), submit a pull request. Reference description is here ( feel free to improve as you wish, I am not a writer).
HTTP Switchboard's documentation is still relevant, except for uMatrix's differences with HTTP Switchboard.
You may contribute with documentation: uMatrix's wiki.
Warnings
Regarding broken sites
uMatrix does not guarantee that sites will work fine: it is for advanced users who can figure how to un-break sites, because essentially uMatrix is a firewall which works in relaxed block-all/allow-exceptionally mode out of the box: it is not unexpected that sites will break.
So this means do not file issues to report broken sites when the sites are broken because uMatrix does its job as expected. I will close any such issue without further comment.
Using uMatrix logger is key to un-break sites: the logger will show you all that uMatrix does internally.
I expect there will be community driven efforts for users to help each others. If uMatrix had a home, I would probably set up a forum, but I do not plan for such thing, I really just want to code, not manage web sites. If you need help to un-break a site when using uMatrix, you can try Wilders Security, where you are likely to receive help if needed, whether by me or other users.
uMatrix can be set to work
in allow-all/block-exceptionally
mode with a single click on the all cell in the global scope *, if you prefer to work this way. This will of course
break less sites, but you would then lose all the benefits which comes with block-all/allow-exceptionally mode -- though
you will still benefit from the 62,000+ blacklisted hostnames by default.