3 ms·

One possible reason for the failed HN launch is the landing pages makes the basic mistake of listing features rather than benefits or use cases. It is a descri

One possible reason for the failed HN launch is the landing pages makes the basic mistake of listing features rather than benefits or use cases. It is a description of what the code does, rather than why it was written. I am still lost to the benefits of managing DNS with github. I can't see the documentation, and the free trial button leads to the scariest signup page in history. It wants read/write access to my private repos.

johnward 13y ago
I agree with this. What is my problem and how are you solving it? OP has to connect to the pain that I assume they are removing with the product.
nl 13y ago
the free trial button leads to the scariest signup page in history To be specific, this goes to the OAuth page for GitHub. That's NOT a good experience. You need a page before it explaining what is going to happen. The same thing happens with the link on the blog post. It says "check us out....", I clicked and ended up with an OAuth page. Once I finally got to your site (manually typing in the URL..) I thought it looked interesting. GeoIP? Weighted records? Round Robin Load Balancing? Ok.. I'm interested - I've build CDNs before, and I'd like to understand how your GeoIP is implemented... hmm, no docs, but "Our quickstart tutorial will have you up and running in no time". Ok, I can read a tutorial. Umm.. where?
sdesol 13y ago
The only thing that I got out of it was, if you are using GitHub, why not use it to manage your DNS. This type of service would be interesting to me since I do need to create a lot of short term sub domains but I wasn't sold. This is my current workflow: - User requests a free trial for my product - I spin up a private VPS for them. - I create a temp subdomain so the user can access the newly created VPS. I use Amazon Route 53 and their command line tool dnscurl.pl to create a new DNS record set. - I keep an eye on the VPS and after an hour, I'll destroy the VPS and remove the temp subdomain with Amazon's dnscurl.pl All of this is automated and adding/removing DNS records takes seconds and I pay about a buck a month. The only thing that I find annoying about working with Amazon S5 is you have to use XML files and they do not support IPV6. I would rather use JSON to manage my domains but I'm not sure it's $50/month nice. I also have concerns about introducing a layer in front my DNS management. GitHub is not available from time to time and I'd hate to have this be another thing to worry about. Maybe I'm not the type of customer you (Namecast) are looking for, but I can see how this would benefit novices. From their point of view, they'll just have to know how to edit a file and do a git push to GitHub.

johnward 13y ago

I agree with this. What is my problem and how are you solving it? OP has to connect to the pain that I assume they are removing with the product.

nl 13y ago

the free trial button leads to the scariest signup page in history To be specific, this goes to the OAuth page for GitHub. That's NOT a good experience. You need a page before it explaining what is going to happen. The same thing happens with the link on the blog post. It says "check us out....", I clicked and ended up with an OAuth page. Once I finally got to your site (manually typing in the URL..) I thought it looked interesting. GeoIP? Weighted records? Round Robin Load Balancing? Ok.. I'm interested - I've build CDNs before, and I'd like to understand how your GeoIP is implemented... hmm, no docs, but "Our quickstart tutorial will have you up and running in no time". Ok, I can read a tutorial. Umm.. where?

sdesol 13y ago

The only thing that I got out of it was, if you are using GitHub, why not use it to manage your DNS. This type of service would be interesting to me since I do need to create a lot of short term sub domains but I wasn't sold. This is my current workflow: - User requests a free trial for my product - I spin up a private VPS for them. - I create a temp subdomain so the user can access the newly created VPS. I use Amazon Route 53 and their command line tool dnscurl.pl to create a new DNS record set. - I keep an eye on the VPS and after an hour, I'll destroy the VPS and remove the temp subdomain with Amazon's dnscurl.pl All of this is automated and adding/removing DNS records takes seconds and I pay about a buck a month. The only thing that I find annoying about working with Amazon S5 is you have to use XML files and they do not support IPV6. I would rather use JSON to manage my domains but I'm not sure it's $50/month nice. I also have concerns about introducing a layer in front my DNS management. GitHub is not available from time to time and I'd hate to have this be another thing to worry about. Maybe I'm not the type of customer you (Namecast) are looking for, but I can see how this would benefit novices. From their point of view, they'll just have to know how to edit a file and do a git push to GitHub.