Steph
@hun3y.eth
Need gigabrain clarity on this: what comes first, the protocol or the API? What are examples of: + protocol --> API + API --> protocol + API <--> protocol (simultaneous launch)
2 replies
0 recast
0 reaction
Carsten
@cpoetter.eth
the non-technical guy (=me) says: applications are built on top of protocols. therefore protocol --> API (application programming interface)
1 reply
0 recast
1 reaction
Carsten
@cpoetter.eth
though not all APIs are built on protocols. Facebook, Twitter,... all provide APIs.
1 reply
0 recast
1 reaction
Steph
@hun3y.eth
what about an application built on top of multiple composable protocols, and then that application launches an API ? (FB and Twitter are probs good examples?)
1 reply
0 recast
0 reaction
Carsten
@cpoetter.eth
it can. my naive mind tells me that an API only makes sense if you have data that's rather unique (e.g. you took raw data from those protocols and made some funky shit with them) and you want to make it available to other apps or companies so that they can build even funkier shit with data that's unique to them.
1 reply
0 recast
1 reaction
