Support for custom domains

[akoenig]

First of all @taravancil and @pfrazee: Thanks for initiating the whole ecosystem around Beaker. It is amazing and very very inspiring.

I tinkered with a local installation of hashbase and was just wondering if you plan to support custom domains / aliases at some point in the future :) Let's say I want to spin up an own hashbase node and want to establish something in the vein of: andre-blog.hashbase.io should also be reachable via blog.my-host.tld. I could imagine that this would be a pretty common use-case which, unfortunately, brings a lot of ceremony to the table, like: The user has to specify the domain upfront, so that the issuing of the SSL certificate still works, etc.

What do you think about this? Is this something worth achieving?

[pfrazee]

Hi @akoenig! We'd very much like to have this feature. But yes, there's a lot of ceremony, and we have to figure out the security challenges. We're focused on the next release of Beaker right now, so this feature is on the back burner. Once we're back on hashbase FT, it's a top addition for us.

[akoenig]

Hi @pfrazee. Awesome, thanks for the note. Can't say how much I'm looking forward to the next release. Very excited! :)

[millette]

I was reading https://ldpreload.com/blog/names-to-reserve and this cought my attention, regarding cookies:

So, if you are letting users register hostnames in your domain, you should get it listed as a public suffix, which requires just sending a pull request or an email. It takes some time for the update to reach browsers (the list is compiled into browsers, so it's only updated by a browser version update), so you should try to do this as far in advance as possible before launching.

Probably a good idea then to register hashbase.io at https://publicsuffix.org/submit/

See also sandstorm-io/sandcats#43