Skip to content
This repository has been archived by the owner on Jul 8, 2023. It is now read-only.

move away from the .io TLD #368

Open
davidmarkclements opened this issue Nov 24, 2019 · 14 comments
Open

move away from the .io TLD #368

davidmarkclements opened this issue Nov 24, 2019 · 14 comments

Comments

@davidmarkclements
Copy link

The UK is an aggressor in the Chagos Islands, it forcefully relocated residents in late 60's early 70's and is now ignoring a UN order return the islands to Mauritius - all the while it is profiting from the .io TLD.

Having talked it over with @mcollina he's asked me to open an issue proposing that we move away from the .io TLD , until/unless the Chagos Islands are restored.

http://www.thedarksideof.io/

https://www.bbc.com/news/uk-50511847

Same issue has been opened for Pino, pinojs/pino#746

@lmammino
Copy link
Member

Do we own any alternative domain already? Also we would still need to own and use the .io as a redirect for a while, IMHO...

Finally, I wonder how this might affect Search engine ranking...

@davidmarkclements
Copy link
Author

I believe Matteo has fastify.dev - totally agree on redirect, probably just wait for the io to expire (or renew if situation resolves). As for SEO I’d be willing to write an article about the move for both fastify and pino (which would hopefully be promoted by nf and the foundation even) to at least partially mitigate the temporary redirect situation

@mcollina
Copy link
Member

Currently fastify.dev is a redirect to fastify.io.

So I think we should:

  1. have fastify.dev return the full site
  2. flip the redirect from the .io domain to the .dev domain.

@lmammino can you check what I’d have to do to get this done?

@delvedor
Copy link
Member

We should update all the URLs also in our social accounts and blog posts.
Regarding the redirect, I fear we'll need to keep .io up and running for a while since we have always used it and now you can find it in many places out of our control.

@lmammino
Copy link
Member

@mcollina, I just had a look now.

Both domains are already available in our domain management and CDN system, so the switch should be just a matter of updating the conf for both domains and updating the build pipeline to use the API KEY of the new domain.

If we are all happy to proceed this way I can do the switch next week.

@mcollina
Copy link
Member

Are there any objections to move to the .dev domain?

@jsumners
Copy link
Member

Same response on Pino applies here pinojs/pino#746 (comment)

@delvedor
Copy link
Member

cc @fastify/fastify

@Ethan-Arrowood
Copy link
Member

I support moving to .dev and redirecting from .io

From my brief time working in web dev, I'm pretty certain that applying a domain management level redirect will have no impact on our SEO. As long as everything redirects correctly (as in we don't create dead links) we should be okay 😁

@lmammino
Copy link
Member

Did we reach an agreement here?

i was thinking about the following possible plan:

  • step 1: Remove the redirect from fastify.dev and publish all the content also on fastify.dev
  • step 2: Enable fastify.io to redirect to fastify.dev

This approach should allow us to do the transition with no downtime 🤞

What do you think?

@stale
Copy link

stale bot commented Dec 12, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@Eomm
Copy link
Member

Eomm commented Nov 28, 2020

Could we push forward this issue?

@mcollina
Copy link
Member

Yes, we should do it. @lmammino could you lead the way?

@Fdawgs Fdawgs transferred this issue from fastify/fastify Sep 2, 2022
@knicola
Copy link

knicola commented Jun 17, 2023

I'm not sure if this change is underway, but fastify.io seems to be down atm. fastify.dev is still online but not listed anywhere else other than this ticket as far as I can tell.

also, fastify.io expires 2023-08-16T11:41:44Z - I suggest not letting it go just yet. It's still the main fastify domain and someone can very well pick it up and use it with malicious intent.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants