sleepy.bike does not need other communities then it’s own only

[mariha]

I am advocating for an app where:

• user owns theirs data - data storage is decoupled from the app and access to the data can be managed independently from the app
• data is not shared between platforms/communities

For this, for me there should be only one community on sleepy.bike.

—-

If there were other communities in the network federated with sleepy.bike: either other instances of same software or different software using common ohn-protocol, they would need a way to establish and manage relationship of trust between them (which communities are visible to our members? which communities we trust to be visible to them?). That could be stored in a config file and entered manually by admins, maybe overwritten by a user in their profile.

List of profiles from the other platform (with geolocation) could be either stored on a server as an index and accessed by other communities’ members (permissions and groups controlled via Solid) or broadcasted (via ActivityPub) to other communities and replicated locally on each community’s own server.

[weex]

That makes sense and is a helpful simplification of the app. There's only one community per instance. That means we can remove the communities screen and also close #6. If I wish to make a new community, I should host a new instance and change the configuration so its identity is the one that's used.