HQCore Federation #9
Description
This is a goal for way in the future, but it is an important feature that shouldn't be forgotten about.
Once clusters properly define scope and users can share devices, it should be a goal to allow hq-core servers to communicate with other hq-core servers. This would involve uniquely identifying the server, then granting access to certain devices and clusters to another federated instance.
This also expands into the concept of having a hub for federated instances. A hub would need to be a separate web server. This might start out as hq view, the client front end for project hq. Later on, maybe it will develop into the dashboard/profile page for a public facing instance shared to a federated hub. This hub might be restricted to a very small group of peers, or could be opened to the public. It all depends on the restrictions around the hub -- the hq-core server owner is the one who ultimately determines what data is allowed to be accessed.
In the end, this allows for users to be in full control of their data, while also allowing them to share it safely with a friend, or efficiently enough to share logged information with the world.