SimonSomeone threw up XEP 280 onto hacker news this morning https://news.ycombinator.com/
KevI don't think your comment is entirely accurate, is it?
KevThe power cost of 'holding open a socket' is 0, in isolation.
KevIt's the traffic that costs you.
KevBut I read your comment as generally saying "Yes, Carbons is there, but it's rubbish", which doesn't seem helpful.
SimonKev: don't know what gave you that impression. I read it as being very much go Carbons!
KevIt was the "More background: XMPP is designed around keeping a connection open to the client and pushing through updates and new messages. These assumptions worked well in a desktop environment on a solid TCP connection. But for power, intermittent network, and mobile OS design reason, holding open a socket isn't ideal." line, before pushing Push. It does mention carbons, but I'm not sure that carbons actually does what you say it does :)
Simon" are working hard to make XMPP more mobile friendly." then explaining the background.
Simonof course I could have started with carbons + push + mam are pieces of the mobile puzzle.
SimonMy point is it's nice to see people posting XMPP related topics to HN.
Tobiason the latest comment there ( https://news.ycombinator.com/item?id=7367920 ): it'd probably useful to have an informational XEP how to best detect the active client among logged in resources so that a) after receiving 10 messages and sending an answer from one resource the notification on the other clients are cleared and b) you're only notified about new messages at the client you're at. both facebook and hangouts fail at that making all devices ring on a new message (sometimes heavily delayed)
KevWe discussed this at the summit.
KevThere's a spin-off from the Push stuff to cope with this.
ralphmMaybe those tables should show server versions.
KevIt seems useful, potentially.
Leonidas Ihas joined
KevZash: I've just noticed that further up that page there's a list of auth mechs. Including SCREAM-SHA-1, which is offered by one server :D