- Edited
As I've joined the Orion community and started frequenting its forum, one thing that has come to my attention more and more is the apparent cycle of Example Extension Gets Updated --> Example Extension Ceases to Work Correctly in Orion --> The Community Complains --> Kagi Update Orion.
The company currently promote certain extensions as "Popular Extensions" right within Orion;
Inside is a relatively modest collection of extensions with (presumably) a large number of users - including some password managers, such as Proton Pass (which I use), and 1Password (which it seems literally every other living person on the forum is currently using... #NotBitter).
I think it's a poor user experience if the browser essentially promotes an extension to you, you install it, and either it never works properly or it silently breaks the next time the extension's author pushes an update. It's one thing if a relatively indie tech company makes a browser, says they'll try to support all Firefox & Chrome extensions, and occasionally there's breakages. But when they have specifically promoted an extension to you themselves, and then that breaks..? It's just a bad look.
So my thinking is that only for a select few browser extensions that are widely used in the Orion userbase, Kagi could have Orion not automatically update those extensions until the update has been tested internally by the team, and / or has been tested by those using RC builds of Orion. If an extension is flagged as a "Popular Extension", Kagi's servers could maintain a list of their names & version numbers - only performing an automatic update for that extension if it wouldn't lead to a higher version number than the one vetted by Kagi.
I have to give a lot of credit to @laiz for testing my suggestion and forcing me to iterate upon it! One of the things laiz brought to my attention is the question of whether Orion, by default, automatically updates extensions. I'm assuming it will by v1.0 if it isn't already - and it's a setting many will turn on in any case.