At the moment, the client seems to be working exclusively on ONE network, should it be the official Anytype network or a self-hosted one.
Users may want to collaborate on mutiple networks though, like a user using the Anytype network but wanting to join also a self-hosted network.
Or a user with a self-hosted network wanting to joing another self-hosted network.
HOW COULD IT BE DONE?
ᅟFirst the client should allow loading mutliple client.yml, and manage multiple named networks (add, remove, rename, etc…). being able to name a network would be rather important but that can be client only.
In the UI, we spaces should be grouped by network or simply merged but the client needs to be know which space belongs to which network.
REAL WORLD USE CASES
The main differenciator of Anytype is its local first architecture and p2p capabilities.
Supporting mutliple network allows smoother transition or even parallel usage of the official Anytype network, side by side with 1..n slef hosted networks.
RECOMMENDED ALTERNATIVES
The alternative is to force a user on a given network which is not great.
I just would not implement exactly as described in what you linked. The point of the user is however valid and I would reword it as:
once Anytype supports multiple networks, each space is known to be linked to a specific network.
For that user, it may sound appealing to be able to toggle a network ON/OFF, effectively preventing sync.
However, since this user uses LOCAL “Network”, sync means nothing in that context. So I think the user considers that spaces could be synced on a network OR another, which I would definitely not go into.
In my request, I think a space should belong to a single network and the client should be able to know about multiple named networks, and my goal would be to see spaces side by side like: