This extension was installed without my consent. Seeing as this extension greatly improves fingerprinting surface, might I suggest you query users prior to installation?
When opening a WebSocket connection, the original User-Agent header is sent (matches navigator.userAgent, doesn't include "Fedora"). The same might apply to EventSource connections.
Many sites (including ours) use the User-Agent for PHP session security; if it doesn't match, the session is invalidated.
When going to https://gitlab.com/users/sign_in with extension enabled I'm stuck on
screen with 503 error returned from Gitlab saying Javascript has to be enabled. As soon as the extension gets disabled proper Sign in form is presented.
Additional information: This extension stopped working after upgrading to Chrome 100.
The extension is leaking memory. When the browser starts it's ok with usage 18.5MB of RAM (5.8MB for JavaScript) but it increases with every page. After several minutes the usage increases to 26.4MB of RAM (10.4MB for JavaScript).
After all day usage I saw it to be more than 56MB of RAM (3x increase in memory usage) which is a lot for basic changing of the user agent.
I'm attaching two screenshots from fresh start and after 20 minutes of browsing.
I happened to notice that at least on Firefox downloaded directly from Mozilla, my user-agent is Mozilla/5.0 (X11; Linux x86_64; rv:100.0) Gecko/20100101 Firefox/100.0 without mentioning Fedora, so I think it could be useful for the extension to be also available on Firefox or Firefox store.
When accessing the user agent via navigator.userAgent it does not report Fedora (it does correctly report Fedora in the http header of outgoing requests).