blockstackd support – @jude is working on moving the subdomain processing out of blockstack_client and into blockstackd. This should allow mac/linux clients to query subdomain names (currently, the clients are default configured not to try and resolve subdomains, because it would require the clients to download all the zonefiles necessary to process subdomain ownership.
I have a question about the timing of this — @jude is also currently working on other changes (atlas-related) in this branch as well – my understanding is that the progress here is really good, and that it looks like the consensus hashes are converging, but Jude should chime in to let us now whether or not bundling these two features together and shipping them is doable next sprint (as it would need to be released before support can be turned on in clients) – I can also help out with this.
registrar deployment – the subdomain_registrar code we currently have is very much a prototype.
This could just beef up the python code that’s there now and make it easier to deploy in a container. Really, it only uses the blockstack_client to submit it’s updates (though it calls functions out of subdomains.py.
Ideally, I’d spin it out into another repo, and have it function somewhat independent of a local blockstack_client instance. This should be pretty doable, though, I’d guess it’d need to know how to generate its own transactions, so it could use my branch of blockstack.js
browser support –
this shouldn’t be too different from the code @larry already has in there, however, we would need dialogs to select whether you’re registering a domain name or a subdomain.
choosing which domain you are registering your subdomain on should be possible, but can probably be pushed to a later release.
I’m happy to work with you on the deployment side of the registrar @aaron. This is something we are going to want to make easy to deploy and operate for other users/orgs.