[jdev] Re: ejabberd vs. Wildfire

[Daniel Henninger]

On Jan 21, 2006, at 2:28 PM, Mickael Remond wrote:

> * Remko Troncon <remko at psi-im.org> [2006-01-21 19:46:40 +0100]:
>
>> On 21 Jan 2006, at 19:23, Yves Goergen wrote:
>>
>>> I've seen that Wildfire doesn't support
>>> Privacy Lists, but as no client supports them as well (especially  
>>> Psi
>>> that I use), that isn't a too big deal
>>
>> Actually, that is a pretty big deal IMHO, since it is required by
>> XMPP. Even if no client implements it, many people just set a privacy
>> list using XML, since this is an operation that you don't need to do
>> often. It's a lot worse that clients won't be able to assume that
>> privacy lists are implemented on every modern server (for e.g.
>> invisibility), than to have no clients using it yet.
>
> As Remko says, ejabberd 1.0.0 is an XMPP compliant server.
> It also has a lot of nice module included such as good (but not yet
> totally complete) pubsub support.
> Depending on the load you are planning, ejabberd might make a big
> difference as it scale very well and is used in production system  
> to run
> really large installation. ejabberd is also very stable.
>
> Regarding the web interface, improvements are planned for ejabberd and
> in the short term, we hope to have something very nice to give you.


While I do find WildFire's web interface prettier, the only real  
thing about it that I really -use- that ejabberd's doesn't have is  
the ability to see a user list, maybe muck with their accounts a tad,  
and most importantly add a new user.  I know the command like tool  
can do that, but still.  That's definitely something I'd like to see  
appear in the web interface.  =)

Daniel