Future plans for Yeemp

Baiting the vapourware wraiths...

(This list current as of August 29 2003 and Yeemp 0.8.)

The most obvious (IMO) thing in Yeemp that needs fixing can be seen in the features list - it says "mostly decentralized". That should be changed to "decentralized" - the trouble is, the default domain name resolvers on most systems wind up going through the thirteen root servers. Which are, as near as I can tell, the inheritors of the old ARPAnet, under control of a handful of large corporations and governments. I've been toying with a decentralized name-resolution protocol, but haven't gotten anywhere near finished with it.

Under Linux, Yeemp can run the SSL shoggoth inside a Subterfugue sandbox. Other apps invoked by Yeemp (gpg, pngtoppm, and so forth) should also be run in sandboxes.

Every so often, someone asks "Does Yeemp do (Yahoo, MSN, Jabber, AIM, ICQ, etc).". The answer should probably be "yes" for more than just ICQ and AIM.

The ICQ plugin should be a shoggoth.

There's still an assortment of rough edges, though fewer than there were.

The current protocol takes rather longer than I like to deliver messages.

The protocol could use more traffic analysis countermeasures.

It could also use more default media, especially sounds.

Those trapped on non-unix OSes should be able to use a Yeemp client.

If you want to help with any of this (or, for that matter, anything else. Especially reporting bugs), contact me.