> Return control back to the user after most (not all) of the PUT RPCs have succeeded and continue with the remaining ones in the background.

Making things faster by doing less (and not the same) been speeding up computing since forever! Can't help but feel like it's slightly misleading to call the providing ("publishing") faster when it's not actually doing the same, it's just that most parts turned async instead of waiting for confirmation.

Wouldn't this lead to the problem where the user things everything been provided properly, but once others try to find it, the records haven't yet been published? As far as I understand, it'd still take mostly the same amount of time until the entire CID (not just some of them) are available to others, the only thing that got "faster" is the end-user UX of the one providing?

Is anyone still (or has anyone ever) used IPFS in production?

I’m not talking about technology demos such as Wikipedia-on-IPFS (which indeed worked and was impressive) but where IPFS is actually being relied on for some functionality.

Is it also possible to speed up lookup? I never used IPFS much as it took several minutes to find a cid.

I'll add to the "is it still...?" questions.

Last I was told about it, there was no way to delete stuff from IPFS. Nothing enforceable, at least. Setting aside that public stuff is "impossible" to delete on the internet, there's something appealing to me about being able to shut off my server. Feels like that is less possible with IPFS hosted content.

Does anyone have some perspective for me about removing content?

Are the defaults still leaking your whole internal and external IP allocations to the dHT still?

Its security posture was absolutely fucking gross the last time I reviewed it.

And of course, there's a shitcoin bolted on as well. Last thing I want to do is feed into FileCoin. Of course, everything new these days has some financial interaction crap bolted on to entice speculators and ilk.