tip parser

[sponnet]

• [ ] create basic parser
• [ ] create JSON schema for tip format
• [ ] create link between tip and original peep (use IPFS hash as primary key)
• [ ] create tree from parent to children - save it in local cache for easy lookup

[sponnet]

sample

{
    "type": "tip",
    "content": "Great job Bevan!",
    "parentID": "QmQfeQuPE3sxeCSrmHMLXxUZysRkA7YsodLYkPkrYXw9CU",
    "shareID": null,
    "untrustedAddress": "0x788d7dcc3c5a23ab08b343e25d76e0cd3174761c",
    "untrustedTimestamp": 1521156236
}

Tip is another data format that needs a JSON schema - it has different fields than a peep - but is similar in structure. It seems that there is a difference when you

• tip a peep or a reply ( parentID is filled in )
• tip a share ( shareID is filled in ) ( to be verified )