3 ms·

> Spheres also power a petname linking system, a kind of hyperlocal distributed DNS. > @gordon/composability This is where (one of) the problem lies, in my vi

> Spheres also power a petname linking system, a kind of hyperlocal distributed DNS. > @gordon/composability This is where (one of) the problem lies, in my view. @gordon is essentially an equivalent of a DNS system. The difference, however, is that you are trying to identify a file. There should be only one namespace, not many. @gordon/composability shouldn't be different than @simon/composability. "composability" should be simply the unique ID for a specific file. > The plot twist is that spheres don’t point to a particular server! Instead, spheres are data structures that live on IPFS. Oh, but it seems that you agree with me!! Except, you don't. I'm just very confused. People should try to ELI5 things, instead of trying to sound too smart but failing at serving a clear explanation.

cdata 4y ago
> There should be only one namespace, not many. @gordon/composability shouldn't be different than @simon/composability. Thanks for this interesting provocation! In Noosphere and Subconscious, we are trying to relax the tension between "I can write to any name in the space" and "I don't want what I write to be clobbered by other people writing to the same name in the space." So, you have a personal scope where only you have write access. We call it a sphere. Within the sphere, you save files to a flat namespace. Other users can write to the same flat namespace in their spheres. And, when you follow another user, Subconscious will collide the namespaces in the UI. So, the content in @gordon/composability and @simon/composability will appear next to each other.