# Best practices for sharing community IPFS infrastructure without spamming?

**URL:** <https://discuss.ipfs.tech/t/best-practices-for-sharing-community-ipfs-infrastructure-without-spamming/19997>\
**Category:** Ecosystem and Usage\
**Tags:** go-ipfs, blockchain, ipfs-cluster, files\
**Created:** [January 21, 2026, 6:01pm UTC](https://discuss.ipfs.tech/t/best-practices-for-sharing-community-ipfs-infrastructure-without-spamming/19997 "2026-01-21T18:01:09Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![DataHosting](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/datahosting/32/9662_2.png) [@DataHosting](https://discuss.ipfs.tech/u/DataHosting)\
**Post date:** [January 21, 2026, 6:01pm UTC](https://discuss.ipfs.tech/t/best-practices-for-sharing-community-ipfs-infrastructure-without-spamming/19997/1 "2026-01-21T18:01:09Z")

</div>

Hi everyone,

I’m running a small IPFS setup mainly to gain real-world operational experience and contribute back to the ecosystem. The setup includes:

- IPFS Kubo (public read-only gateway)

- IPFS Kubo (private/authenticated gateway)

- IPFS Cluster with configurable replication

The goal is to understand:

- real storage and bandwidth costs,

- cluster behavior with different replica counts,

- long-term retention and pin guarantees,

- and how developers actually use IPFS in production.

I’d like to ask the community:

- What is the **preferred way to share community IPFS infrastructure or tools** without it being considered advertising?

- Are **benchmarks, open-source tools, or tutorials** generally the right approach?

- Are there ecosystem lists or directories that are recommended for infrastructure providers?

- Any common mistakes to avoid when sharing gateways or cluster endpoints?

I’m not looking to spam or push a service — more interested in contributing useful data (benchmarks, docs, tools) and learning from real usage.

Any guidance from people who’ve done this before would be appreciated.  
Thanks!