|
Size: 4432
Comment:
|
Size: 3343
Comment: Fix typo
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| = Fellowship XMPP server = | ## page was renamed from TechDoku/XMPP ## page was renamed from Migrated/XMPP = FSFE XMPP server = |
| Line 3: | Line 5: |
| Each Fellow has an account on our public [[http://en.wikipedia.org/wiki/Xmpp|XMPP]] (formerly known as "jabber") server for instant messaging. | Each FSFE supporter and volunteer has an account on our public [[http://en.wikipedia.org/wiki/Xmpp|XMPP]] (formerly known as "jabber") server for instant messaging. |
| Line 9: | Line 11: |
| * [[http://gajim.org/|Gajim]] | [[http://gajim.org/|Gajim]] | [[http://kopete.kde.org/|Kopete]] | [[http://pidgin.im/|Pidgin]] | [[http://psi-im.org/|Psi]] | [[http://live.gnome.org/Empathy|Empathy]] | [[http://adium.im|Adium]] [[http://www.kadu.im/w/English:Main_Page|Kadu]] | [[https://jitsi.org/|Jitsi]] | [[http://salut-a-toi.org|Salut à Toi]] | [[https://conversations.im|Conversations]] (Android) |
| Line 11: | Line 14: |
| * [[http://kopete.kde.org/|Kopete]] | or any other :-) |
| Line 13: | Line 16: |
| * [[http://pidgin.im/|Pidgin]] * [[http://psi-im.org/|Psi]] * [[http://live.gnome.org/Empathy|Empathy]] * [[http://adium.im|Adium]] * [[http://www.bitlbee.org|Bitlbee]] and any IRC client. * ... add your Free Software XMPP client here |
|
| Line 27: | Line 19: |
| * Username: your usual Fellowship username * Domain: `jabber.fsfe.org` (so your complete jabber account will be: `USERNAME@jabber.fsfe.org`) |
* Username: your usual FSFE username * Domain: `fsfe.org` (so your complete jabber account will be: `USERNAME@fsfe.org`) |
| Line 30: | Line 22: |
| * Password: your usual Fellowship password * Jabber server: `jabber.fsfe.org` |
* Password: your usual FSFE password * Jabber server: `jabber.fsfe.org` (In practice you might not need to specify this) |
| Line 33: | Line 25: |
| * Port: you can use the standard XMPP port 5222, or the (deprecated) port 5223; if you are behind a blocking firewall/proxy, you can also use port 80 or 443 (the latter is more likely to work, since some ISPs filter traffic on port 80). In any case, the server will enforce a secure SSL/TLS connection. | * Port: you can use the standard XMPP port 5222; if you are behind a blocking firewall/proxy, you can also use the BOSH proxy on port 80 or 443 [[http://xmpp.org/extensions/xep-0124.html]], which can be found under the proxy settings in gajim for example |
| Line 43: | Line 35: |
| = Contacting other Fellows = | = Contacting other users = |
| Line 45: | Line 37: |
| To find other Fellows, you can either check their login on the Fellow listing at http://wiki.fsfe.org/fellows and try to contact them directly at `USERNAME@jabber.fsfe.org`, or use the Jabber User Directory on the server. | To find other users, you can try to contact them directly at `USERNAME@jabber.fsfe.org` OR `USERNAME@fsfe.org`. Unfortunately, both work, but they are practically different accounts, so if someone is using `USERNAME@jabber.fsfe.org` and you try to add them as `USERNAME@fsfe.org` they will not find you. |
| Line 47: | Line 39: |
| The Jabber User Directory is located at `vjud.jabber.fsfe.org` and you can use it to register yourself (so others can find you) and look for other Fellows on the server. Please see the documentation of your Jabber client on how to use this service. | = Chat rooms = |
| Line 49: | Line 41: |
| = Chat conferences = | There's a chat room for our volunteers and supporters available through our XMPP server: |
| Line 51: | Line 43: |
| If you wish to talk with others, there is also a multi user chat (MUC) server at `conference.jabber.fsfe.org` on which you can join existing chat rooms or open new ones for you and other Fellows. The `fellowship` chat room is a general meeting point for all Fellows, so feel free to join it! == Notes for specific clients == * '''Kopete''' MUCs are available as "group chats" only from the context menu for an account; use the right mouse button on the systray icon, pick an account and choose "Join Groupchat...". Do not attempt to add a group chat as a contact, since that will just get you loads of domain-not-found errors. * '''Bitlbee''' MUCs are available as "chat room". You should add a chat entry with {{{ chat add N fellowship@conference.jabber.fsfe.org fellowship }}} where ''N'' is the account number for you connection to jabber.fsfe.org. Then you can join the conference room by {{{ /join &fellowship }}} * '''Pidgin''' MUCs: Join via 'Buddies' -> 'Join a chat'. If you right-click the channel in your budyy list, you can make it 'Persistent' and 'Auto-Join'. These enable you to close the chat window without leaving the channel and to auto-join the channel when starting up / connecting the client. |
[[xmpp:community@conference.jabber.fsfe.org?join|community@conference.jabber.fsfe.org]] |
| Line 71: | Line 46: |
| If you have problems with your Jabber account, you can contact <<MailTo(fellowship-hackers AT fsfeurope DOT org)>> | If you have problems with your Jabber account, you can contact <<MailTo(contact AT fsfe DOT org)>> ---- Category/FellowshipServices |
FSFE XMPP server
Each FSFE supporter and volunteer has an account on our public XMPP (formerly known as "jabber") server for instant messaging.
Connecting to the server
In order to use the Jabber service, you will need a Jabber client, such as:
Gajim | Kopete | Pidgin | Psi | Empathy | Adium
Kadu | Jitsi | Salut à Toi | Conversations (Android)
or any other 
Configuration is simple:
- Username: your usual FSFE username
Domain: fsfe.org (so your complete jabber account will be: USERNAME@fsfe.org)
- Password: your usual FSFE password
Jabber server: jabber.fsfe.org (In practice you might not need to specify this)
Port: you can use the standard XMPP port 5222; if you are behind a blocking firewall/proxy, you can also use the BOSH proxy on port 80 or 443 http://xmpp.org/extensions/xep-0124.html, which can be found under the proxy settings in gajim for example
Notes for specific clients
Kopete When creating the account in Kopete, switch to the "connection" tab in the settings and check "Use protocol encryption (SSL)" and also make sure that "Allow plain-text password authentication" is enabled. The default server information should be ok. Cut-and-paste into the configuration dialog seems to be problematic: type the server name and your password by hand (and double check this if you are getting "host not found" errors).
Pidgin If you have problems with upgrading to versions > 2.6, it might be unavoidable to delete the account in pidgin and recreate it.
Pidgin + GnuTLS: SSL certificate problem Some users reported SSL connection problems while using Pidgin with the GnuTLS library (you can learn something more about this problem here and here). To fix this, you can manually add the jabber.fsfe.org SSL certificate to your pidgin client, as suggested in this blog post; note that downloading the server certificate directly from the jabber server using the "openssl" command won't work, instead you can download the certificate here: jabber.fsfe.org.pem
Contacting other users
To find other users, you can try to contact them directly at USERNAME@jabber.fsfe.org OR USERNAME@fsfe.org. Unfortunately, both work, but they are practically different accounts, so if someone is using USERNAME@jabber.fsfe.org and you try to add them as USERNAME@fsfe.org they will not find you.
Chat rooms
There's a chat room for our volunteers and supporters available through our XMPP server:
community@conference.jabber.fsfe.org
If you have problems with your Jabber account, you can contact <contact AT fsfe DOT org>
Category/FellowshipServices