Skip to content

feat: move to ipfs.tech#133

Merged
lidel merged 4 commits intomainfrom
feat/move-to-ipfs.network-domain
Jul 27, 2022
Merged

feat: move to ipfs.tech#133
lidel merged 4 commits intomainfrom
feat/move-to-ipfs.network-domain

Conversation

@lidel
Copy link
Copy Markdown
Member

@lidel lidel commented May 20, 2022 •
edited
Loading

This PR changes the canonical address of IPFS project's website from ipfs.io to ipfs.tech

Context: https://github.com/protocol/bifrost-infra/issues/178#issuecomment-1195867284

TODO

  • new DNSLink and Fleek CDN for ipfs.network domain (smoke-test before we got final one)
  • new DNSLink and Fleek CDN for ipfs.tech domain
  • keep publishing to old domain and DNSLink as well
  • add JS that does redirect to new domain client-side, including gateways
  • emails – descoped tracked in refactor: switch emails to @ipfs.tech #142

@lidel lidel force-pushed the feat/move-to-ipfs.network-domain branch from cc7e9a4 to 003201c Compare May 21, 2022 21:08
@lidel lidel force-pushed the feat/move-to-ipfs.network-domain branch from 003201c to d92f65d Compare May 21, 2022 21:26
johnnymatthews
johnnymatthews approved these changes May 23, 2022
View reviewed changes
Copy link
Copy Markdown
Contributor

@johnnymatthews johnnymatthews left a comment •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice! Merge when ready.

@thattommyhall
Copy link
Copy Markdown
Member

thattommyhall commented May 23, 2022

Came to complain about doing the redirect in JS, but stayed to congratulate @lidel on doing it so tastefully
(I was going to say folks should not get redirected if they use a a gateway, but this is delightful)

andyschwab
andyschwab reviewed May 23, 2022
View reviewed changes
Comment thread content/legal.md Outdated

### Where do you email/send the DMCA Notice?
The quickest way is to email it to abuse@ipfs.io. If you prefer, you can instead send it to:
The quickest way is to email it to **abuse@ipfs.network**. If you prefer, you can instead send it to:
Copy link
Copy Markdown
Member

@andyschwab andyschwab May 23, 2022 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@lidel, note that this is NOT functional yet - abuse@ is considered a reserved name, and I couldn't set it up as an alias. I did setup abuse-reports@ipfs.network that will forward to abuse@ipfs.io for now. Once we change the primary domain in Google Workspace, this will not be an issue.

Copy link
Copy Markdown
Member Author

@lidel lidel Jul 26, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've extracted email migration to separate PR: #142

@lidel lidel added the status/blocked Unable to be worked further until needs are met label Jul 18, 2022
@lidel lidel mentioned this pull request Jul 18, 2022
Closed
1 task
@lidel lidel changed the title feat: move to ipfs.network feat: move to ipfs.tech Jul 26, 2022
@lidel
Copy link
Copy Markdown
Member Author

lidel commented Jul 26, 2022 •
edited
Loading

Updated this PR to use ipfs.tech (https://github.com/protocol/bifrost-infra/issues/178#issuecomment-1195867284)
Merging is blocked until we have DNS (Fleek) is set up – email stays in @ipfs.io for now, will update in separate PR: #142

@lidel lidel force-pushed the feat/move-to-ipfs.network-domain branch from 1357488 to 22a1601 Compare July 26, 2022 20:20
@lidel
feat: move to ipfs.tech
be906bc 
protocol/bifrost-infra#178 (comment)

Email still @ipfs.io -- will update in separate PR.
@lidel lidel force-pushed the feat/move-to-ipfs.network-domain branch from 22a1601 to be906bc Compare July 26, 2022 20:22
lidel added a commit that referenced this pull request Jul 26, 2022
@lidel
refactor: switch emails to @ipfs.tech
6f7fb2a 
This is a follow-up to #133
@lidel lidel mentioned this pull request Jul 26, 2022
Merged
1 task
@lidel lidel removed the status/blocked Unable to be worked further until needs are met label Jul 26, 2022
@lidel
Copy link
Copy Markdown
Member Author

lidel commented Jul 26, 2022

This is unblocked and https://ipfs.tech should already work.
I will wait until tomorrow (just to give DNS more time to propagate) and then merge.

lidel
lidel commented Jul 26, 2022
View reviewed changes
Comment thread nuxt.config.js
'@nuxtjs/speedcurve',
'~/modules/nuxt-module-ipfs',
['nuxt-canonical', { baseUrl: 'https://ipfs.io' }],
['nuxt-canonical', { baseUrl: 'https://ipfs.tech' }],
Copy link
Copy Markdown
Member Author

@lidel lidel Jul 26, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ℹ️ this takes care of canonical link and SEO migration

@lidel lidel self-assigned this Jul 26, 2022
@lidel
refactor: smart redirect ipfs.io → ipfs.tech
5d77c4a 
Switching to location.replace() because is ensures replaced .io URLs
will not be saved in browser history
@lidel lidel force-pushed the feat/move-to-ipfs.network-domain branch from ba6caa2 to 5d77c4a Compare July 27, 2022 00:15
@lidel lidel merged commit cda6747 into main Jul 27, 2022
@lidel lidel deleted the feat/move-to-ipfs.network-domain branch July 27, 2022 11:50
@lidel lidel mentioned this pull request Jul 29, 2022
Merged
lidel added a commit that referenced this pull request May 9, 2023
@lidel
refactor: switch emails to @ipfs.tech (#142)
c38305f 
* refactor: switch emails to @ipfs.tech

This is a follow-up to #133
Part of protocol/bifrost-infra#2018
nova-forge5t6y added a commit to nova-forge5t6y/ipfs-website that referenced this pull request Sep 29, 2025
@nova-forge5t6y
refactor: switch emails to @ipfs.tech (#142)
36952e1 
* refactor: switch emails to @ipfs.tech

This is a follow-up to ipfs/ipfs-website#133
Part of https://github.com/protocol/bifrost-infra/issues/2018
node-seeker574 added a commit to node-seeker574/ipfs-website that referenced this pull request Dec 11, 2025
@node-seeker574
refactor: switch emails to @ipfs.tech (#142)
d5aa7ee 
* refactor: switch emails to @ipfs.tech

This is a follow-up to ipfs/ipfs-website#133
Part of https://github.com/protocol/bifrost-infra/issues/2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@andyschwab andyschwab andyschwab left review comments

+1 more reviewer

@johnnymatthews johnnymatthews johnnymatthews approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

@lidel lidel

Labels

None yet

Projects

No open projects
IPFS Shipyard Team
Archived in project

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@lidel @thattommyhall @johnnymatthews @andyschwab