@mat mostly agree: client-to-client protocols is a real gap right now.
-
@mat mostly agree: client-to-client protocols is a real gap right now. everyone assumes s2s is all that matters and consequently builds monolith servers. the ironic thing is that those monoliths function more as clients than servers, as user-agents doing a form of c2c protocol which is why there are so many interop issues when two peers don’t share the exact same protocol. you can get text from A to B, and you can mandate it to be an AS2 Activity, but beyond that? eh.
-
@mat mostly agree: client-to-client protocols is a real gap right now. everyone assumes s2s is all that matters and consequently builds monolith servers. the ironic thing is that those monoliths function more as clients than servers, as user-agents doing a form of c2c protocol which is why there are so many interop issues when two peers don’t share the exact same protocol. you can get text from A to B, and you can mandate it to be an AS2 Activity, but beyond that? eh.
@mat i’m of the opinion that messaging and publishing ought to be considered different communication paradigms. in a sense, messaging is just transport, while publishing is just messaging with persistence, but we use them differently even though mechanistically they work very much the same (and transport protocols are basically all messaging protocols over some session between peers). but transport alone isn’t enough; we need identity and we need storage.
-
@mat i’m of the opinion that messaging and publishing ought to be considered different communication paradigms. in a sense, messaging is just transport, while publishing is just messaging with persistence, but we use them differently even though mechanistically they work very much the same (and transport protocols are basically all messaging protocols over some session between peers). but transport alone isn’t enough; we need identity and we need storage.
@mat currently we handwave that away and collapse everything into a single HTTP server+client that handles identity+storage+transport on more or less a single domain. i’d like to see that split up into its constituent 3 parts: an identity server, a storage server, and a transport protocol for passing resources around while making some resources persistent through the identity+storage layers. this can be generic across various transport protocols and negotiated bw 2 peers.