Configure your IM client for Twitter
You can chat with online friends (bidirectional follow relationship). You don’t post tweet, you directly send message to you friend without publishing it somewhere.
Treegger does not store any data, credentials or messages, all contents just transit between you and our servers using secure connection (TLS).
As twitter does not provide digest authentication feature, you should send your login/pass in plain text using SSL/TLS connection.
Don’t worry we never store any password and nobody can access to them as the connection always remains secure.
A problem? A suggestion? Send us some feedback, we’ll do our best to help you.
Any XMPP Client
For any XMPP client software you should use following setup:
Jabber ID: [your twitter account name]@twitter (for example ‘jchasetg@twitter’)
Connect Server: xmpp.treegger.com with port 5223
Allow plaintext authentication (twitter doesn’t provide any other authentication method yet)
SSL/TLS (old style) required and selected
Configuration is exactly the same as Google Talk except:
Screen name: use your Twitter name (here jchasetg)
In advanced tab, enter ‘xmpp.treegger.com’ in the Connect Server box (be sure that server is still ‘twitter’ in the previous tab)
Create a new Jabber account.
Set the user name (here jchasetg), and the password. You can’t set the server here (you have to go to the ‘Configuration’ panel by clicking on the icon on the bottom left).
Create Jabber account, use same configuration as any XMPP client and use in option panel xmpp.treegger.com port 5223 with plaintext, old style SSL and required SSL/TLS checked.
Configuration is exactly the same as Google Talk
Just replace server “talk.google.com” by “xmpp.treegger.com” and use [your twitter account name]@twitter (for example jchasetg@twitter) as Jabber ID and use your twitter account password.
On account property window, select connection panel. Manually specify server host/port set to xmpp.treegger.com/5223, select ‘Legacy SSL’ in the combobox and allow plaintext authentication ‘over encrypted connection’.