Evan Prodromou wrote:
Jeremy Slade wrote:
Any idea if desktop clients such as twitter will work with laconica over
https?
That makes absolutely no sense.
Indeed -- meant to say: Any idea if desktop clients such as twhirl will
work with laconica over https?
Many API clients will use SSL; Gwibber insists on using SSL for the
API, which is just a terrible bug.
The easy way to implement this (as in the patch) is to force https for
everything, but that is overkill. What would a client have to know/do
to use SSL for some methods (authorization) and normal HTTP for
everything else?
_______________________________________________
Laconica-dev mailing list
[email protected]
http://mail.laconi.ca/mailman/listinfo/laconica-dev
