These are chat archives for etherapis/etherapis

8th
Feb 2016
void4
@void4
Feb 08 2016 12:43
ping!
Question: Do you plan to integrate IPFS/libp2p? Otherwise I will do this as a long term project.
Péter Szilágyi
@karalabe
Feb 08 2016 12:44
The focus will be more towards generic web/rest APIs
not sure long term what additional techs could be supported
but the first target is the classical online service world
void4
@void4
Feb 08 2016 13:06
Have you already decided on a service description language?
Ethereums' Whisper is already sufficient for most applications, but it would be neat to be able to address services by their identities
Péter Szilágyi
@karalabe
Feb 08 2016 13:08
We're not targeting Ethereum services
We're targeting plain HTTP RESTful services
Péter Szilágyi
@karalabe
Feb 08 2016 13:29
current web APIs aren't broken from the technological decentralization perspective, so that's not the pain point that needs to be sorted out imho
the problematic part is the trust centralization, that's what we're aiming to solve
void4
@void4
Feb 08 2016 13:45
I corrected it: "This includes hardware- and software-, but also indirectly real services."
This is more about finding a transport and protocol independent way to describe and interact with services.
If we make the bold assumption that libp2p/Whisper/Swarm become "default" components for "Web3" as well, it could be necessary. Have you heard of IPFSs' multi-stream and multi-protocol descriptors?
Jeffrey Wilcke
@obscuren
Feb 08 2016 13:49
Etherapis isn’t about any of the above mentioned technologies
void4
@void4
Feb 08 2016 13:49
Okay, so I assume you will stick to contracts and HTTP REST?
Jeffrey Wilcke
@obscuren
Feb 08 2016 13:51
Better put, we offer a decentralised API payment system with zero trust. The technology, while interesting to you and me, doesn’t really matter. But yes, to answer your question, it will be HTTP (REST doesn’t matter either, we don’t offer the API, it are the service providers that do)
and the underlaying payment system is written using smart contracts
void4
@void4
Feb 08 2016 13:52
Okay, thanks :)
Péter Szilágyi
@karalabe
Feb 08 2016 16:52
@obscuren Did you merge in the etherapis ethereum fixes into the upstream repo?
I.e. can I switch over the codebase to upstream + go vendoring?
Jeffrey Wilcke
@obscuren
Feb 08 2016 17:29
yep