Basic per-domain settings (which also allow blocking/allowing Javascript for a page, though not for different origins on that page) have been around since qutebrowser v1.2.0 (March 2018).
For more sophisticated uMatrix-like blocking, work is ongoing on an extension API, but there's jmatrix which already uses that API unofficially. I plan to get back to the extension API soon, but there are some more important things to take care of first - see the current roadmap for details. Also, I expect things to go much faster soon, as I finished my studies and I'll soon be able to start working part-time on qutebrowser funded by donations (via GitHub sponsors).
Basic per-domain settings (which also allow blocking/allowing Javascript for a page, though not for different origins on that page) have been around since qutebrowser v1.2.0 (March 2018).
For more sophisticated uMatrix-like blocking, work is ongoing on an extension API, but there's jmatrix which already uses that API unofficially. I plan to get back to the extension API soon, but there are some more important things to take care of first - see the current roadmap for details. Also, I expect things to go much faster soon, as I finished my studies and I'll soon be able to start working part-time on qutebrowser funded by donations (via GitHub sponsors).
Some links:
v1.2.0 release: https://lists.schokokeks.org/pipermail/qutebrowser-announce/... jmatrix: https://gitlab.com/jgkamat/jmatrix roadmap: https://lists.schokokeks.org/pipermail/qutebrowser-announce/... GitHub sponsors: https://github.com/sponsors/The-Compiler/ related issues: https://github.com/qutebrowser/qutebrowser/issues/30 https://github.com/qutebrowser/qutebrowser/issues/28