A design for IPFS version RSS

FledgeXu · February 10, 2021, 8:07am

wclayf:

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"
   cid: "QmW2WQi7j6c7UgJTarActp7tDNikE4B2qXtFCfLPdsgaTQ/cat.jpg"
   mime: "image/jpeg"
}

haha, This is the thing that I did in another protocol.

github.com

HermesProtocol/HermesDoc/blob/1f87451c26f56109f026c00d50d848b49105bc04/protocal.ipldsch#L25


      
          type Content enum {
              | ImageContent
              | VideoContent
              | AudioContent
          }
          type ImageContent struct {
              version Version
              mime RFC6838
              image Link
          }
          type VideoContent struct {
              version Version
              mime RFC6381
              video Link
          }
          type AudioContent struct {
              version Version
              mime RFC6381
              audio Link
          }
          type Operation enum {

@plantimals Now I’m more interested in another protocol.

And, It’s just an idea. If it inspired you, you can write a new post talk about your idea.

Topic		Replies	Views
Structures for feeds on IPLD? Protocol ipld , use-cases-and-apps	1	234	January 19, 2023
IPLD and IPFS - A Pitch for the Future ⚾ Protocol ipld	0	551	August 31, 2022
IPFS conceptual questions from a semi-noob	3	700	February 24, 2018
XML as an IPLD format Ecosystem ipld	3	648	April 12, 2018
Linking data on IPFS	1	720	November 29, 2017

A design for IPFS version RSS

Related Topics