davecridland

7 ms·

1.
by davecridland 5y ago
XMPP is routinely used on HF radio and SATCOM networks field-deployed by militaries. It's deployed with channel compression (so the links themselves are compressed), but it routinely operates down to way way below mobile. In general, t
2.
by davecridland 8y ago
There's an awful lot of "why not?" here. Remember, this is an Experimental XEP. The XMPP Council saw no reason to actively block it, but that doesn't mean we're all mad keen that everyone should rush out and do it.
3.
by davecridland 9y ago
Nice write-up of it, though I disagree that you can (or should) "recover" from a database breach in that way. If you detect a database breach, it's likely considerably after the event, and you should enforce password changes
4.
by davecridland 10y ago
I'd really appreciate more detail, here.
5.
by davecridland 10y ago
And XMPP has always tried to be the email of IM. Similar model, address format, and so on. A sea of independent, autonomous domains openly connecting to each other.
6.
by davecridland 10y ago
Agreed, which is why XMPP does this.
7.
by davecridland 10y ago
Sure it is. https://xmpp.org/extensions/xep-0365.html
8.
by davecridland 10y ago
I don't buy this. XMPP uses no more than any other IM system, and much less than most. The military use it over HF links in theatre, for heaven's sake - this is not what you'd choose to be doing if the bandwidth was so high.
9.
by davecridland 10y ago
1) XML really isn't that bad. Honestly. It can be (and is) parsed fast, without any schemas at all. The only thing you need to define about your namespace is the URI you're using. XMPP is not SOAP. 2) Wrong. RFC 6122 explicitly pe
10.
by davecridland 10y ago
Matrix will hit exactly the same problem in a few years. The solution is certainly not to restart with a clean slate every few years and fucks to you if you wanted compatibility. That's Google's approach, where every few years t
11.
by davecridland 10y ago
Oh, okay - in that case I slouch corrected.
12.
by davecridland 10y ago
A device-global push protocol isn't entirely useless, since the device OS can wake all the clients at once if it needs to, synchronizing network activity. But I agree it's a significant overhead if you're able to just hold op
13.
by davecridland 11y ago
So either XMPP is bad because it hasn't changed for years and is therefore old, or else XMPP is bad because there's new replacements for stuff that didn't work so well. Honestly, there's some days I wonder if there'
14.
by davecridland 11y ago
What? Openfire has had XEP-0136 for literally years. I think a little over a decade, actually. It's only recently implemented XEP-0313.
15.
by davecridland 11y ago
Also a later version at http://www.stateslab.org/HowToWriteUnmaintainableCode-Green0... which includes that crazy offbeat language, JavaScript (which was, amusingly, my contribution).
16.
by davecridland 11y ago
Actually a mixture. Some shortcomings have vanished because while they're problems, they're solved problems. And adoption etc, too. I'd note that I was never against XMPP, though; I just don't see the need to pretend it&
17.
by davecridland 11y ago
The Holleriths (later IBM Tabulators) were also used extensively in Bletchley Park and the Heliopolis station as part of the technique for cracking Italian Air codes - explaining why there's one or two knocking about in the National Mu
18.
by davecridland 11y ago
Worth noting that two of the people fairly heavily quoted on the shortcomings of XMPP both serve on the XMPP technical Council at the moment. (One of them is me, the other is Philipp Hancke).
19.
by davecridland 11y ago
Thanks for picking up on the important content there. ;-) If you want to be pedantic, Merlin - assuming he existed in the most likely timeframe - probably was aware of Angleland to his east, and would have been defending against its encroac
20.
by davecridland 11y ago
Really? The old Google Talk service used to do this, but I didn't think ejabberd did. There's a bunch of non-IM use-cases which need presence-less messaging.
21.
by davecridland 11y ago
You might want to read it. :-) The problem has mostly been that nobody's come up with a better JSON representation than one in a April 1st XEP (and they have been proposed - as ralphm says, they're mostly XML-with-curly-brackets,
22.
by davecridland 11y ago
You'll be glad that someone got the IMAP reference... (Unless you're as niche as I, and were referring to ACAP).
23.
by davecridland 11y ago
> I don't know how accurate Android's power estimates are, but I consistently have people telling me that they are switching back to proprietary messengers because every XMPP client they've tried drained their battery. Wha
24.
by davecridland 11y ago
I use Gajim on Linux and Conversations on Android, but the technology you're looking for is "XEP-0280: Message Carbons".
25.
by davecridland 11y ago
FWIW, I added the following to the Wiki page when I saw it was on HN, which might help give some context to what you're reading: Hi. I'm Dave Cridland. There's a note just up there which says "(Draft blog post)", an
26.
by davecridland 11y ago
The specific claims I was responding to when writing this (and it's still a draft) were an HTTP-based JSON protocol whose FAQ makes all these claims and more. And yeah, I think it's dumb to do things that way (both JSON/HTTP
27.
by davecridland 11y ago
http://matrix.org/docs/spec/#identity """ Users in Matrix are identified via their matrix user ID (MXID). However, existing 3rd party ID namespaces can also be used in order to identify Matrix users
28.
by davecridland 11y ago
OK, so your website claims that identity mapping is an integral key feature, so if I'm spreading FUD I apologise for repeating what's on your website. As to whether XMPP and Matrix are competitors, you make direct comparisons betw
29.
by davecridland 11y ago
Matrix do have a much bigger marketing budget than the XSF, it's true. They fly their employees all over the globe, and appear to have a constant stream of FUD on tap about XMPP, presumably because it's their strongest competitor.