XMPP platforms, specifically Libervia and Movim, are developing systems with persistent messages by utilizing Atom Over XMPP (XEP-0277 and XEP-0472) for publishing.
IPFS can be a preferred multimedia delivery solution for most XMPP servers that would choose to operate as publishing platforms.
How can the IPFS community assist in increasing the popularity of IPFS over XMPP?
Mr. Stephan Paul Weber @singpolyma is already delivering multimedia files of JMP Journal (powered by Libervia) via IPFS.
fwiw there is a docs page that describes how to reference content-addressed data on the HTTP-based web:
For future-proof spec work, HTTP Gateways | IPFS Standards can be linked to as source of standards / conventions.
If we talk about referencing resources from Atom-like XML feeds, TLDR is to follow gateway URLconventions, namely /ipfs/cid paths:
Clients that support the IPFS protocol can ignore HTTP details and retrieve data natively [based on root CID], while those that don’t can fetch the resource from HTTP server at
ipfs.iogateway, as long as they have the content identifier (CID). Whenipfs.ioor any other public gateway goes down, IPFS aware clients will still be able to fetch the content from the IPFS network as long as at least one node still provides the data behind the CID to the network
One can also use ipfs://cid URIs without specifying a default/fallback HTTP gateway, but that shifts burden on client to implement it – HTTP URLs provide more gentle user onboarding via progressive interop.
