pull down to refresh

0 sats \ 11 replies \ @andy 10 Nov \ on: Spaces Protocol to go live on Bitcoin Mainnet on block 871222 bitcoin
with bob@bitcoin, bob is a subspace of the parent space bitcoin. What about sub-sub-spaces? What do those look like?
Why not user@bob.bitcoin as a delegation like is done with traditional DNS?
write
preview
0 sats \ 10 replies \ @ca98am79 OP 10 Nov
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
0 sats \ 1 reply \ @andy 11 Nov
what do you do for a sub sub space? user.subsubspace.subspace@space? the syntax just seems weird.
reply
0 sats \ 0 replies \ @buffrr 11 Nov freebie
do we even need sub sub spaces? what use cases do you have in mind?
0 sats \ 1 reply \ @andy 11 Nov
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
0 sats \ 0 replies \ @buffrr 11 Nov freebie
yes checkout the current proposed draft https://github.com/spacesprotocol/sips/blob/main/sip-0002.mediawiki
0 sats \ 5 replies \ @andy 10 Nov
but there are still going to be collisions with all TLD, right?
reply
0 sats \ 3 replies \ @ca98am79 OP 10 Nov
sorry I mean we used this syntax to make it less confusing with any conflicts with other naming systems
reply
0 sats \ 0 replies \ @andy 10 Nov
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
0 sats \ 1 reply \ @andy 10 Nov
can a space have a . in it's name?
reply
0 sats \ 0 replies \ @ca98am79 OP 10 Nov
no, it has the same rules as a traditional dns name
reply
0 sats \ 0 replies \ @buffrr 11 Nov freebie
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