diff --git a/.github/styles/Vocab/ipfs-docs-vocab/accept.txt b/.github/styles/Vocab/ipfs-docs-vocab/accept.txt index fedb954c0..d2a3fe5d1 100644 --- a/.github/styles/Vocab/ipfs-docs-vocab/accept.txt +++ b/.github/styles/Vocab/ipfs-docs-vocab/accept.txt @@ -100,6 +100,7 @@ Filebase filesizes? Filestore FQDNs? +Functionland gasless geospatial Gnutella diff --git a/.github/styles/pln-ignore.txt b/.github/styles/pln-ignore.txt index 9b8eb68ca..62fc0d126 100644 --- a/.github/styles/pln-ignore.txt +++ b/.github/styles/pln-ignore.txt @@ -75,6 +75,7 @@ flatf[ss] flatfs fleek fqdns +functionland gasless geospatial git(hub) diff --git a/docs/concepts/persistence.md b/docs/concepts/persistence.md index 59535321d..e9663900c 100644 --- a/docs/concepts/persistence.md +++ b/docs/concepts/persistence.md @@ -48,6 +48,7 @@ Some of the pinning services listed below are operated by third party companies. - [4EVERLAND Bucket](https://www.4everland.org/bucket/) - [Filebase](https://filebase.com/) +- [Functionland Fula](https://fx.land/) - [NFT.Storage](https://nft.storage/) - [Pinata](https://pinata.cloud/) - [Scaleway](https://labs.scaleway.com/en/ipfs-pinning/) diff --git a/docs/concepts/privacy-and-encryption.md b/docs/concepts/privacy-and-encryption.md index d66586e5b..d7b032ca6 100644 --- a/docs/concepts/privacy-and-encryption.md +++ b/docs/concepts/privacy-and-encryption.md @@ -54,6 +54,7 @@ IPFS uses transport-encryption but not content encryption. This means that your - [Ceramic](https://ceramic.network/) - [Fission.codes](https://fission.codes/) - [Fleek](../case-studies/fleek.md) +- [Functionland Fula](https://fx.land/) - [Lit Protocol](https://litprotocol.com/) - [OrbitDB](https://github.com/orbitdb) - [Peergos](https://peergos.org/) diff --git a/docs/how-to/peering-with-content-providers.md b/docs/how-to/peering-with-content-providers.md index 4aee59b31..904927b01 100644 --- a/docs/how-to/peering-with-content-providers.md +++ b/docs/how-to/peering-with-content-providers.md @@ -72,6 +72,12 @@ This list is provided for informational purposes only. The IPFS Project does not | ------- | --------- | |`12D3KooWGtYkBAaqJMJEmywMxaCiNP7LCEFUAFiLEBASe232c2VH`|`/dns4/bitswap.filebase.io/tcp/443/wss`| +### Functionland Fula Network + +| Peer ID | Addresses | +| ------- | --------- | +|`12D3KooWEGy1b9QLiQ4kyjk9GhF3vcWj3aQyVzfbuW7JeS1NdWhb`|`/dns4/ipfs.cloud.fx.land/tcp/443/wss`| + ### Storj | Peer ID | Addresses | diff --git a/docs/how-to/work-with-pinning-services.md b/docs/how-to/work-with-pinning-services.md index 5212e12bc..9f002b477 100644 --- a/docs/how-to/work-with-pinning-services.md +++ b/docs/how-to/work-with-pinning-services.md @@ -44,13 +44,14 @@ Third-party pinning services allow you to purchase pinning capacity for importan - [Pinata](https://pinata.cloud/) - [Filebase](https://filebase.com/) +- [Functionland Fula](https://fx.land/) - [Temporal](https://temporal.cloud/) - [Crust](https://crust.network/) - [Infura](https://infura.io/) - [Scaleway](https://labs.scaleway.com/en/ipfs-pinning/) ::: callout -As of June 2023, [Filebase](https://filebase.com) and [Pinata](https://pinata.cloud/) support the [IPFS Pinning Service API endpoint](https://github.com/ipfs/pinning-services-api-spec). +As of June 2024, [Filebase](https://filebase.com), [Functionland Fula](https://fx.land/) and [Pinata](https://pinata.cloud/) support the [IPFS Pinning Service API endpoint](https://github.com/ipfs/pinning-services-api-spec). ::: To add and use a remote pinning service directly in IPFS, you'll first need to have an account with that service. diff --git a/docs/quickstart/publish.md b/docs/quickstart/publish.md index ee3a22f72..248e70640 100644 --- a/docs/quickstart/publish.md +++ b/docs/quickstart/publish.md @@ -20,7 +20,7 @@ The web3.storage pinning service was chosen purely for demonstration purposes, a - [Overview](#overview) - [Pinning services](#pinning-services) - [Prerequisites](#prerequisites) -- [Uploading and pinning a file](#uploading-and-pinning-a-file) +- [Upload and pin a file](#upload-and-pin-a-file) - [CIDs explained](#cids-explained) - [Retrieving with a gateway](#retrieving-with-a-gateway) - [Summary and next steps](#summary-and-next-steps) @@ -117,3 +117,4 @@ Possible next steps include: - Try fetching the pinned file by following the [retrieval quickstart](./retrieve.md). - If you prefer to upload a file programmatically with JavaScript or Go, check out the [Web3.storage docs](https://web3.storage/docs/how-tos/store/). - Alternatively, try out [Filebase](https://filebase.com/), a pinning service that offers an [AWS S3-compatible API for pinning](https://docs.filebase.com/getting-started/s3-api-getting-started-guide), so you can use any S3-compatible SDK, e.g. [aws-sdk](https://www.npmjs.com/package/aws-sdk), and [many](https://github.com/s3tools/s3cmd) more. +- You can also try out [Functionland Fula network](https://fx.land), a pinning service that provides a true globally distributed and individually-owned nodes [Fula Network](https://docs.fx.land). The SDK supports mobile-native applications and offers built-in encryption. \ No newline at end of file diff --git a/docs/quickstart/publish_cli.md b/docs/quickstart/publish_cli.md index ae0f4ed66..db7c5927b 100644 --- a/docs/quickstart/publish_cli.md +++ b/docs/quickstart/publish_cli.md @@ -20,7 +20,7 @@ The web3.storage pinning service was chosen purely for demonstration purposes, a - [Overview](#overview) - [Pinning services](#pinning-services) - [Prerequisites](#prerequisites) -- [Uploading and pinning a file](#uploading-and-pinning-a-file) +- [Install and register to w3](#install-and-register-to-w3) - [CIDs explained](#cids-explained) - [Retrieving with a gateway](#retrieving-with-a-gateway) - [Summary and next steps](#summary-and-next-steps) @@ -119,5 +119,9 @@ Possible next steps include: - Check out [the lifecycle of data in IPFS](../concepts/lifecycle.md) to learn more about how publishing by pinning fits into the full lifecycle of data in IPFS. - Try fetching the pinned file by following the [retrieval quickstart](./retrieve.md). + +In addition to self-hosting, IPFS publishing can be augmented with third-party commercial services: + - If you prefer to upload a file programmatically with JavaScript or Go, check out the [Web3.storage docs](https://web3.storage/docs/how-tos/store/). - Alternatively, try out [Filebase](https://filebase.com/), a pinning service that offers an [AWS S3-compatible API for pinning](https://docs.filebase.com/getting-started/s3-api-getting-started-guide), so you can use any S3-compatible SDK, e.g. [aws-sdk](https://www.npmjs.com/package/aws-sdk), and [many](https://github.com/s3tools/s3cmd) more. +- You can also try out [Functionland Fula network](https://fx.land), a pinning service that provides a true globally distributed and individually-owned nodes [Fula Network](https://docs.fx.land). The SDK supports mobile-native applications and offers built-in encryption.