Jonny Mack
@nonlinear.eth
in as few words as possible: what are the fundamental differences between an api and a protocol?
14 replies
0 recast
0 reaction
Rohit Kulshreshtha
@rohit
Ownership of the receiver.
1 reply
0 recast
0 reaction
borodutch
@warpcastadmin.eth
permissionlessness
1 reply
0 recast
0 reaction
Michael Pfister
@pfista
Protocols are blueprints APIs are implementations
0 reply
0 recast
0 reaction
moreReese
@morereese
Protocol is a rule set. API is a protocol for software.
0 reply
0 recast
0 reaction
Carlos Acevedo
@carlosace
@perl
0 reply
0 recast
0 reaction
matt ๐ญ
@matthewmorek
Protocol = communication blueprint API = specific communication layer that can follow a protocol
0 reply
0 recast
0 reaction
Ben
@benersing
@perl
0 reply
0 recast
0 reaction
vincent
@pixel
Who owns the data: API means there's an entity who owns data, protocol means everyone's on equal ground.
0 reply
0 recast
0 reaction
m_j_r
@m-j-r.eth
the rate limit is either physical or practical
0 reply
0 recast
0 reaction
Nicholas Charriere
@pushix
Protocol is a spec, you implement it (or not) API exists and is provided by a central authority
0 reply
0 recast
0 reaction
Mitch
@off-fleek
API = system interface (provides functionality) protocol = inter-system interface (specifies communications among functionalities)
2 replies
0 recast
0 reaction
Jason Goldberg โ๏ธ ๐
@betashop.eth
protocols are permissionless api's are permissioned
1 reply
0 recast
0 reaction
Alex Loukissas ๐
@futureartist
Naively in my head: API: someone runs it for you (e.g. Stripe) Protocol: someone implements it and you can build around it (e.g. IMAP) - not to be confused with open standard though (e.g. internal protocols within a company, e.g. WhatsApp)
0 reply
0 recast
0 reaction
Tim OโShea
@timothyoshea
Protocol = unstoppable organism API = stoppable access to someones system
0 reply
0 recast
0 reaction
