Launched in 2017 with the goal of building an uncensorable, resilient web, IPFS has grown into infrastructure that handles roughly 250 million requests per day. It powers censorship-resistant publishing, web3 infrastructure, scientific data archives, developer tooling, and long-lived content across the open web.
No quarrel with the gateway advice. We run our own gateways and have for years, so none of this changes anything for us. Anyone serious about content addressing has been self-hosting for nearly a decade.
Which is why the post reads oddly. It answers a question serious users settled long ago, and doesn’t touch the one that appeared last week.
Nothing here says who maintains Kubo, Boxo or Helia after September 30, who triages a security report, or who cuts releases. delegated-ipfs.dev and the bootstrap nodes go unmentioned, though Shipyard’s post says it stops operating both. Badbits too.
The stated direction is “specs, conformance tests, implementation diversity”. ipfs/specs#291, the issue to populate the specs-stewards team, has been open since June 2022 with nobody named to it.
Those are the things anyone planning a business around this needs, and they are all still open:
Answers there would help a lot.
two weeks and no succession plan, pretty sad