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.

Sign up for GitHub

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

Jump to bottom

Non-garlic-routed updates of plugin #6

Closed
eyedeekay opened this issue Jun 24, 2019 · 1 comment
Closed

Non-garlic-routed updates of plugin #6

eyedeekay opened this issue Jun 24, 2019 · 1 comment

Comments

@eyedeekay
Copy link
Owner

eyedeekay commented Jun 24, 2019 •
edited

When using AMO, plugins will probably be fetched over clearnet.
@eyedeekay eyedeekay changed the title Non-private updates of plugin Non-garlic-routed updates of plugin Jun 24, 2019
@eyedeekay eyedeekay mentioned this issue Jun 24, 2019
Closed
@eyedeekay
Copy link
Owner Author

It seems like it does honor proxy settings, so this is pretty much a non-issue. If somebody installs from AMO, they update from AMO, it's that simple. The real business then becomes creating the update mechanism for the non-AMO version of the plugin, which I think should follow different principles(Be inside I2P, possible leverage Bittorrent, etc).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@eyedeekay