[OTR-dev] daemon-only?

[Len Sassaman]

The first few versions of OTR-proxy were commandline-only. I actually
liked that better than this one -- very few people verify keys anyway, and
for warnings, you could always insert the warning message into the IM
itself as OTR does already.

(As for the UI sucking, I agree. I've had on my todo list a native Cocoa
app built with Interface Builder for the Mac, and something better then
wxWidgets for everything else, but, I'm busy. However, I can give pointers
from feedback from the HCI group here if anyone else wants to take this
on.)

The best fix would be to make OTR-proxy unnecessary, though. Lobbying the
chat client authors to include native OTR support as Adium as done would
be good. Trillian has expressed willingness (though it seems to be low
priority). I think all but AOL/Apple/Microsoft/Google could probably be
persuaded. (Which unfortunately still leaves a need for a good OTR-proxy.
I'll try to make that a higher priority.)


--Len.

On Wed, 6 Feb 2008, alex black wrote:

> hey all,
>
> is there a daemon-only version of otrproxy? I think it would be pretty
> easy to do this from the commandline, and then I wouldn't have to keep
> a window running all the time (which would reduce memory consumption..)
>
> any opinions?
>
> best,
>
> _alex
>
>
> --
> alex black, founder
> the turing studio, inc.
>
> 510.666.0074
> root at turingstudio.com
> http://www.turingstudio.com
>
> 800 jones street
> berkeley, ca 94710
>
>
>
> _______________________________________________
> OTR-dev mailing list
> OTR-dev at lists.cypherpunks.ca
> http://lists.cypherpunks.ca/mailman/listinfo/otr-dev
>

--Len.