4 ms·
XMPP has already been mentioned (thanks edhelas). What I didn't see mentioned was ActivityPub (https://www.w3.org/TR/activitypub/ https://www.w3.org/TR/activity
by Communitivity 8y ago
XMPP has already been mentioned (thanks edhelas). What I didn't see mentioned was ActivityPub (https://www.w3.org/TR/activitypub/ https://www.w3.org/TR/activitypub/), or some of the advanced messaging features users have come to expect (e.g., store and forward, forms, automated route handlers).
What I am curious about are the following questions?
1) What differentiates WebSub from XMPP?
2) What differentiates WebSub from ActivityPub?
3) How are you handling the N-squared delivery problem, if you are delivering content directly to each subscriber with HTTP POSTs?
4) Does WebSub currently support store and forward? If not, is that on a roadmap for a future version?
5) Same as 4, except for support for forms and form responses? Examples are a builtin Yes or No reply, or a builtin poll vote.
6) Same as 4, for automated message routing.
7) Why not have it be transport-agnostic, instead of mandating HTTP? And why HTTP? The growing trend is towards more decentralized.
8) How does this compare to Sir Tim Berners-Lee's SOLID (https://solid.mit.edu/ https://solid.mit.edu/)?