Skip to content

Conversation

@2color
Copy link
Member

@2color 2color commented Jan 23, 2026

@github-actions
Copy link
Contributor

🚀 Build Preview on IPFS ready

@mishmosh
Copy link
Collaborator

This is great as a specific how-to. Is there another, complementary place we can write about all the ways geospatial users can benefit from IPFS?

From live meeting:

  • Consider title “Scientific Data” as category
    • Ecosystem Tooling
    • Guide to Publishing Scientific Data
  • IPFS is used by the geospatial community for better collaboration, data integrity, and open access.
    (make sure we can describe some of the architectures used)
    • Connecting kubo to your existing data repositories (stac catalog)
    • Private clusters (but open retrieval) or “Collaborative publishing”
    • Provenance

@2color 2color marked this pull request as ready for review February 4, 2026 16:14
Copy link
Collaborator

@mishmosh mishmosh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few suggestions and comments inline, but I'm confident you can take it from here. Would also like to see @vmx review.


Before starting, ensure you have:

- A Zarr data set for
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fragment?

Before starting, ensure you have:

- A Zarr data set for
- [Kubo](/install/command-line/) or [IPFS Desktop](/install/ipfs-desktop/) installed on a machine with a public IP
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

machine with a public IP

can we link to a resource to help people check if they have a public IP, or configure one if not?


1. **Merkleizes** the folder: converts files and directories into content-addressed blocks with UnixFS
2. **Pins** the data locally: prevents garbage collection from removing it
3. **Queues providing**: announces to the IPFS network that your node has this data
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Queues providing" introduces multiple new terms at once. Would any of these alternates work?

  • Broadcasts availability
  • Starts providing
  • Starts advertising
  • Advertises the content


## Step 5: Content Discovery

Users need a way to discover your datasets. Choose an approach based on your needs:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Users need a way to discover your datasets. Choose an approach based on your needs:
Now that your data is available on the public network, the next step is making it discoverable to others. Choose a sharing approach based on your needs:


### Option B: Use IPNS for Updatable References

IPNS provides a stable identifier that you can update when datasets change:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
IPNS provides a stable identifier that you can update when datasets change:
If you want to share a stable identifier but be able to update the underlying dataset, create an [IPNS](https://docs.ipfs.tech/concepts/ipns/) identifier and share that instead. This is useful for datasets that get updated regularly —users can bookmark your IPNS name and always retrieve the latest version.

(not sure if that's the correct way to link internally)

ipfs name publish /ipfs/<new-dataset-cid>
```

Users can subscribe to your IPNS name to always get the latest version.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this an explicit, persistent "subscribe" function? Or do we recommend using it like an IPFS CID (in which case maybe we should describe this without the word "subscribe")

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants