Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow decentralized component updates to be served #53

Open
bbondy opened this issue Jan 20, 2021 · 0 comments
Open

Allow decentralized component updates to be served #53

bbondy opened this issue Jan 20, 2021 · 0 comments

Comments

@bbondy
Copy link
Member

bbondy commented Jan 20, 2021

Currently only extensions that are on the Google store can be installed.

It would be neat to have the ability for user's to set their own component update server URL in Brave.
Once this is set, perhaps via a local environment variable. We could allow users of Brave browser to point to our go-update endpoint with a particular subdomain. Perhaps via a location that requires administrator access, like an admin policy.

This particular subdomain could be of the format
https://<libp2p-key>.go-updater.brave.com/extensions

When this is done, go-update could merge the served manifest with one controlled by an IPNS URI.

Alternatively, users could host their own go-update servers with their own backend and offering their own extensions. For an extension request that they didn't know about, they'd forward it to our component update server, just like we do when we don't know about an ID to Google's.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant