Active Topics

 


Reply
Thread Tools
Posts: 1,096 | Thanked: 760 times | Joined on Dec 2008
#1
I know some of you in here probably run your own jabber servers, and I was just curious about feedback on this issue.

As network and sysadmin, I like the control for my own users using transports, but it seems like for end users it is all just multiprotocol clients.

I wish some of the bigger networks would install some transports to xmpp-ize more people.

what do you run?

opinions, comments, argument, flames?
 
Posts: 5 | Thanked: 3 times | Joined on Mar 2010 @ San Jose CA, USA
#2
This is what I like:
As a server - Openfire: http://www.igniterealtime.org/projects/openfire/
As a client - Spark (from openfire site).
On N900 just the regular Jabber client will do.
 
Posts: 543 | Thanked: 181 times | Joined on Aug 2009 @ Universe,LocalCluster.MilkyWay.Sol.Earth.Europe.Slovenia.Ljubljana
#3
ejabberd - though planing on migrating to prosody
pymsnt and pyicqt and I used jmc(mail in jabber but it has bugs) as well and I have a j2j(jabber2jabber connect to a different jabber from the current jabber transport standing by(not sure I used that yet)(and I only really use pyMSNt now and even that just to be in contact with people that don't want to switch)

For the clients: N900 standard and bitlbee.

I'm a strong believer in transports and not multi protocol clients.

Reasons:
Not all protocols support connecting from multiple clients at the same time
Not all protocols support server side offline messaging
Not all protocols support encrypted connections

And probably the biggest XMPP is an open protocol.
__________________
For any repos or anything else I might have working on my N900 see:
http://wiki.maemo.org/User:Ruskie
A quick list of what I have in the repos
zsh|xmms2|fcron|gtar|gcoreutils
 
Reply


 
Forum Jump


All times are GMT. The time now is 03:19.