Why We Never Got Back to IPFS
I wrote some relatively simple programs to handle our IPFS archives. They were stable and predictable. The problem was, IPFS itself was a beast that eats up both traffic and hardware resources, which have since then gotten a lot more expensive (especially this past year).
As of this month, it has been 6 years since IPFS was adopted by us. In 2023 (or late 2022) we recognised, based on the media at least, that IPFS had become a domain of 'bros' and scammers. I too occasionally received malicious E-mails with links in them pointing to HTTP nodes/relays/gateways for IPFS. That served to (re)affirm what the media said. IPFS was getting a bad reputation. It probably deserved this.
Practically speaking, we could get back to IPFS any time (feasibility isn't a barrier; we have all the objects in place). But it would mostly lead to risk and problems.
IPFS itself is not malicious, but as a distributed, decentralised system it does adopt and potentially circulate a vortex of malicious traffic/activities. █