Currently the only thing that this does is iterate through all Peepeth events - and un it through the current version of parsers. The only thing that they do currently is copying the centralized aspects of Peepeth ( the avatar images and backgrounds ) to IFPS and create a tree of linked peeps on IPFS. A demo of the output is currently at https://peepfeed.netlify.com - but there is a lot more that we could do using this data..
Architecture of the parsers
Each peep event is read from the smart contract in the peepin.js file. Each event first trigggers a download of the related IPFS data (The IPFS hash in the contract function) and then looks up if a parser exists for its type, and if so it passes all this data to the corresponding parser ( see parsers/index.js for the mapping of data-types -> parser.
The parser then does whatever he wants with the data. Currently the implemented parsers use a local 'leveldb' database to store some of its info for easiers lookups later.
If you want to help implement parsers, there's some info and ideas in this epic#2
{
"type": "peep",
"content": "Yay mobile!!\n\nThe great news is we have @pete from #Cipher @sid from #Toshi and @vikmeup from #Trust (I like to shout about mobile)\n\nBetween those three we can get a great mobile experience. ",
"pic": "",
"untrustedAddress": "0x13ebd3443fa5575f0eb173e323d8419f7452cfb1",
"untrustedTimestamp": 1521775536,
"shareID": "QmREFpaf53MLW1C3MyHxgmbVdUxS5VjKHjeP2hPuhEjwbg",
"parentID": null
}
{
"type": "peep",
"content": "...and Peepeth is live! Thanks to all who helped.\n\nShare what matters, reward the truth, and have fun!",
"pic": "",
"untrustedAddress": "0x30755d3e65c0cf46c35b72d11e52d941c5fc3a3e",
"untrustedTimestamp": 1521135122,
"shareID": null,
"parentID": null
}
Currently we need more insights in the data format and improve the parsers. So if you want to take a look at the issues, please install the ZenHub plugin for your browser (https://www.zenhub.com/) and head over to the board. https://github.com/sponnet/peepin#boards
请发表评论