pull down to refresh
a sub sub space would probably look like user.bob@bitcoin
we wanted to avoid name collisions with traditional DNS which is why we chose this syntax
reply
what do you do for a sub sub space? user.subsubspace.subspace@space? the syntax just seems weird.
reply
do we even need sub sub spaces? what use cases do you have in mind?
with this syntax, is there a way to distinguish between a subspace that was delegated via the spaces protocol or inside a zonefile that has been attached to the space?
reply
yes checkout the current proposed draft https://github.com/spacesprotocol/sips/blob/main/sip-0002.mediawiki
but there are still going to be collisions with all TLD, right?
reply
since the inception of the internet no email addresses have been defined directly on the tld so practically no collisions sip-02 also attempts to make this as painless as possible to integrate even into mainstream resolvers
sorry I mean we used this syntax to make it less confusing with any conflicts with other naming systems
reply
I agree this is an issue, but I don't know that I like the syntax you've chosen. Not sure what a good solution is though.
reply
can a space have a
. in it's name?reply
no, it has the same rules as a traditional dns name
reply
bob@bitcoin,bobis a subspace of the parent spacebitcoin. What about sub-sub-spaces? What do those look like?