enable eth subdomains

[lyricalpolymath]

Hi Ric

the search box only supports top level .eth domains (example.eth)
and doesn't support subdomains ( ipfscontent.example.eth)

I think this is where the regex should be changed

if (value.match(/^[a-z0-9-]*\.eth$/i)) {

right?

[ricmoo]

The problem is more with how DNS works with SSL and how it resolves names. For example, I cannot get a "..meeseks.app" SSL certificate with my current provider.

I am working on another solution to having to own a .eth TLD, and I am working with another group to enable full sub-domain support, which will likely require running a custom domain name server and I still need to research a multi-tier SSL certificate provider.

If those weren’t a problem, you are absolutely correct though, that regex could just let the name through, ENS would resolve it just fine and IPFS would be able to serve the content. The legacy part of the web is the only problem. :(

[lyricalpolymath]

wow, more complicated than I thought :)
I thought it was a content resolver (figuring out from ENS if a domain has content and simply opening it... similar to portal network.
there's clearly more going on.

couldn't it work without SSL? just less secure
thanks anyways

[ricmoo]

There are still DNS issues, but yes, it could much more easily (and cheaply) work without SSL, but that is a pretty big compromise. :)

I've never heard of portal network, but just checked them out; they have the same issues. :(

It is something I'm working on. ;)