Add a setting to allow cleartext password transmission #8
Comments
tarsius
pushed a commit
to emacsmirror/jabber
that referenced
this issue
Aug 6, 2023
This was a non trivial merge. There were 311 conflicts to resolve. We would have saved ourselves considerable effort if the branch mentioned in issue legoscia#8 had been merged much earlier. Many of the conflicts were indications of duplicated effort. But that said, the conflicts were not difficult to resolve. In resolving conflicts, we prefer the nongnu-lexbind implementation, though not in every case. In particular we draw from nongnu-lexbind: - Comment style updates - Indentation adjustments - Single quotes in docstring corrections - Prefer pcase over cl-case - Prefer pcase-let over cl-destructuring-bind - Prefer nth over cl-first, cl-second, etc. - Avoid quoting lambdas - Drop :group specification in defcustom forms - In context where a function is expected, prefer function over symbol quoting ("#'" vs "'") - quash vestigial dynamic binding forms We have diverged and preferred the current implementation in the following situation: - Rework of `require' forms to quell warnings from the byte-compiler while avoiding circular dependencies - Sentence terminators (periods) in docstrings - Unused lexical arguments are deleted rather than commented out
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Unfortunately even in 2015 some servers do not support password encryption.
I came across this thread, which provided a patch to create an option for allowing the transmission of cleartext passwords. That will prevent emacs-jabber from asking this question over and over again:
Jabber server only allows cleartext password transmission! Continue?Do you think that is something worth merging?
The text was updated successfully, but these errors were encountered: