Ayttm

Are You Talking To Me?

"Are you talking to me?" or "Ay-wai-tee-tee-em" or "item" - the choice is yours, as long as your audience gets the reference right :-)

Primary difference - and the reason many people choose Ayttm (and EveryBuddy before it) over others - is that we treat a person as the basic buddy entity, while others treat each account as the basic buddy entity. We feel it's more natural to think of a person as, well, a person, rather than a bunch of accounts on different services - which non-geeks don't care about, and seldom understand for that matter.

As a result of this, comes our second major point - automatic fallbacks. If a service fails while you're in the middle of a conversation, say, the MSN server goes down for maintenance, Ayttm will automatically switch to the next available service. In the extreme case, this could go all the way to mailing/smsing the contact (yeah, I [Philip]'ve done that).

No one in the (little) development team uses these protocols, so our interest in fixing them is not much. It takes some time to document ourselves, understand the module source code, go into fix/debug/fix/debug loop and so on.
If you really are interested in these protocols and are a developer, patches are welcome.
AIM, still, is supported via AIM-toc module, and ICQ works using ICQ-toc module.

The sender of the file should have a public IP and allow incoming connections to TCP port 6891.

See GnomeMeeting's quite extensive FAQ on the subject.

This is so because Ayttm is a gtk1 application. Give a look at your LANG and LC_ALL environment variables, and if they contain something about UTF, try running ayttm after removing these parts. On Redhat 8 & 9 systems, you can fix it in /etc/sysconfig/i18n too.

Smileys work, but only after your conversation has started. This is so because until you actually start chatting, there's no way to know which service you're using, and therefore, which smileys to use.

Ayttm uses the HTTP CONNECT method to get through HTTP Proxies. This message from Arun Shrimali (India) explains what to do:

find the following line in squid.conf
#http_access deny CONNECT !SSL_ports

replace it with
http_access allow CONNECT !SSL_ports

But, probably it will open all the secure ports. I am trying to find out another solution also.

Regards

Arun

Savannah had too many recurrent problems. Project CVS did not work (update or commit sometimes impossible for hours), HTML CVS did not work (auto-update broken for weeks), Mailing-lists did not work (disappearing messages and long delays).

Um, there's just this one that a local artist drew for me (Philip) during the Kala Ghoda Art Festival.