The Yeemp instant messaging protocol is mostly decentralized. It does, however, still rely on DNS tolocate servers. Yeemp addresses are in the form user~machine.

Yeemp messages are encrypted using GPG and transmitted to the server through SSL; the only informationabout a message that the server should receive is the recipient, the ciphertext, and the expiry (whichis used so that servers don’t have to keep status messages sitting around forever.) They also windup able to see a copy of your first receiving key during IKE; this could be exploited by a maliciousserver to perform a man-in-the-middle attack. Yeemp does not use SSL certification authorities (as I don’t trust Verisign as far as I can throw them), and does not use the PGP “Web of Trust” model. I recommend exchanging key fingerprints out-of-band for verification.

Status notifications are handled by the client. The client-to-server protocol supports accountcreation, message delivery, receipt of queued messages, and notification when new messages arrive.

The clients can send files and supply customizable per-contact status icons and message sounds.The X client has rudimentary webcam support.

Yeemp messages are plain UTF-8 text.

The default client, also called Yeemp, is also capable of sending messages using the AIM and ICQ protocols.Additional IM protocol plugins can be written in Perl.

Main download site:

The majority of Yeemp is licensed under the GPL. Part of the server falls under the intersection of the GPLand the Net::SSLeay Documentation License.

– Deekoo

TakeDown.NET -> “Yeemp