The uMatrix extension, created by Raymond Hill (uBlock Origin developer), offered granular control over website permissions and subresource requests. When deprecated in favor of uBlock Origin, users faced a dilemma: uBOLite, the MV3 successor, removed these critical permission controls. This left privacy-conscious users searching for alternatives to manage third-party access effectively.

The technical challenge lies in rebuilding uMatrix's functionality under Manifest V3's restrictions, which eliminate callback-based request blocking. The proposed solution leverages declarativeNetRequest policies combined with Content-Security-Policy. This approach allows developers to declare rules in advance rather than executing JavaScript on each request, though with some capability limitations compared to the original.

Implementing this vision requires creating a reporting endpoint to capture security violations and populate a list of subresources to allow or deny. The author has already developed a prototype called matrix³, demonstrating the concept's viability. The minimal codebase can be loaded directly in Chrome without dependencies, offering hope for those unwilling to sacrifice permission control in the name of browser security updates.

Browser extensions like uMatrix empowered users to decide which resources websites could load, preventing tracking and unnecessary bandwidth usage. With the migration to Manifest V3, this functionality becomes increasingly important as users seek ways to maintain control over their browsing experience despite platform limitations.