Haketilo

How about updating site scripts only when the user visits that site? There would only ever be a single script API request at a time. Plus we could allow the user to configure whether the extension should automatically query the repo for updates upon a visit to a site and how often such a query should be allowed to happen.

the most likely first adopters tend to be very concerned about that

True. Obviously, we're going to also make the repo available as .onion. Making an .i2p version would also make sense

How about updating site scripts only when the user visits that site? There would only ever be a single script API request at a time. Plus we could allow the user to configure whether the extension should automatically query the repo for updates upon a visit to a site and how often such a query should be allowed to happen.

Maybe; could that then somehow make automatic updates leak information on which sites a person visits and when, however?

I might try asking some of the people who raised the issue for Audacity, as they (I assume) know something about update system requirements. Actually, now that I think of it, a few of thing mentioned using LibreJS- perhaps they would be interested!

Obviously, we're going to also make the repo available as .onion. Making an .i2p version would also make sense

Now that's a good idea!

Well, I seem to have misremembered some parts of threads and can't find others, which leaves asking a much less plausible option.

Your suggestion seems like a good idea overall; if you're happy to I would suggest adopting that, perhaps adding the option to update everything at once too.

EDIT: Actually, I noticed the issue is "Plan the update system", not "implement", so we indeed can discuss this now

Still, thank for raising the point! I only filed this under the assumption that you would be starting work on updates soon, which it's useful to know won't actually be happening for a while.