Merge AstroDNS and is-a-dev

[tlochsta]

Hi! I'm the founder of AstroDNS. (click here for link) I think you should connect your domain is-a.dev because its easier to use the AstroDNS control panel then the GitHub pull requests. [your dns records must be hosted on cloudflare] What is AstroDNS? Welcome to AstroDNS, the go-to platform for easy and hassle-free subdomain creation. With AstroDNS, you can effortlessly obtain free subdomains and manage your DNS records to suit your needs. Register an account, personalize your subdomains, and enjoy our user-friendly interface. We provide comprehensive DNS management tools, high security, and reliable performance. Please note that AstroDNS offers free subdomains and does not support connecting your own domain. Experience the simplicity of AstroDNS today and unlock the full potential of your online presence.

[wdhdev]

Sorry, we cannot allow this due to a few reasons:

• Moving all the records over would be a massive hassle
• Using GitHub is easier as we can get more recognition and many people are already familiar with it
• We don't use Cloudflare, we use Namecheap DNS, due to Cloudflare's DNS record limit
• We don't want our users to have to create an account just to use is-a.dev, they should be able to use an account they already have (in this case, GitHub)
• Also, we have never heard of the service either and do not know its limitations and security risks

[tlochsta]

ok

[MaskDuck]

Adding to William's points, I'd say we could if your project was crafted with more care. I mean, it isn't up to the standard we are looking for. One maintainer tried to make a subdomain, and he failed to create a domain using your service. Also I'd like to note some points I didn't like, according to others:

• You have to create a SEPARATE account for this service. is-a.dev's aim is to make pretty subdomains accessible at the push of a button. GitHub enables us to do that, since most developers have a GH account.
• Cloudflare moving has been denied before (#1112)
• I feel like moving would be a breaking change for our users, as many has been using them and already familiar with GitHub (we have around 2k+ domains)
• Were we to move then how would our users access the moved domains? Do they have to register their domain again (if yes, this would lead to domain wrongfully claiming, e.g. I have been using maskduck.is-a.dev for long and someone could claim maskduck.is-a.dev faster than me)? Some users don't have emails, how would you create account for them if you decide to move the domains into your service? Also who would review the domains to ensure that the service isn't abused? Who would know that whether a page is "blank" or not, to prevent "cold domains" - domains that is claimed but never used?