There's two specific attributes that are unique to IPFS.

1 - A content addressable URI protocol that allows you to locate a file without linking to a singly-owned and named server or host. This is not the case with HTTPS URL protocol.

2 - Open source clients where multiple parties, including competing parties and individual users, can all simultaneously and permissionlessly peer-to-peer host an asset behind the content addressed URI.

I understand that. This doesn't address https://news.ycombinator.com/item?id=32743041 or any of the subsequent discussion.

We are entering a recursive loop, because I’ve already responded to that. :)

And that's the problem, really. As pure tech IPFS is interesting (probably). But if it doesn't have concrete answers to user questions/problems apart from vague "yeah, maybe perhaps probably something will maybe happen", it's useless beyond a small following of hardcore geeks.