Skip to content

Commit f1b829e

Browse files
2color2color
authored
Remove outdated content provider list and update peering documentation (#2119)
* edit and remove content provider list * fix links and refine introduction --------- Co-authored-by: Daniel N <2color@users.noreply.github.com>
1 parent 3daa048 commit f1b829e

File tree

1 file changed

+4
-85
lines changed

1 file changed

+4
-85
lines changed

‎docs/how-to/peering-with-content-providers.md‎

Lines changed: 4 additions & 85 deletions
Original file line numberDiff line numberDiff line change
@@ -5,11 +5,11 @@ description: Optimize retrieval speed by making direct connections to large cont
55

66
# Peering with content providers
77

8-
IPFS allows you to request data from any IPFS node with a copy using the data's [CID][cid-explainer] or content identifier. This process usually involves a lookup on the [distributed hash table][dht-explainer] and may also require establishing new connections to the nodes storing the content.
8+
IPFS allows you to fetch data from providers using [CIDs][cid-explainer]. This process usually involves a content routing lookup to find providers for the CID in the [DHT][dht-explainer] and IPNI.
99

1010
If you're running an IPFS node that serves many requests, such as a public HTTP gateway, you may be able to speed up queries by maintaining long-lived connections to nodes that provide many CIDs.
1111

12-
Prioritizing connections to certain peers is called **Peering**, and you can tell IPFS which peers to prioritize by editing the [`Peering` configuration][docs-peering-config] in your IPFS config file.
12+
Prioritizing connections to certain peers is called **Peering**, and you can tell IPFS which peers to prioritize by editing the [`Peering` configuration][docs-peering-config] in your [Kubo config file](https://github.com/ipfs/kubo/blob/master/docs/config.md).
1313

1414
To _peer_ with nodes from Cloudflare, for example, update your config to include a `Peering` section like this:
1515
```json
@@ -31,88 +31,7 @@ Generally speaking, users running IPFS at home won't need to set up peering and
3131
Peering is most helpful for nodes that have a lot of concurrent connections since it prevents the [connection manager][docs-connmgr] from dropping connections it thinks aren't "useful" any longer. If you find yourself running near the connection manager's limit, you may benefit from peering with content providers.
3232
:::
3333

34-
## Content provider list
35-
36-
Below is a community-maintained list of nodes that provide a lot of content to the IPFS network.
37-
38-
If you're running a public IPFS gateway, you may see improved performance for popular queries by adding these nodes to your [Peering configuration][docs-peering-config].
39-
40-
To add your platform to this list, please [open a PR to edit this page](https://github.com/ipfs/ipfs-docs/edit/main/docs/how-to/peering-with-content-providers.md) and add yourself to the list in alphabetical order.
41-
42-
:::warning
43-
This list is provided for informational purposes only. The IPFS Project does not endorse or guarantee any of the content providers listed here, nor does it have any control over their operations or services. Users should exercise their own discretion and conduct their own due diligence when selecting and interacting with content providers.
44-
:::
45-
46-
### Cloudflare
47-
48-
| Peer ID | Addresses |
49-
| ----------------------------------------------- | --------------------------------------------- |
50-
| `QmcFf2FH3CEgTNHeMRGhN7HNHU1EXAxoEk6EFuSyXCsvRE` | `/dnsaddr/node-1.ingress.cloudflare-ipfs.com` |
51-
| `QmcFmLd5ySfk2WZuJ1mfSWLDjdmHZq7rSAua4GoeSQfs1z` | `/dnsaddr/node-2.ingress.cloudflare-ipfs.com` |
52-
| `QmcfFmzSDVbwexQ9Au2pt5YEXHK5xajwgaU6PpkbLWerMa` | `/dnsaddr/node-3.ingress.cloudflare-ipfs.com` |
53-
| `QmcfJeB3Js1FG7T8YaZATEiaHqNKVdQfybYYkbT1knUswx` | `/dnsaddr/node-4.ingress.cloudflare-ipfs.com` |
54-
| `QmcfVvzK4tMdFmpJjEKDUoqRgP4W9FnmJoziYX5GXJJ8eZ` | `/dnsaddr/node-5.ingress.cloudflare-ipfs.com` |
55-
| `QmcfZD3VKrUxyP9BbyUnZDpbqDnT7cQ4WjPP8TRLXaoE7G` | `/dnsaddr/node-6.ingress.cloudflare-ipfs.com` |
56-
| `QmcfZP2LuW4jxviTeG8fi28qjnZScACb8PEgHAc17ZEri3` | `/dnsaddr/node-7.ingress.cloudflare-ipfs.com` |
57-
| `QmcfgsJsMtx6qJb74akCw1M24X1zFwgGo11h1cuhwQjtJP` | `/dnsaddr/node-8.ingress.cloudflare-ipfs.com` |
58-
| `Qmcfr2FC7pFzJbTSDfYaSy1J8Uuy8ccGLeLyqJCKJvTHMi` | `/dnsaddr/node-9.ingress.cloudflare-ipfs.com` |
59-
| `QmcfR3V5YAtHBzxVACWCzXTt26SyEkxdwhGJ6875A8BuWx` | `/dnsaddr/node-10.ingress.cloudflare-ipfs.com` |
60-
| `Qmcfuo1TM9uUiJp6dTbm915Rf1aTqm3a3dnmCdDQLHgvL5` | `/dnsaddr/node-11.ingress.cloudflare-ipfs.com` |
61-
| `QmcfV2sg9zaq7UUHVCGuSvT2M2rnLBAPsiE79vVyK3Cuev` | `/dnsaddr/node-12.ingress.cloudflare-ipfs.com` |
62-
63-
### European EPC Competence Center
64-
65-
| Peer ID | Addresses |
66-
| ------- | --------- |
67-
|`12D3KooWGaHbxpDWn4JVYud899Wcpa4iHPa3AMYydfxQDb3MhDME`|`/dns4/ipfs.ssi.eecc.de`|
68-
69-
### Filebase
70-
71-
| Peer ID | Addresses |
72-
| ------- | --------- |
73-
|`12D3KooWGtYkBAaqJMJEmywMxaCiNP7LCEFUAFiLEBASe232c2VH`|`/dns4/bitswap.filebase.io/tcp/443/wss`|
74-
75-
### Storj
76-
77-
| Peer ID | Addresses |
78-
| ------- | --------- |
79-
|`12D3KooWFFhc8fPYnQXdWBCowxSV21EFYin3rU27p3NVgSMjN41k`|`/ip4/5.161.92.43/tcp/4001`<br/>`/ip4/5.161.92.43/udp/4001/quic-v1`<br/>`/ip6/2a01:4ff:f0:3b1e::1/tcp/4001`<br/>`/ip6/2a01:4ff:f0:3b1e::1/udp/4001/quic-v1`|
80-
|`12D3KooWSW4hoHmDXmY5rW7nCi9XmGTy3foFt72u86jNP53LTNBJ`|`/ip4/5.161.55.227/tcp/4001`<br/>`/ip4/5.161.55.227/udp/4001/quic-v1`<br/>`/ip6/2a01:4ff:f0:1e5a::1/tcp/4001`<br/>`/ip6/2a01:4ff:f0:1e5a::1/udp/4001/quic-v1`|
81-
|`12D3KooWSDj6JM2JmoHwE9AUUwqAFUEg9ndd3pMA8aF2bkYckZfo`|`/ip4/5.161.92.36/tcp/4001`<br/>`/ip4/5.161.92.36/udp/4001/quic-v1`<br/>`/ip6/2a01:4ff:f0:3764::1/tcp/4001`<br/>`/ip6/2a01:4ff:f0:3764::1/udp/4001/quic-v1`|
82-
83-
### bit.site
84-
85-
| Peer ID | Addresses |
86-
| ------- | --------- |
87-
|`12D3KooWKNJDVqWKdGH5PJUpgG7JwSQnJCHSt2abfRMht2yjyV5x`|`/dnsaddr/node-1.ipfs.bit.site`|
88-
89-
### StorryTV
90-
91-
| Peer ID | Addresses |
92-
| ------- | --------- |
93-
|`bafzaajaiaejca3eporu7skzkukuie5nopngnubidqmnf57fl3qet7angukq234qj`|`/dnsaddr/peer.ipfs.storry.tv`|
94-
|`bafzaajaiaejcajedrki5t7qmgxzhwr24pfxb5cwrdf5d7rktguqurqztxsbffbvh`|`/dnsaddr/peer2.ipfs.storry.tv`|
95-
96-
### Web3.Storage
97-
98-
| Peer ID | Addresses |
99-
| ------- | --------- |
100-
|`bafzbeibhqavlasjc7dvbiopygwncnrtvjd2xmryk5laib7zyjor6kf3avm`|`/dns4/elastic.dag.house/tcp/443/wss`|
101-
102-
### 4EVERLAND
103-
104-
| Peer ID | Addresses |
105-
| ------- | --------- |
106-
|`12D3KooWQ85aSCFwFkByr5e3pUCQeuheVhobVxGSSs1DrRQHGv1t`|`/dnsaddr/node-1.ipfs.4everland.net`|
107-
108-
### 8api.sh
109-
110-
| Peer ID | Addresses |
111-
| ------- | --------- |
112-
|`12D3KooWGASC2jm3pmohEJXUhuStkxDitPgzvs4qMuFPaiD9x1BA`|`/ip4/78.46.108.24`|
113-
|`12D3KooWRbWZN3GvLf9CHmozq4vnTzDD4EEoiqtRJxg5FV6Gfjmm`|`/ip4/65.109.19.136`|
114-
11534
[dht-explainer]: ../concepts/how-ipfs-works.md#distributed-hash-tables-dhts
11635
[cid-explainer]: ../concepts/content-addressing.md
117-
[docs-peering-config]: ../how-to/configure-node.md
118-
[docs-connmgr]: ../how-to/configure-node.md
36+
[docs-peering-config]: https://github.com/ipfs/kubo/blob/master/docs/config.md#peering
37+
[docs-connmgr]: https://github.com/ipfs/kubo/blob/master/docs/config.md#swarmconnmgr

0 commit comments

Comments
 (0)