XSF Discussion - 2014-02-24

tobias: thanks for info, sad it would have been a perfect to get more IoT done.

yeah...would have been interesting to get more IoT explosure

“Unfederated chat systems are a single point of failure. And not just technically. Consider centralized e-mail going down. #xmpp” – ralphm (https://twitter.com/ralphm/status/437897021693771777)

Maybe I should write a longer text on this.

But my feeling is that recent events, with DDoS attacks against WhatsApp and Telegram, but also jabber.org, highlight this.

realtime messaging all started with erlang?

http://blog.process-one.net/whatsapp-facebook-erlang-and-realtime-messaging-it-all-started-with-ejabberd/

Facebook uses Erlang for their messaging platform (but not ejabberd). WhatsApp uses FunXMPP for their server (but not ejabberd). And I'll take a sip of whatever the author of that post is drinking.

Simon: this is no longer true

https://twitter.com/mickael/status/437663361325883392

ralphm: I did some research on the Facebook claim. Not buying it.

Simon: which claim exactly? That ejabberd was the bases for Facebook's initial XMPP stuff (I think this is true) or that they no longer use Erlang (I trust Bob on this)

next its google talk using ejabberd (-:

I do agree with your stance on the hyperbole.

(i suspect they do java based on some tls bugs)

WhatApp definitely doesn't use Ejabberd https://github.com/ottolin/whatspoke/blob/master/doc/funxmpp.txt

Simon: what's being claimed is that WhatsApp was originally based on ejabberd and still probably is a highly modified version of it

Could well be - seems a rather tall claim imho.

https://pdincau.wordpress.com/tag/whatsapp/

Simon: ^

"Paolo - How long has Whatsapp been using Erlang? Did the company switch from a different language or did you decided to start the project in Erlang from the beginning? Eugene - WhatsApp server has started from ejabberd – famous open source Jabber server written in Erlang. It was originally chosen because of a group of reasons, including openness, great reviews by developers, ease of start and the promise of Erlang’s long term suitability for large communication system. We started from ejabberd and made just few extensions and changes to get WhatsApp service up and running. We have spent next few years re-writing and modifying quite a few parts of ejabberd, including switching from XMPP to internally developed protocol, restructuring the code base and redesigning some core components, and making lots of important modifications to Erlang VM to optimize server performance."

I stand corrected.

http://techcrunch.com/2014/02/24/messaging-giant-whatsapp-with-465m-users-will-add-voice-services-in-q2-of-this-year/

wonder how their mangled jingle looks like

:)

also: https://twitter.com/rikardstrid/status/437024405299150849

there is a new kid in town... http://tox.im/

nice UI. Looks a bit like oTalk

ralphm: they'll just use SOX :-)

Their crypto docs are still quite lacking.

the av part of tox looks like mediastreamer / linphone 12 years ago... :-)

"For more info on the nospam see: Spam Prevention (page does not exist)"

jitsi just got accepted for GSOC

great

emcho: Congrats.

Kev: thanks!

kev: basically that means emcho volunteers to do the same for the XSF next year, right?

We haven't had an issue with getting accepted yet in the years we've applied :)

XSF actually parented Jitsi in 2011

no 2012

I remember.

emcho: that's great news!

jitsi might even be the only project doing webrtc-related stuff

stpeter: yup, that's good news indeed :) ... especially since they started rejecting us a couple of years ago :)

heh