Skip to content
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

Investigate the implications of 964070 #87

Open
arlolra opened this issue Aug 19, 2016 · 1 comment
Open

Investigate the implications of 964070 #87

arlolra opened this issue Aug 19, 2016 · 1 comment
Assignees
Labels

Comments

@arlolra
Copy link
Owner

arlolra commented Aug 19, 2016

@aleth suggests we have a look at 964070 and see how it interacts with OTR, and whether to recommend a different default value for the pref.

/cc @azadi

@arlolra arlolra self-assigned this Aug 23, 2016
@arlolra
Copy link
Owner Author

arlolra commented Aug 31, 2017

The patch just adds another call to writeMessage(), which is the correct method for the transformation pipeline, so no problems there.

As xnyhps says, instance tag support should help with OTR messages ending up at the wrong device. See #45 for that.

However, as the XEP suggests, it might be nice to add an API in IB to append <private/> and <no-copy/> elements to <message/>s in an OTR session.

It's probably ok to leave this enabled by default as it stands, though there's the potential for some poor interactions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant