infranet/README.md

48 lines
1.3 KiB
Markdown
Raw Normal View History

2022-03-24 09:11:25 +00:00
# InfraNet
2022-03-24 08:54:37 +00:00
Distributed & E2EE self-hosting
2022-03-24 09:11:25 +00:00
## Goals
2022-03-24 13:57:38 +00:00
2022-03-24 09:11:25 +00:00
* End-to-end encrypted
2022-03-24 09:19:22 +00:00
2022-03-24 09:11:25 +00:00
E2EE is a requirement for privacy.
2022-03-24 09:19:22 +00:00
2022-03-24 09:11:25 +00:00
* Collabrative
2022-03-24 09:19:22 +00:00
2022-03-24 09:28:32 +00:00
Members of the network are expected to cooperate to the best of their abilities, whether it's technical, financial or resources.
2022-03-24 09:19:22 +00:00
2022-03-24 09:11:25 +00:00
* Distributed, resilient, reliable and dynamic
2022-03-24 09:19:22 +00:00
2022-03-24 09:11:25 +00:00
Nodes should be able to join and leave without too much disruption. Bootstrapping, joining and autodiscovery should be as easy as possible, allowing for easy scaling across all members of the network.
2022-03-24 09:19:22 +00:00
2022-03-24 09:11:25 +00:00
* Free and open
2022-03-24 09:19:22 +00:00
2022-03-24 09:11:25 +00:00
All components should be free and open.
2022-03-24 09:19:22 +00:00
2022-03-24 09:11:25 +00:00
* Shared responsibility
2022-03-24 09:19:22 +00:00
2022-03-24 13:57:38 +00:00
Knowledge of components will be documented and shared and responsibility for the uptime and maintainence should be shared where possible.
2022-03-24 09:11:25 +00:00
## Design principles
2022-03-24 13:57:38 +00:00
2022-03-24 09:11:25 +00:00
* Tested
2022-03-24 09:19:22 +00:00
2022-03-24 09:44:06 +00:00
All components and goals should be testable to ensure changes don't impact existing functionality or reliabilty.
2022-03-24 09:19:22 +00:00
2022-03-24 09:11:25 +00:00
* Monitored
2022-03-24 09:19:22 +00:00
2022-03-24 09:11:25 +00:00
All components should be monitored and raise appropriate alerts to ensure good health and early detection of potential problems.
2022-03-24 09:44:06 +00:00
* Containerised
Simple, versioned components that can be resource constrained, when required, would be of great benefit.
* IPv6
Avoiding issues with IPv4 NAT, etc. would be desirable.
2022-03-24 09:46:47 +00:00
* Multi-architecture
The underlaying hardware type shouldn't be a constraint, within reason.