[jdev] FOSDEM 2017 and XMPP Summit 21 dates

Marcel Waldvogel marcel.waldvogel at uni-konstanz.de
Thu Jul 28 07:36:01 UTC 2016

XMPP has three strengths: extensibility, vendor-independence, and
XMPP also has three weaknesses: extensibility (there is no clear "right
way"), vendor-independence (no big pusher [not even Cisco pushes it]),
and openness (there are many projects out there, but rarely a focus on
There are proposals to address the first weakness (e.g., [1][2]). The
second and third have been neglected for many years, but now several
are working on it (notably Conversations [3], but also Monal [4] or
ChatSecure [5]).
With the weaknesses taken care of, let's focus on the strengths: The
openness and vendor-independence allows us to create products that
extend the functionality of existing software. For example, JSXC [6]
provides a basis for add-ons to web applications. Plugins exist for
ownCloud/nextCloud (with an optional local XMPP server included, for
easy bootstrapping), the Ilias e-learning platform, the SOGo groupware,
or the Diaspora* OSN. These combinations allow you to chat while
collaboratively editing documents, discuss problems you have
understanding part of a lecture [7], or respond to an email via video
or text chat. That is added value we can leverage. And there are
probably other integration ideas out there, waiting to be implemented
with a few lines of code [8].
In many scenarios, the federation concept (a fourth advantage) comes
much more natural than in centralized approaches. This comes in as a
natural for Diaspora*. But it also allows for cross-institution
collaboration (very active in German research and education
institutions) while keeping the identity.
The use of multiple federated identities (maybe I should add a fifth
advantage?) also allows you to separate friends and family from work
and the rabbit breeding association or public office you are also
associated with. You can switch these identities on and off during
different parts of the day, something the centralized approaches which
typically enforce a single identity (the mobile phone number).
XMPP is far from dead, but as any standard, it needs to be pampered and
nourished and we daily need to breathe new life into it, continually
living and improving it with our ideas, hopes, and excitement.
[1] Daniel Gultsch: "The State of Mobile XMPP in 2016", 2016-06-02, htt
[2] Dave Cridland and Sam Whited: "XEP-0286: Mobile Considerations",
2015-07-24, http://xmpp.org/extensions/xep-0286.html
[3] https://conversations.im/
[4] https://monal.im/
[5] https://chatsecure.org/
[6] https://www.jsxc.org/
[7] Automatic MUC creation for every lecture coming soon.
[8] Klaus Herberth, Daniel Scharon, Matthias Fratz, Marcel Waldvogel:
"JSXC: Adding Encrypted Chat with 3 Lines of Code." In: NetSys 2015,
Gesellschaft für Informatik, 2015. https://netfuture.ch/2014/12/jsxc-ad
On Mit, 2016-07-27 at 18:28 -0300, 
> Maybe not directly related to what you expected to read in replies to
> this
> message, but I want to say a few things that I wish that XMPP had.
> I am desapointed with what I can do now with XMPP. Mobiles clients
> are not
> as good as clients for Telegram and Whatsapp. There are alternatives,
> which is good. But not as good when people are not using them because
> they
> do not give what similar programs already do well (or, if you
> analyse,
> just good enough), and they are popular. XMPP does not have something
> good
> for normal people wanting to use them. Talking with one or two
> people??
> That is what I offer to the very few friends whom accepted to use
> just because I use  it. But who else does??? That is missing. As I
> have
> said, the limitations of mobile clients compared with XMPP desktop
> clients
> are considerable, and sometimes they are just what I needed - in
> better
> words, they are just what someone who accepted it with my indication
> needed.
> I hope that something meaninful in these aspects come out of these
> encounters. Keep the list informed when it ends!
> Kind regards
> -=-=-=-=-= Certo dia, Ralph Meijer escreveu: =-=-=-=-=-
> > 
> > Hi all,
> > 
> > The FOSDEM organization has announced the dates for the 2017
> > edition:
> > Saturday 4 and Sunday 5 February. As usual, we will try to arrange
> > for
> > having another Realtime Lounge, as well as a devroom, as soon as
> > the
> > Call for Participation happens. Of course, you can already start
> > thinking about:
> > 
> >  * Your demo for the Realtime Lounge (if allocated). Anything
> > related to
> > XMPP or other open realtime protocols or technology goes. IoT stuff
> > is
> > always a great thing to show off something as abstract as
> > protocols.
> > 
> >  * Your talk, presentation, etc., for the devroom (if allocated).
> > 
> >  * Your main track or lightning talk.
> > 
> > 
> > Additionally, I am proud to announce that the XSF is once again
> > organizing an XMPP Summit, for the 21st time. The dates are
> > Thursday 2
> > and Friday 3 February.
> > 
> > Usually, we spend these days talking about XMPP protocols in
> > plenary
> > sessions. However, this year, we wanted to settle on the dates as
> > soon
> > as possible to have plenty of time to do other things. We could
> > have
> > parallel sessions, BoFs, (invited?) talks from people outside our
> > community, coding or interop sessions, you name it. In fact:
> > 
> >   You name it!
> > 
> > If you have any suggestions for things we could do at the XMPP
> > Summit,
> > let me know, or write them down on our shiny new wiki page:
> > 
> >   https://wiki.xmpp.org/web/Summit_21
> > 
> > Please also consider sponsoring the traditional XMPP Dinner, most
> > likely
> > on Thursday evening, or the XSF in general. You can contact me or
> > any
> > other Board member on this.
> > 
> > So, jot down the dates for FOSDEM and the XMPP Summit in your
> > calendar,
> > and sign up as participant at this wiki page, so we can look into
> > Hotel
> > discounts and generally prepare for another great Summit.
> > 
> > I hope to see a lot of you in Brussels, again.
> > 
> > --
> > Cheers,
> > 
> > ralphm
> > _______________________________________________
> > JDev mailing list
> > Info: http://mail.jabber.org/mailman/listinfo/jdev
> > Unsubscribe: JDev-unsubscribe at jabber.org
> > _______________________________________________
> > 
> _______________________________________________
> JDev mailing list
> Info: http://mail.jabber.org/mailman/listinfo/jdev
> Unsubscribe: JDev-unsubscribe at jabber.org
> _______________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/jdev/attachments/20160728/1353f2ac/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 6240 bytes
Desc: not available
URL: <http://mail.jabber.org/pipermail/jdev/attachments/20160728/1353f2ac/attachment-0001.bin>

More information about the JDev mailing list