Since you're a developer at protocol labs, I will assume you remember why beaker dropped IPFS in favor of DAT. I think IPFS is cool but the biggest hurdle for adoption is the naming scheme. More specifically what happens when a file content changes. You have IPNS to handle this but as far as I know it's virtually unusable because it's extremely slow. And I got the impression that you guys have no real solution for this, and maybe IPNS is not even one of your top priorities because you're focused on other important things.
But as a user this matters a lot because without a name resolution system, we're left with static files only, and while this may be a good alternative to S3, this means that's about it and people can't build apps on top of it. I wonder what your plans are and if you have any solution to building an actual functional IPNS, or if you're focused on building an S3 alternative at the moment.