chore: remove mentions of decommissioned Cloudflare hosts (#1886)

* chore: remove mentions of sunset Cloudflare hosts this removes mentions of `https://cf-ipfs.com` or `https://cloudflare-ipfs.com` and ensures content makes sense after August 14th, 2024 Context: https://blog.cloudflare.com/cloudflares-public-ipfs-gateways-and-supporting-interplanetary-shipyard * fix: 2019 camp website link * fix: broken ecosystem link * fix: 403 on iotop and iostat links * fix: broken relative link * fix: various ci lint * fix: delegated routing links * fix: reviewdog errors * fix: example url with path Co-authored-by: Adin Schmahmann <[email protected]> * fix: switch iostat to github url --------- Co-authored-by: Adin Schmahmann <[email protected]>
ipfs · Jul 2, 2024 · 5081425 · 5081425
1 parent 25c5a82
commit 5081425
Show file tree

Hide file tree

Showing 7 changed files with 30 additions and 13 deletions.
diff --git a/.github/styles/pln-ignore.txt b/.github/styles/pln-ignore.txt
@@ -37,6 +37,7 @@ CNAME
 CNAMEs
 codec
 Coinlist
+Combinator
 Composable
 composable
 config
@@ -59,6 +60,7 @@ dClimate
 deduplicate
 Denylist
 deserialization
+deserialized
 Dheeraj
 DHT
 DHTs
@@ -67,7 +69,9 @@ discoverability
 DNS
 DNSAddr
 DNSLink
+DNSLinks
 dnslink
+dnslinks
 dotgraph
 DWeb
 dweb
@@ -78,6 +82,7 @@ ethereum
 explainers
 Fabien
 failover
+Fastly
 Filebase
 Filecoin
 filecoin
@@ -89,6 +94,8 @@ FQDN
 FQDNs
 gasless
 geospatial
+Git
+Git's
 GitHub
 Gnutella
 goroutine
@@ -102,11 +109,14 @@ Hareesh
 Helia
 homebrew
 hostname
+hostnames
 HTML
 HTTPS
 identafiability
 Infura
 interop
+iotop
+iostat
 IPFS
 IPFS's
 ipget
@@ -151,17 +161,21 @@ metadata's
 Metamask
 Minty
 Minty's
+Mojitos
 multiaddr
+Multiaddrs
 Multiaddress
 multiaddresses
 Multibase
 multibase
 Multicodec
 multicodec
+Multicodecs
 Multiformat
 Multiformats
 multiformat
 Multihash
+Multihashes
 multihash
 multipage
 Nagaraj
@@ -209,15 +223,19 @@ Rabin
 rasterio
 README
 READMEs
+reachability
 referenceable
+Repo
 reprovider
 reproviding
+retrievability
 roadmaps
 sandboxed
 Satoshi
 serverless
 sharding
 snapshotted
+Speedtest
 stackparse
 stdout
 someguy

diff --git a/docs/concepts/glossary.md b/docs/concepts/glossary.md
@@ -166,7 +166,7 @@ Direct Connection Upgrade through Relay (DCUtR) protocol enables [hole punching]
 
 ### Delegated routing
 
-Delegated routing is a mechanism by which IPFS implementations can offload content routing, peer routing, and naming (IPNS) to another process/server. The most widely adopted vendor-agnostic spec for delegated routing is the [Delegated Routing V1 HTTP API](https://specs.ipfs.tech/routing/http-routing-v1/).
+Delegated routing is a mechanism by which IPFS implementations can offload content routing, peer routing, and naming (IPNS) to another process/server. The most widely adopted vendor-agnostic spec for delegated routing is the [Delegated Routing V1 HTTP API](https://specs.ipfs.tech/routing/http-routing-v1/) with [public utility instance at `delegated-ipfs.dev/routing/v1`](../concepts/public-utilities.md#delegated-routing).
 
 Delegated routing is useful in browsers and other constrained environments where it's infeasible to be a DHT client/server. More broadly, it enables experimentation and innovation in content routing while maintaining interoperability and modularity.
 

diff --git a/docs/concepts/public-utilities.md b/docs/concepts/public-utilities.md
@@ -8,7 +8,7 @@ description: Information about hosted public utilities such as public gateways a
 
 The IPFS Foundation (and Protocol Labs in the past) and several other organizations provide hosted public utilities to the community on a best-effort basis. As such, it is not intended to be part of your critical path or production infrastructure.
 
-These include [IPFS Gateways](./ipfs-gateway.md), hosted [Delegated Routing V1 endpoints](./nodes#delegated-routing), and the [Amino DHT](./glossary.md#amino) [Bootstrappers](./nodes.md#bootstrap).
+These include [IPFS Gateways](./ipfs-gateway.md), hosted [Delegated Routing V1 endpoints](./glossary.md#delegated-routing), and the [Amino DHT](./glossary.md#amino) [Bootstrappers](./nodes.md#bootstrap).
 
 These utilities make it easier to retrieve data from the IPFS network in resource-constrained environments such as browsers and low-powered devices.
 
@@ -36,13 +36,13 @@ Your browser may have a local cache of the content in question and might not ref
 
 ## Other Public Gateways
 
-Additionally, there's a community-maintained [tool for finding and testing public gateways](https://ipfs.github.io/public-gateway-checker/) such as the one operated by Cloudflare: `https://cf-ipfs.com`.
+Additionally, there's a community-maintained [tool for finding and testing public gateways](https://ipfs.github.io/public-gateway-checker/).
 
 ## Delegated Routing
 
 While IPFS Gateways are immensely helpful in doing all the heavy lifting of finding providers for CIDs and retrieving them, they can be a choke point for retrieval and a point of centralization.
 
-[_Delegated Routing_](./nodes.md#delegated-routing) endpoints are a key step towards eliminating the emergent centralization of public gateways thereby increasing the health of the network.
+[_Delegated Routing_](./glossary.md#delegated-routing) endpoints are a key step towards eliminating the emergent centralization of public gateways thereby increasing the health of the network.
 
 Browsers and low-powered devices can make a single HTTP call to a _Delegated Routing_ endpoint with the CID they are looking to retrieve. The endpoint returns the [multiaddresses](./glossary.md#multiaddr) of the providers for the CID, from which the browser can download directly.
 

diff --git a/docs/how-to/address-ipfs-on-web.md b/docs/how-to/address-ipfs-on-web.md
@@ -135,8 +135,7 @@ Examples:
 
 ```plaintext
 https://bafybeiemxf5abjwjbikoz4mc3a3dla6ual3jsgpdr4cjr3oz3evfyavhwq.ipfs.dweb.link/wiki/
-https://bafybeiemxf5abjwjbikoz4mc3a3dla6ual3jsgpdr4cjr3oz3evfyavhwq.ipfs.cf-ipfs.com/wiki/Vincent_van_Gogh.html
-https://bafybeiemxf5abjwjbikoz4mc3a3dla6ual3jsgpdr4cjr3oz3evfyavhwq.ipfs.localhost:8080/wiki/
+http://bafybeiemxf5abjwjbikoz4mc3a3dla6ual3jsgpdr4cjr3oz3evfyavhwq.ipfs.localhost:8080/wiki/Vincent_van_Gogh.html
 ```
 
 #### Native support in Kubo

diff --git a/docs/how-to/gateway-best-practices.md b/docs/how-to/gateway-best-practices.md
@@ -35,7 +35,7 @@ If you are running an IPFS node that is also configured as an IPFS gateway, each
 - Put a CDN like Cloudflare in front of the IPFS gateway.
 - Consider enabling the [Accelerated DHT Client](https://github.com/ipfs/go-ipfs/blob/master/docs/experimental-features.md#accelerated-dht-client). 
 - Test and monitor your internet connection speed, with a tool like [Speedtest CLI](https://www.speedtest.net/apps/cli).
-- Monitor disk I/O and make sure that no other processes are causing disk I/O bottlenecks with a tool like [iotop](https://linux.die.net/man/1/iotop) or [iostat](https://linux.die.net/man/1/iostat).
+- Monitor disk I/O and make sure that no other processes are causing disk I/O bottlenecks with a tool like [iotop](https://github.com/Tomas-M/iotop) or [iostat](https://github.com/sysstat/sysstat).
 
 
 
@@ -89,7 +89,7 @@ A compromised writeable gateway may inject falsified content into the IPFS netwo
 1. Alice gives the falsified content CID to Bob.
 1. Bob fetches the content with this CID and cryptographically validates the balance of `0.00`.
 
-To partially address this exposure, you may wish to use the public gateway [cf-ipfs.com](https://cf-ipfs.com) as an independent, trusted reference with both same-origin policy and CORS support.
+To address this exposure, public gateways should only be limited to [trustless and verifiable response types](https://docs.ipfs.tech/reference/http/gateway/#trustless-verifiable-retrieval).
 
 ## Assumed filenames when downloading files
 

diff --git a/docs/project/history.md b/docs/project/history.md
@@ -46,7 +46,7 @@ Protocol Labs entered the [Y Combinator Summer 2014 Class](https://www.ycombinat
 
 The whitepaper was published in July 2014. It caught the attention of P2P and internet enthusiasts, including Jeromy Johnson (aka [whyrusleeping](https://github.com/whyrusleeping)). "Why" and other early contributors shared Juan's vision for a distributed, uncensorable, and permissionless file system. They worked nights and weekends, and initially for free, because they believed in the positive impact that open networks like IPFS could have on the world.
 
-Juan, Why, and other contributors spent many late nights in Juan's living room with takeout food and too many coffees ([Philz Mint Mojitos](https://www.philzcoffee.com/menu) FTW!) to create the alpha release of [Kubo](https://github.com/ipfs/kubo/blob/master/CHANGELOG.md#023---2015-03-01). IPFS was ready to begin its growth journey in the open.
+Juan, Why, and other contributors spent many late nights in Juan's living room with takeout food and too many coffees ([Philz Mint Mojitos](https://web.archive.org/web/20230520184851/https://philzcoffee.com/menu/coffee) FTW!) to create the alpha release of [Kubo](https://github.com/ipfs/kubo/blob/master/CHANGELOG.md#023---2015-03-01). IPFS was ready to begin its growth journey in the open.
 
 In the summer of 2015, the small but growing IPFS team (about five or six full-time contributors) settled into a coworking space in Seattle. They hammered out improvements to the Go and JavaScript implementations of IPFS as interest in the project grew. Satoshi Nakamoto's 2009 [Bitcoin whitepaper](https://bitcoin.org/bitcoin.pdf) had ushered in a renaissance of P2P innovation. A P2P summer was in full swing. IPFS gained usage in the [Ethereum](https://ethereum.org/) and wider blockchain communities. In September 2015, [Neocities](https://neocities.org/) became the first major site to [implement IPFS in production](https://blog.neocities.org/blog/2015/09/08/its-time-for-the-distributed-web.html).
 
@@ -60,10 +60,10 @@ Two watershed moments in 2017 validated the growing excitement around IPFS. The
 
 According to [Uncle Ben](https://en.wikipedia.org/wiki/Uncle_Ben#%22With_great_power_comes_great_responsibility%22), with great power comes great responsibility. So in 2018, IPFS entered the next phase of its maturation. The project needed to deliver on its ideological and technical advantages at scale. As seen in previous P2P eras, theoretical advantages must translate to tangible developer and user benefits in order to win over the mass market. With a growing team, multiple interdependent projects, and an ecosystem of users and partners, the team began developing, sharing, and executing product roadmaps to maturity.
 
-This focus bore significant results in the IPFS community in 2019. Protocol Labs hosted the [first IPFS Camp](https://camp.ipfs.io/) in Barcelona in June. The retreat brought together 150 distributed-web pioneers to learn, collaborate, and build. It inspired a [successful collaboration](https://blog.ipfs.tech/2020-02-14-improved-bitswap-for-container-distribution/) with one of the biggest, most innovative corporations in world, Netflix. By the end of 2019, the IPFS network had grown by more than 30x. The community of open-source contributors stood at more than 4,000.
+This focus bore significant results in the IPFS community in 2019. Protocol Labs hosted the [first IPFS Camp](https://2019.ipfs.camp) in Barcelona in June. The retreat brought together 150 distributed-web pioneers to learn, collaborate, and build. It inspired a [successful collaboration](https://blog.ipfs.tech/2020-02-14-improved-bitswap-for-container-distribution/) with one of the biggest, most innovative corporations in world, Netflix. By the end of 2019, the IPFS network had grown by more than 30x. The community of open-source contributors stood at more than 4,000.
 
-The April 2020 [Kubo 0.5.0 release](https://github.com/ipfs/kubo/blob/master/docs/changelogs/v0.5.md) provided the largest performance upgrades to the network yet: faster file adding (2x), providing (2.5x), finding (2-6x), and fetching (2-5x). For the ever-growing [IPFS ecosystem](https://ipfs.io/images/ipfs-applications-diagram.png), reliability is just as important as speed. For that, Protocol Labs developed, used, and released [Testground](https://blog.ipfs.tech/2020-05-06-launching-testground/). Testground is a huge step forward in testing and hardening P2P systems not just for IPFS, but the community at-large.
+The April 2020 [Kubo 0.5.0 release](https://github.com/ipfs/kubo/blob/master/docs/changelogs/v0.5.md) provided the largest performance upgrades to the network yet: faster file adding (2x), providing (2.5x), finding (2-6x), and fetching (2-5x). For the ever-growing [IPFS ecosystem](https://ecosystem.ipfs.tech/), reliability is just as important as speed. For that, Protocol Labs developed, used, and released [Testground](https://blog.ipfs.tech/2020-05-06-launching-testground/). Testground is a huge step forward in testing and hardening P2P systems not just for IPFS, but the community at-large.
 
-Major collaborations with [Opera](https://blog.ipfs.tech/2020-03-30-ipfs-in-opera-for-android/), [Microsoft ION](https://techcommunity.microsoft.com/t5/azure-active-directory-identity/toward-scalable-decentralized-identifier-systems/ba-p/560168), and [Cloudflare](https://www.cloudflare.com/distributed-web-gateway/) just scratch the surface of possibilities for IPFS. The H2 2020 Filecoin Mainnet launch is poised to fundamentally shift economic incentives of the P2P IPFS network to compete with the entrenched client-server web.
+Major collaborations with [Opera](https://blog.ipfs.tech/2020-03-30-ipfs-in-opera-for-android/), [Microsoft ION](https://techcommunity.microsoft.com/t5/azure-active-directory-identity/toward-scalable-decentralized-identifier-systems/ba-p/560168), and [Cloudflare](https://blog.cloudflare.com/distributed-web-gateway) just scratch the surface of possibilities for IPFS. The H2 2020 Filecoin Mainnet launch is poised to fundamentally shift economic incentives of the P2P IPFS network to compete with the entrenched client-server web.
 
 IPFS has come a long way in the journey to building a faster, safer, and more open web to preserve and grow humanity's knowledge. The beautiful thing is, that journey is never ending. This is still just the beginning!
diff --git a/docs/quickstart/retrieve.md b/docs/quickstart/retrieve.md
@@ -79,7 +79,7 @@ Congratulations, you have successfully fetched the CID.
 To fetch the CID using an IPFS gateway is as simple as loading one of the following URLs:
 
 - [https://ipfs.io/ipfs/bafybeicn7i3soqdgr7dwnrwytgq4zxy7a5jpkizrvhm5mv6bgjd32wm3q4](https://ipfs.io/ipfs/bafybeicn7i3soqdgr7dwnrwytgq4zxy7a5jpkizrvhm5mv6bgjd32wm3q4)
-- [https://cloudflare-ipfs.com/ipfs/bafybeicn7i3soqdgr7dwnrwytgq4zxy7a5jpkizrvhm5mv6bgjd32wm3q4](https://cloudflare-ipfs.com/ipfs/bafybeicn7i3soqdgr7dwnrwytgq4zxy7a5jpkizrvhm5mv6bgjd32wm3q4)
+- [https://dweb.link/ipfs/bafybeicn7i3soqdgr7dwnrwytgq4zxy7a5jpkizrvhm5mv6bgjd32wm3q4](https://dweb.link/ipfs/bafybeicn7i3soqdgr7dwnrwytgq4zxy7a5jpkizrvhm5mv6bgjd32wm3q4)
 - [https://gateway.pinata.cloud/ipfs/bafybeicn7i3soqdgr7dwnrwytgq4zxy7a5jpkizrvhm5mv6bgjd32wm3q4](https://gateway.pinata.cloud/ipfs/bafybeicn7i3soqdgr7dwnrwytgq4zxy7a5jpkizrvhm5mv6bgjd32wm3q4)
 
 ## Summary and next steps