Added Functionland Fula network pinning service

Added Functionland Fula network as a pinning service. The corresponding web-ui PR is: ipfs/ipfs-webui#2242
ehsan6sha · Jun 28, 2024 · 6facb8b · 6facb8b
1 parent 25c5a82
commit 6facb8b
Show file tree

Hide file tree

Showing 7 changed files with 29 additions and 15 deletions.
diff --git a/.github/styles/Vocab/ipfs-docs-vocab/accept.txt b/.github/styles/Vocab/ipfs-docs-vocab/accept.txt
@@ -97,6 +97,7 @@ explainers?
 Fabien
 failovers?
 Filebase
+Functionland
 filesizes?
 Filestore
 FQDNs?

diff --git a/.github/styles/pln-ignore.txt b/.github/styles/pln-ignore.txt
@@ -79,6 +79,7 @@ explainers
 Fabien
 failover
 Filebase
+Functionland
 Filecoin
 filecoin
 Filestore

diff --git 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/)
 - [Estuary](https://estuary.tech/)
+- [Functionland](https://fx.land/)
 - [Filebase](https://filebase.com/)
 - [Infura](https://infura.io/)
 - [Kriptonio](https://kriptonio.com/)

diff --git a/docs/how-to/peering-with-content-providers.md b/docs/how-to/peering-with-content-providers.md
@@ -66,6 +66,12 @@ This list is provided for informational purposes only. The IPFS Project does not
 | ------- | --------- |
 |`12D3KooWGaHbxpDWn4JVYud899Wcpa4iHPa3AMYydfxQDb3MhDME`|`/dns4/ipfs.ssi.eecc.de`|
 
+### Functionland Fula Network
+
+| Peer ID | Addresses |
+| ------- | --------- |
+|`12D3KooWEGy1b9QLiQ4kyjk9GhF3vcWj3aQyVzfbuW7JeS1NdWhb`|`/dns4/ipfs.cloud.fx.land/tcp/443/wss`|
+
 ### Filebase
 
 | Peer ID | Addresses |

diff --git a/docs/how-to/work-with-pinning-services.md b/docs/how-to/work-with-pinning-services.md
@@ -43,14 +43,15 @@ If you've decided that creating your own pinning service is right for you, learn
 Third-party pinning services allow you to purchase pinning capacity for important data. Each service has its own approach to pinning data and managing pins, so users should do their research to ensure that the service meets their particular needs. Service providers include, but are not limited to:
 
 - [Pinata](https://pinata.cloud/)
+- [Functionland](https://fx.land/)
 - [Filebase](https://filebase.com/)
 - [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, [Functionland](https://fx.land/), [Filebase](https://filebase.com) 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
@@ -17,13 +17,14 @@ The web3.storage pinning service was chosen purely for demonstration purposes, a
 
 ## Contents <!-- omit from toc -->
 
-- [Overview](#overview)
-- [Pinning services](#pinning-services)
-- [Prerequisites](#prerequisites)
-- [Uploading and pinning a file](#uploading-and-pinning-a-file)
-- [CIDs explained](#cids-explained)
-- [Retrieving with a gateway](#retrieving-with-a-gateway)
-- [Summary and next steps](#summary-and-next-steps)
+- [Publish a file with IPFS](#publish-a-file-with-ipfs)
+  - [Overview](#overview)
+  - [Pinning services](#pinning-services)
+  - [Prerequisites](#prerequisites)
+  - [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)
 
 ## Overview
 
@@ -116,4 +117,5 @@ 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).
 - 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/).
+- You can also try out [Functionland](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. As an example, you can checkout the FxFotos app, which is designed as an alternative to Media Sync applications [GitHub Repo](https://github.com/functionland/fotos) and live on [Google Play](https://play.google.com/store/apps/details?id=land.fx.fotos)
 - 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.
diff --git a/docs/quickstart/publish_cli.md b/docs/quickstart/publish_cli.md
@@ -17,13 +17,14 @@ The web3.storage pinning service was chosen purely for demonstration purposes, a
 
 ## Contents <!-- omit from toc -->
 
-- [Overview](#overview)
-- [Pinning services](#pinning-services)
-- [Prerequisites](#prerequisites)
-- [Uploading and pinning a file](#uploading-and-pinning-a-file)
-- [CIDs explained](#cids-explained)
-- [Retrieving with a gateway](#retrieving-with-a-gateway)
-- [Summary and next steps](#summary-and-next-steps)
+- [Publish a file with IPFS using the command line](#publish-a-file-with-ipfs-using-the-command-line)
+  - [Overview](#overview)
+  - [Pinning services](#pinning-services)
+  - [Prerequisites](#prerequisites)
+  - [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)
 
 ## Overview
 
@@ -120,4 +121,5 @@ 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).
 - 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/).
+- You can also try out [Functionland](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. As an example, you can checkout the FxFotos app, which is designed as an alternative to Media Sync applications [GitHub Repo](https://github.com/functionland/fotos) and live on [Google Play](https://play.google.com/store/apps/details?id=land.fx.fotos)
 - 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.