Skip to content

Commit 47e20b2

Browse files
content: remove Web3.Storage callout in pinning services how-to per @jnthnvctr
1 parent 1706182 commit 47e20b2

File tree

1 file changed

+0
-4
lines changed

1 file changed

+0
-4
lines changed

docs/how-to/work-with-pinning-services.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -8,10 +8,6 @@ description: Learn how to use or create remote pinning services with IPFS, the I
88

99
Depending on how you use IPFS, you might find it helpful to use a **remote pinning service** instead of, or in addition to, pinning files on your local IPFS node. Whether it happens remotely or locally, **pinning** an item in IPFS identifies it as something you always wish to keep available, exempting it from the routine _garbage collection_ that IPFS does on infrequently-used items in order to efficiently manage storage space. [Learn more about local pinning →](pin-files.md)
1010

11-
:::tip
12-
If you're looking for long-term storage, Web3.Storage combines the speed of a pinning service and the data resiliency of Filecoin. [Find out more at Web3.Storage →](https://web3.storage)
13-
:::
14-
1511
If you've got just one local IPFS node that's always running, local pinning may be all you need to ensure your important items are persisted and never garbage-collected. However, using a remote pinning service — or creating your own — might be useful to you if:
1612

1713
- Your local node isn't always online, but you need items to be consistently available.

0 commit comments

Comments
 (0)