¹ https://mail.jabber.org/pipermail/operators/2013-February/00... and then https://mail.jabber.org/pipermail/operators/2013-May/001680....
807 karma · joined July 6, 2011
¹ https://mail.jabber.org/pipermail/operators/2013-February/00... and then https://mail.jabber.org/pipermail/operators/2013-May/001680....
https://snikket.org/ is worth checking out as a (self-)hosted personal chat system.
https://www.w3.org/TR/websub/ formerly PubSubHubbub was used to notify subscribers, but it was optional and subscribers would fall back to polling. WebSub could be a separate service.
The trickiest part is handling replies, which involves some cryptography to prevent spoofing. But this too could be done by polling, only then you only get replies from those you subscribe to. ActivityPub does this with crypto too IIRC.
And then crickets for 3 years...
And then along comes https://datatracker.ietf.org/doc/draft-ietf-dnsop-svcb-https... defining a "SRV2", SVCB and also its identical twin the HTTPS RR (same format, different RR number). I have a fear that those routers will end up supporting the HTTPS RR but not SVCB...
qrencode -t utf8 'WIFI:T:WPA;S:network;P:password;;'You can include the same header multiple time in a HTTP message, and this is equivalent to having one such header with a comma-separated list of values.
Then there's WWW-Authenticate (the one telling you to re-try with credentials). It has a comma-separated list of parameters.
The combination of those two leads to brokenness, like how recently an API thing would not get Firefox to ask for username and password, because it happened to have put "Bearer" before "Basic" in the list.
Other parts of the XMPP ecosystem also have easy invites that can be shared via QR code, SMS or any other messenger. Example: https://yax.im/i/#user@example.com or https://conversations.im/i/user@example.com See also https://yaxim.org/blog/2020/01/31/yaxim-0-dot-9-9-fosdem-edi...
Compared to the number of GTalk users, a bunch of self-hosted users probably didn't count for much.
> and something like 99%+ of the federation traffic was inbound spam
I heard this too, not sure if it was the only reason.
Too bad Google doesn't know how to manage spam. Good thing they don't have any other federated communication products. /s
> Federated protocols aren't very good, and don't evolve.
What makes you say this? XMPP has come a long way since 1999 and is still evolving to this day. Even email is slowly evolving. Is Matrix not evolving? HTTP isn't really federated, but Moxie also mentions the web being stuck on HTTP/1.1, because HTTP/2 and HTTP/3 don't exist.