-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
start session on query? #118
Comments
I think you are looking for Another good one, but not wanted in this case is |
ah ok, but this doesn't let you talk with people who doesn't have otr, so i guess i'm asking for something in between require_encryption and send_tag :P |
send_tag should start a session automatically on /query if the other party has OTR. How would this be different from send_tag? |
Doesn't send_tag send the first message without OTR but ending to the whitespace tag which then makes the OTR-supporting recepient initate OTR? |
send_tag will send all messages with the whitespace tags (including the first message) until it receives an untagged plaintext message in response. |
And what is asked here if I understand correctly is always starting query with the person automatically encrypting all messages. |
Of course you can send "?OTR?" on every query. However, with One possible feature might be to automatically set |
I'm ok with enabling require_encryption for contacts with past otr sessions :) |
It seems like the The only drawback I can see is that the first message is sent in the clear but as @tribut said you can be aware of that and only send something like "hi". @fauno is this your main objection to using |
you have to send "hi" and wait a few secs. i've seen many people starting to talk before the session is set (using otr in other plugins i admit). as i suggested in #48 plain text messages should be queued, not sent in plain text or dropped. currently instead of "hi" i'm running
in this case i'll use |
would it be ok to put up a hook running /otr start on /query? so if the other end is known to have otr the private chat is encrypted by default.
The text was updated successfully, but these errors were encountered: