|
|
|
|
|
|
by grishka
1524 days ago
|
|
|
And after reading the whole article, I'd like to add: it really helps to treat these protocols like APIs. As in, if you're building an XMPP server, you wouldn't want to expose the actual clients as resources, for example. You'd instead just send each message to each connected client and present them all as one single "client" to other users and for the purpose of s2s federation. That would eliminate an entire class of issues, like messages getting lost, AND improve the user experience at the cost of a slight, barely noticeable spec noncompliance. I do a variation of this for ActivityPub in my project already. Except I don't implement c2s ActivityPub at all. |
|
|