The Tuntox Proxy buffer is mostly useful to those who know about the low-level operation of crdt.el. So, instead of always opening that process buffer when it is created, leave the process buffer in the background and use process filters to post more user-friendly notifications about tuntox connection status to Messages.
I'm not that familiar with process filters, but I saw that overriding the default filter causes the buffer to no longer get updated by default, so I copied the way the crdt-connect tuntox filter writes to the process buffer into crdt-new-session as well.
Co-authored-by: @artenator
Jonathan Ming (a8c1874a) at 17 Nov 00:34
Instead of opening tuntox buffer, use messages
Hi there,
@artenator and I have also run into this bug, and we were able to capture the logs you requested!
In our test, @artenator was the host and I was the client. Near the end of our test, my buffer looked like this (blue circle edited in for emphasis):
But the host's version of the buffer said "how are you" correctly instead of "hoaw re you" like my client showed.
Here are our logs captured using your instructions above:
For reference we are both using:
crdt-use-tuntox
enabledI thought we were both on latest crdt.el, but it turns out that @artenator was actually on 1897d623 while I was on 480f60fd. Looking at the diff, I don't see any real elisp changes between those commits though so I think it should still be a useful test!
P.S. In my experience M-: (crdt--recover)
is able to recover from this situation, but I totally agree with the points you made above why it shouldn't be interactive/necessary!
Jonathan Ming (fc0f99c8) at 03 Jul 02:04
Thanks for this great package!
These changes allow faster sharing & connecting with tuntox links made using crdt-copy-url
. This changed behavior is toggleable using crdt-tuntox-password-in-url
, which defaults to nil to preserve existing behavior and to remind users that they should be sure they can trust their sharing channel before turning this on.
If you set crdt-tuntox-password-in-url
to t
, then the URL made by crdt-copy-url
will put the password in plaintext into the query string of the URL. When calling crdt-connect
, pasting in the URL with the query string password will automatically get and use the password without requiring a separate prompt. This lets users (like my friend and I) who already have a secure/encrypted text channel send each other the full link with password in a single copy-paste, instead of having to copy-paste the URL followed by typing out the password again in two separate steps.
I saw there's also a development
branch, but I wasn't sure what state that branch was in or when that might make it to the ELPA version, so that's why this merge request targets master
-- it should apply pretty cleanly onto development
as well though so let me know if I should rebase.
Jonathan Ming (fc0f99c8) at 24 Jun 23:04
fix: password process metadata locations
... and 1 more commit
Jonathan Ming (6be3deae) at 24 Jun 22:59
fix: password process metadata locations
Jonathan Ming (d920ce75) at 24 Jun 22:15
feat: Option to put tuntox password in copied URL