I agree there badly needs to be some way to store as text (like YAML, JSON, and/or XML) a file that can contain a hierarchical structure containing at a minimum these properties (shown as JSON here)
name: "My Favourite little kitty"
This way people can publish data structures to each other, and download their content (technically an index of their content, not the actual content) from pinning services, or upload to pinning services.
If there were a simple standard layout for this kind of file, people could move from one pinning service to another by downloading all their PINs and then sending them to the new service, etc.
One of the big goals also of Social Media 3.0 (Web 3.0) is for people to be able to download all their content, so ultimately also when ActivityPub Objects are stored on the Fediverse as IPFS links it means people can also download their entire social media history as one of these JSON files.
@ecloud I know you’re actively working on Social Media like I am, so you likely agree with this. Maybe there’s already a “file format” under development for this? I don’t know. But people are continually bringing up the need for mime info to be somehow cleanly available at least in some sort of file format.
EDIT: I posted all the above as independent from RSS, but I think perhaps the IPFS version of RSS (if there ever is one) should be hierarchical, rather than “flat” like RSS. RSS is ideal for a single feed that is just a reverse chronological list, but when it comes to actually organizing information, the ability to have a hierarchical structure in the file is critical, and I don’t think RSS can do that. We really don’t need something fancy. A “level 1” compliance would be just what’s shown above: name, cid, mime.