Why not asyncapi.org about spec HOT 12 CLOSED

I already started promoting the .org in some tweets. I think for now we'll do both.

from spec.

Hey Andrés! That's not a dumb question at all. We also registered asyncapi.org for the same reason you explain. Why we chose .com? To be fair we didn't even thought about it. It was natural for us to think about the .com as the default one because it's what more people are used to 😊

Thanks!

from spec.

Thanks @fmvilas :)

from spec.

I noticed https://www.asyncapi.org is not redirecting to .com. it works without www

from spec.

Oh! great catch @andresgutgon. We'll fix it. Thanks!

from spec.

It's working now. Thanks for reporting @andresgutgon.

from spec.

💪

from spec.

I'm closing the issue now but don't hesitate to continue discussion or open a new issue if you see something else :)

from spec.

Well original question was why you don't promote .org domain. For me feels more Open than a .com :)

from spec.

Adding my thoughts here: usually .org TLD subdomains are associated with non-commercial organizations. We ended up choosing the .com TLD for the sake of transparency—we are a commercial company.

Thanks for sharing your thoughts and helping us improve!

from spec.

I know. But Facebook started http://ogp.me/ Open Graph Protocol. The protocol is Open but Facebook is not.

Imo the company and the protocol can be different things.

I could implement asyncapi without been a Hitch customer, right?

Btw I love you're thinking about transparency 👏

from spec.

@andresgutgon Thanks!

Yes, you're totally correct, anyone can use the Async API specification without being a Hitch customer.

In any case, both domains work and we'll be promoting https://www.asyncapi.org more.

from spec.