Practicality of automatic new build distribution #1012
backtopyramidone
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
It's inevitable that software updates will introduce new features that will eventually inhibit the functionality of nodes that are not periodically updated.
Is it feasible to distribute binaries, or perhaps source code with all required dependencies through the network? Would releases need to be signed, and by whom?
If the goal is to avoid centralization of firmware updates, I suppose certain nodes could voluntarily host the necessary files. Advertisements between peers could serve as notice about whether a particular node is serving files.
This responsibility could also be deferred to the regional network operator, or whoever happens to be provisioning a large number of nodes. Yggdrasil would be competitive with typical provider-based services if it functioned seamlessly. At the moment, it is rather unintuitive for the typical user and lacks a phone number for technical support.
This is more about engineering for human factors. We want people to find that the software is easy to use.
Beta Was this translation helpful? Give feedback.
All reactions