Protocol://Domain.Subdomain/Path

[TylerAbeoJordan]

I was WRONG: (see @neo’s post below correcting me) → In the regular web clearnet subdomains have nothing to do with DNS, they are dealt with locally by a web server.

I’m not sure how it will all work on Safe. For instance will there be a tld? e.g. .com, .org, etc.

if there are tlds … would that come first in your idea @Sascha? e.g. safe://com.google/sheets/ouertp235-9a8/
or
safe://com/google/sheets/ouertp235-9a8/

Is the ‘.’ more authoritative!

I suppose if you were offering some sort of web service though then maybe it’s helpful to delineate between things.

@TylerAbeoJordan

I like this idea of having a browser plugin manage domains … so maidsafe might only need to reserve .web, .web2 … etc tld’s … then a particular plugin with a particular system of domain management would be able to handle the rest e.g.: safe://google.com.web … where each plugin would handle only a single tld.

In this manner we can have any number of domain systems catering to whatever people like.

One plugin might have a 30 year contract with option to renew … another might be pay as you go, another might be in perpetuity … another might auction it off to highest bidder at the end of a period of time … whatever you want, you can have it as a system … just build yourself a plugin and buy a tld from maidsafe.

If we had something like that - separate browser plugins each act as a DNS system for individual (or groups of) TLD’s … then I guess you could have a plugin that does subdomains the way you like them … you could even copy an existing plugin for an existing tld group and swap around how it processes subdomains so you get it they way you want it personally.

@dirvine what are the current plans regarding safe dns? Will there be an RFC on this or is it already worked out? I did a search on this forum but didn’t find anything very new (less than two years old).