XSF Discussion - 2014-03-02

https://twitter.com/ade_oshineye/status/439869042783174656

It appears we need to do a better job at explaining when people like Adewale keep spreading misinformation.

Gnrf

I note that he links to an "Android not really XMPP" thread in which Google say that if only XMPP had resumption and EXI, it'd have been great.

I also wonder if, six years later, it's possible that the expense of zlib vs radio on a phone processor isn't the same as it used to be.

ralphm: Hopefully this satisfies your requirement of explaining stuff: https://plus.google.com/+AdeOshineye/posts/YbsTNU43rV9

Kev: that's pretty good indeed.

Kev: I've been thinking, for a while, that I wanted to do a series of blog posts on XMPP myths.

I wouldn't frame it in that way.

yeah...a XMPP Mythbuster show :D

But yes, I was thinking that a blog post about how to use XMPP in ways that myth says it doesn't work would be good.

There are many such misconceptions as I discovered over last few weeks, following Twitter mentions of XMPP.

I'm open to suggestions for positive framing.

The other side is that this Twitter stalking of yours may help us work out areas we need to improve :)

my biggests wishes: 1. good, pretty, native and energy efficient XMPP client with MUC support on every mobile platform. 2. working file transfer based on Jingle. 3. E2e encryption beyond OTR.

I'm also excited about the push stuff

ralphm: i'll hopefully have a chance to look closer at datachannels + jingle filetransfer soon

where 'datachannels' really doesn't have anything to do with webrtc except for using the same protocols for data transfer over udp, right?

fippo: ^