Unlocking Desktop, doesn't unlock browser extention

Hey @"jack.platten",

I understand that Chromium isn't code signed, but I'm still curious whether there's a way to 'disable' this security/integrity somehow, as previous extensions worked just fine when DIY'ing a workaround. It doesn't even need to be a toggle in the app, even an app-level or configuration file patch that I'd have to (re)apply manually every time the app updates would more than satisfy me.

Of course, I understand that there is a technical argument to be made with regards to near-guaranteeing the safety of the extensions by only talking to code-signed browsers, but to the (highly technical) users that go out of their way to (constantly) compile and run up-to-date Chromium builds, this feels like more of a limitation. At least speaking for myself, I don't run Chromium because I enjoy compiling my own browser for hours every week, but rather because even though Google's track record with privacy and the protection of user data is arguably poor at best, they still make the most web-compatible browser out there these days.

Thanks