You are viewing a single comment's thread from:
RE: [piston.web] First Open Source Steem GUI - Searching for alpha testers
Currently, there still is a central point of failure and that is the this.piston.rocks API server. However, I plan to extend this quite a bit and use geolocated DNS with several servers around the globe to make it more robust ..
I think it would be more impotent to have a way for independent community members to run API nodes them self, then having a nice geo redundant deployment managed by one party.
What dose the API Server consists of? Is this just the API of steemd or is there another service involved and if so would it be possible to have the code available to play around with and try to build a independent setup connecting to a local steem-node?
Not to be ungrateful, my first reaction to this post was off course: awesome, finally a way to use steem independent of steemit.com like a real decentralized app. And it still locks to me a lot like that, only this small part seems missing, so thanks a lot for this awesome project!
Wouldn't it be a good idea to offer an incentive for running an API server in steemd itself? Like Masternodes for DASH, or an Incentive Node for VCASH.
Absolutely, I think it can be easily done by just asking Steem to pay for their public APIs. A post about the APIs statistics now and then might bring in enough money to continue service. Time will tell.
Is it hard to run your own API server?
I think someone has even created a docker image for steem .. search on steemit or github
Yes it is hard if you are fluent with the required programming language.
Funny, my original comment mentioned having thousands of clones of this.piston.rocks, but I ended up removing that part before I posted and talked about how this gets us a step closer. Maybe some day that code can also be decentralized, self-hosted, and distributed. Either way, thanks again for all your hard work, @xeroc! To me, stuff like this is the difference between success and... something else that isn't success. :)
In the realm of decentralized services, I think that consul is really, really overlooked, especially the potential of consul, coupled with ultra-low-cost servers. Once a machine is in a consul cluster, it is "bound" to the consul master and that master can execute commands on it as though it were root.
Consul also manages services and service discovery.
It can be run alongside Nomad, which can schedule anything that can be run on linux in an extremely neat, tight fashion.
I wanted to add the ability to change the API node. piston allows that already, but the gui has no feature for that yet. It will come for sure.
Yes, we need each one a node, unfortunately actually steem doesn't build on ubuntu 14 or debian jesse so it's really difficult to get one, the to be sure nobody will get one they take this wonderful instructions https://github.com/steemit/steem/blob/master/BUILD_UBUNTU.md and no bin release https://github.com/steemit/steem/releases actually I find this a shame... Fortunatly at least @xeroc works with us :)