State of naming discussions

[Frando]

I'm still not sure about the Island term. It might be a good choice for a specific wording strategy in the frontend, but in the code it looks a bit weird.

What is it that we call island at the moment?

• A shared "address key" on which these feeds are swarmed in hyperswarm
• A specific set of feeds, and model by which is decided which feeds are allowed: Currently the "invite-spread" (the original author adds new feeds, those feeds can add feeds too). I likely wanna add the "shared-key" model too (all peers that know a certain public key are allowed to add any feeds they want). In the future, we might have additional trust- or moderation-based models.
• A specific kappa database. Currently all our views are "per island", which means they are completely seperated. If feeds are shared between islands, and if we want to enable shared search across all your local islands, we might want to change parts of that into a global local database, where all messages have a property with a list of address keys they belong to.

So, what is this, in a more technical sense? In Cobox its a group, in cabal its a cabal. I think for us space would make sense (as in our model the idea would still be that you can easily create islands/spaces that consist out of other islands/spaces). Possibly also context. Other suggestions?

[Frando]

Decision for now:

High-level terms:

• island -> collection Rename Island to Collection everywhere #51
• source -> feed

Records:

• add ref for key@seq string
• id stays id and is documented as "entity id"
• schema property becomes type. schema refers to the schema definition of a type.