Automatically initiate otr session if peer uses otr

[dtto]

Current usage: Requires user to explicitly type /otr init in a /msg window to start otr.

Better: otr looks to see if uid uses otr, and if so, automatically initiates.

Possible options: Only initiate for trusted FP.

[Tronic]

What would be a good way to do this without interference, CTCP perhaps? Another related issue is re-initializing the session after one of the users has disconnected. Currently irssi-otr doesn't handle this automatically and requires /otr finish /otr init to fix the connection.

[dgoulet]

What I was thinking about is to support something like "/otr init ". Which opens up a msg window with the user and automatically initiate otr. Thoughts?

On the re-init issue, if the other side sends a finish message, you should not try to re-init the OTR. It should be possible to make /otr init a bit more intelligent and automatically finish the current session if it's in the finish state.

[dtto]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

David Goulet:

What I was thinking about is to support something like "/otr
init ". Which opens up a msg window with the user and
automatically initiate otr. Thoughts?

That sounds good, but why make otr dependent on the user
remembering the right command? I will freely admit that I am not a
coder, and I understand it may be more difficult to make it
automatically initiate otr when a user uses /msg instead of /otr
init. But the best tool is one that will protect the user from
their own ignorance of the correct commands. :)

Thanks for this plugin, it is awesome!

• -devin
  -----BEGIN PGP SIGNATURE-----

iQJ8BAEBCgBmBQJTmiezXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ0ODQ5N0M5QjU5NzFENDQ5MUZEOTZDNTdE
NDU1MjM2NzZFRDYxMEI3AAoJENRVI2du1hC3F0AP/2ki22dL7z49KiiiHVoTWQ4v
O4P22TveK1yxdTkSxB3RhV9PljoxVLZ4RiwarYwgokN12+MHWhyJv4WY4gdkaoWR
bQf2A2rofaypGWv9QNso2LHKO1n4PmLTeC+SrSfFcPnUq+8wOIg4FKhou879SJwE
gxgUm8/DBDdqlE/4/H2XSq+rAfYqaTDqbVwkEmxyxop/3/KpR1Ivq+QOgujM6Hha
Q/76BKAZco+yt49pPUjiApNk9RhYkdImM/++2QuI2F3isFSknl8B4p4Rc51Osp5Z
14X+g/jOkmTVaeb4FhsxlPH2gpde/33xcuslUYik/GFXAkx1dYLQQadim+c+xuvu
rQUwI8/vEchHyNVIrxvSUsjX7qo9NAYoXWOaPsg8CNWm2zJs9pTSDpilJOLTTbeo
MM6PrDDEk18EWoWNbop6sGaJr/wG50sQBHZ7+j18+a6y9517EOydPg+8VNQJj5hW
2ign9k4aVumxhy4nv0lyQ6pX0dvTivmzbKE1Uu4egE2tw10fm0vpU24p9tiVI1wI
w1byaGsq7Ce+o4at2tul/Fy/mlFYmcWTk3EFreCu2Fz0BWBgCc104XhzuNGBHdmd
K3ZQo8EOJ29y2WVQIh3NggZAQNg2kYOnnXqbkeR3AAkGblFjPCBVB0QwLvrs2YGa
HjcFV70V2tTqCrxrTEfc
=CQ7O
-----END PGP SIGNATURE-----

[dgoulet]

True, that could be doable. This plugin used to have a way to control OTR policies that tells if OTR should be tried every time or just for those supporting it, I can give it a shot and have it at least opportunistic. :)

[geor-g]

Any update on this? This would be such a great feature...