The problem with ipfs is finding the information, if you have a centralized directory, what good is ipfs? This is where I see a merger of the two worlds, ipfs + nostr. The client supports ipfs, it is the client itself that is responsible for hosting your files such as images and videos. When you post a note with a file, you attach the ipfs path to that file. For this we could implement a NIPS.
Discussion
You could already post https://ipfs.io/ipfs/hash links and deliver them via local IPFS if available.
The nice thing about this would be that the client supports ipfs and can display the file.
But it's just a concept idea. Maybe these days I'll get into it.