Application design: Content synchronization between STEEM and glogchain
Okay, so when I began to learn go, I heard from all the older, wiser folks that go was all about the stdlibs. Go is all about the stdlibs. So I've re-designed Ingestron in order to connect steem to glogchain and to the larger cosmos ecosystem of blockchains.
This is only going to work if the relevant APIs on the steem side have stabilized from the last time I attempted. What am I talking about? To understand what I am referring to, please see the uptime logs of streemian.com.
That's what I am talking about.
Finished Tasks
- [x] Launch a glogchain testnet
- [x] Develop a mental "game plan" for implementation
The plan: Instead of using libraries to access APIs on either side of this process, I will use net/http or the curl library that you can use from golang.
- Per-user bidirectional content flow-- using posting keys, move content between the two chains on the back end. Posting keys are held in RAM only. Process is entirely user-controlled.
Immediate tasks
- [ ] Diagram: Post synchronization
- [ ] code it: Post synchronization
- [ ] Test it: Post Synchronization
Objective
Graphene and tendermint are really similar concepts, but surely not the same. I want to inspire people to wonder what could be accomplished through earnest collaboration.
This post has been ranked within the top 10 most undervalued posts in the second half of Feb 02. We estimate that this post is undervalued by $32.94 as compared to a scenario in which every voter had an equal say.
See the full rankings and details in The Daily Tribune: Feb 02 - Part II. You can also read about some of our methodology, data analysis and technical details in our initial post.
If you are the author and would prefer not to receive these comments, simply reply "Stop" to this comment.