This is just a tracking issue to note that the kubo-sidecar tutorial provided in the README.md of this repo relied on some internal APIs that are unstable. I am working on a PR to update the tutorial (working notes here) with a variation for post-v0.38 versions of kubo (which require the new ProvideSweep routing mechanism to be disabled before fallback to older provide subsystem will work), but the more fundamental issue is that work on a more flexible/protocol agnostic way of using PUT over HTTP to publish records has yet to be specified and negotiated across stakeholders, and is currently unfunded technical debt without a champion or governance structure. Lidel has helpfully documented the history of the current PUT API used by IPNI, but since the maintainers of Kubo (and of the IPFS specs generally, and most importantly the test vectors that allow them to add features with automated regression testing) do not have bandwidth or scope to address this backlog item, it is at serious risk of being further broken by adjacent work, as DHT announcing has experience a series of major upgrades in recent versions and more are planned for 2026.
Publishing to IPNI from [a sidecar to] the IPFS reference implementation isn't necessarily essential to the smooth interoperability of the network, and kubo growing increasingly incapable of (or difficult to configure to allow) IPNI publishing would probably require researching and documenting a more involved tutorial for IPNI publishing with boxo and/or helia, etc. So this tracking issue may, over time, get renamed to "new tutorial for readme"
This is just a tracking issue to note that the kubo-sidecar tutorial provided in the README.md of this repo relied on some internal APIs that are unstable. I am working on a PR to update the tutorial (working notes here) with a variation for post-v0.38 versions of kubo (which require the new ProvideSweep routing mechanism to be disabled before fallback to older provide subsystem will work), but the more fundamental issue is that work on a more flexible/protocol agnostic way of using PUT over HTTP to publish records has yet to be specified and negotiated across stakeholders, and is currently unfunded technical debt without a champion or governance structure. Lidel has helpfully documented the history of the current PUT API used by IPNI, but since the maintainers of Kubo (and of the IPFS specs generally, and most importantly the test vectors that allow them to add features with automated regression testing) do not have bandwidth or scope to address this backlog item, it is at serious risk of being further broken by adjacent work, as DHT announcing has experience a series of major upgrades in recent versions and more are planned for 2026.
Publishing to IPNI from [a sidecar to] the IPFS reference implementation isn't necessarily essential to the smooth interoperability of the network, and kubo growing increasingly incapable of (or difficult to configure to allow) IPNI publishing would probably require researching and documenting a more involved tutorial for IPNI publishing with boxo and/or helia, etc. So this tracking issue may, over time, get renamed to "new tutorial for readme"