[Freedombox-discuss] Plinth v0.13.1 released

[Petter Reinholdtsen]

[Jonas Smedegaard]
> The recent blog posts are essentially about configuring a Jabber server 
> to support the features of the Android-based Jabber client 
> Conversations.

Yes, but it is also about configuring a Jabber server to have several
recommended extentions to support multiple devices and encrypted (group)
chat, which is not really about Conversations at all.  And the key
information I took away was the recommendation found in <URL:
http://rtcquickstart.org/guide/multi/xmpp-server-choice.html >:

  It is recommended that you use the Prosody XMPP server. It is widely
  used and relatively easy to configure. Latest releases of Prosody are
  being made available as packages on the major Linux distributions.

The next sentence regarding server choice is this, supporting your
suggestion:

  You can also use ejabberd, jabberd2 or another server if you prefer.

> Such configuration is possible to do with both Ejabberd and Prosody,
> so I fail to see the reason for switching based on that.  Makes sense
> to identify the comparable changes needed for Ejabberd and apply
> those.

OK.  Do you know of a recipe and if the set of required extentions to
ejabberd is included in Debian?

> I believe the debian.org Jabber server runs Prosody, and you point out
> that that setup is known to have problems handling spim.  Possibly
> Ejabberd has similar problems (I have run a couple of ejabberd systems
> for several years without experiencing a single spim but that might
> simply be because I am not as exciting a target as debian.org). I fail
> to see the reason for switching to a server known to have issues with
> spim.

Unless ejabberd reject federation (unlikely), I see no reason why we
should believe it is less affected by spim than prosody.

Using the same server as debian.org and being able to share experience
and setup with the server on debian.org seem like a fairly big advantage
to me.

-- 
Happy hacking
Petter Reinholdtsen