Nicholas Merrill <[email protected]> writes: > On 1/31/14, 2:54 PM, Nicolás Reynolds wrote: >> Nicolás Reynolds <[email protected]> writes: >> >>> i suggested the idea of otr requirement to prosody devs :) >> in case the attached email wasn't clear, one of the prosody devs replied >> with this snippet for testing: >> >> https://prosody.im/pastebin/eed63406-cd84-4ee0-a550-94c9f69a73b2 >> >> > > Thank you, Nicolás for making that suggestion! > > I am running the code now - it technically works, in that it doesn't > allow non-OTR messages through. > > But the problem at the moment is that if you try to send non-OTR > messages, the error message is not popping up, at least in my testing, > on any XMPP client I have tried. The server basically silently drops > the unencrypted message without notifying the user. So for it to be > really more useful that needs to be sorted out. > > I have tested with Pidgin, Adium and ChatSecure (on Android)
i had to do a minor modification because the origin variable wasn't defined, but it's true, in the pidgin xmpp console i see the error coming but it isn't handled by the client. is there a kind of error that's regularly processed by clients? should the server reply with a regular message (impersonating the other party?), kind of the regular otr message "this person wants to communicate with you using otr..." http://kiwwwi.com.ar/pastes/mod_require_otr.lua.html -- http://partidopirata.com.ar
-- Liberationtech is public & archives are searchable on Google. Violations of list guidelines will get you moderated: https://mailman.stanford.edu/mailman/listinfo/liberationtech. Unsubscribe, change to digest, or change password by emailing moderator at [email protected].
