Auto-generated parking page
planned
S
Scott
Automatically generate a "parking page" for domains bought on namebase. This may instantly increase the value of names a little bit. If you really want to get technical with it, auto-generate a parking page on namebase.io also for each domain with instructions for how to access the domain without the namebase.io url.
Johnny Wu
Merged in a post:
An "hello" webpage pre-configured for max 10 TLDs of yours
ben.oxmo
The idea is to have a fixed number of webpage (my suggestion would be 10) that are associated with their respective TLDs. This will be done then by default with one of the service provider that currently supports the handshake protocol.
Namers would only have to tick, up to 10 TLDs, to get their landing page setup without doing anthing
Johnny Wu
planned
Johnny Wu
Merged in a post:
Standard parking information
Fernando Falci
Hey namebase! I would like to propose a standard about parking domains:
We could agree and define a format for a key=value TXT, and promote it for all domains available for selling (namebase or not)
The way I imagined:
TXT parking-value=10000 HNS (the coin could be optional)
But it would require a contact option. Namebase handle it, but since the TXT it could be found by dig'ing the domain, so...
TXT parking=http://namebase.io/domains/example
Why it would be interesting for namebase?
Imagine there's a domain I'm interested in (eg: nb). How could I know if it is available for selling and the owner's contact?
You could park (ns) the domain, but..
By having a common/standard way of publishing this data, we could have other sites listing all domains, including namebase's. This is the http://parking.sinpapeles/
I believe it could be good for the HNS as an ecosystem
WDYT?
Fernando Falci
I'm working on a side project for this.
You can set the NS to parking.sinpapeles.
More info: http://parking.sinpapeles/
Johnny Wu
under review
Tieshun Roquerre
I've personally wanted to do this for a long time! This feature makes a ton of sense and we'll definitely get to it eventually (after current performance and stability priorities)