fastify / website-metalsmith

This project is used to build the website for fastify web framework and publish it online.
https://www.fastify.io
MIT License
76 stars 133 forks source link

move away from the .io TLD #368

Open davidmarkclements opened 4 years ago

davidmarkclements commented 4 years ago

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, https://github.com/pinojs/pino/issues/746

lmammino commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

@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 commented 4 years ago

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

jsumners commented 4 years ago

Same response on Pino applies here https://github.com/pinojs/pino/issues/746#issuecomment-557934502

delvedor commented 4 years ago

cc @fastify/fastify

Ethan-Arrowood commented 4 years ago

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 commented 4 years ago

Did we reach an agreement here?

i was thinking about the following possible plan:

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

What do you think?

stale[bot] commented 4 years ago

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 commented 3 years ago

Could we push forward this issue?

mcollina commented 3 years ago

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

knicola commented 1 year ago

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.