3 ms·
Wave, in a lot of ways, is just a XMPP client/aggregator. I don't mean that in a condescending way, it's very cool, but it's hardly "the first truly revolutiona
by btn 17y ago
Wave, in a lot of ways, is just a XMPP client/aggregator. I don't mean that in a condescending way, it's very cool, but it's hardly "the first truly revolutionary leap since HTTP itself".
The article says that this revolution hinges on XMPP letting you "talk directly to ANYTHING, and ANYONE", but that's just false (it's decentralised but not peer-to-peer) and hardly "HUGE": SMTP is such a protocol where "Social networks and proprietary transports no longer have an exclusive license to deliver content", it's just too old and crusty for us to slap some buzzwords on it and claim that "it can easily turn into a bona-fide platform for next-generation applications".
- zby 17y agoXMPP is only the connection part of the Wave - the other, if not more complex then at least much less understood part, is http://www.waveprotocol.org/whitepapers/operational-transform http://www.waveprotocol.org/whitepapers/operational-transfor... which is a theory about how to change a document according to concurrent editing commands streams. The idea is that using a special document structure and operations you can emulate the interface of any communication application (in email that document is a thread of conversation with rules allowing people append new 'emails', irc channels can be similarly represented with the document being the channel 'screen', you can even represent a chess game as a series of editing of the chess board). This generality let's you mix and match freely the communication modes used in different communication tools (like wiki and im etc).