Earlier quoted context omitted.
IPFS doesn't help - you still need a store-and-forward architecture for messaging, so you might as well use that for images too. IPFS is not a store-and-forward architecture; a file does not get automatically stored by the system, so when the sender disconnects, the file is no longer accessible. There's "solutions" to this, like Filecoin, but nobody wants folks to be paying to upload images. Or, in other words - the…
My idea was more in that every p2p node of Matrix can also be a IPFS server, and be used to pin all of your own media + a small cache of your contacts/group media. You wouldn't need to save all of the media your homeserver is dealing with, but you still could be reasonably sure that your node would be able to find all media you are supposed to access. Given that the post talks about libp2p and how libp2p's main drive…
libp2p is what IPFS is built on, not the other way round.