You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd suggest a quick button that can be clicked next to each user input field (where encrypted or plaintext is pasted) to clear its contents. For long file contents (e.g. when you paste in armored encrypted .jpg file contents) it is somewhat painful to select all the armored text with a mouse to remove it. You'd otherwise have to know to use e.g. CMD-a on macOS to select all text and then delete key.
Also, the way the saltpack armor works, with 200 "words" on a line (which results in VERY long lines, thousands of characters wide) followed by a newline results in armoring that cannot be selected with a triple click within the text box to select very long blocks of armor. Triple click ends up just selecting the "words" up to the previous newline, not the entire armored text.
I question the decision to split saltpack lines at 200 words (I did see its the default in the saltpack spec, but only by convention and not required). If you are not splitting armored text into lines suitable for pasting in an email (e.g. five words wide) why bother splitting them with newlines at all?
Here's a screenshot of cat of a long armored file. You can clearly see the giant line lengths with infrequent newlines.
Since whitespace gets stripped, the encoder has some flexibility in formatting. Our encoder emits a space every 15 characters and a newline every 200 words. That's what felt nicest when we tested it in different terminals and messaging apps. Because the decoder doesn't rely on this spacing, we can change it in the future.
I'd suggest a quick button that can be clicked next to each user input field (where encrypted or plaintext is pasted) to clear its contents. For long file contents (e.g. when you paste in armored encrypted .jpg file contents) it is somewhat painful to select all the armored text with a mouse to remove it. You'd otherwise have to know to use e.g. CMD-a on macOS to select all text and then delete key.
Also, the way the saltpack armor works, with 200 "words" on a line (which results in VERY long lines, thousands of characters wide) followed by a newline results in armoring that cannot be selected with a triple click within the text box to select very long blocks of armor. Triple click ends up just selecting the "words" up to the previous newline, not the entire armored text.
I question the decision to split saltpack lines at 200 words (I did see its the default in the saltpack spec, but only by convention and not required). If you are not splitting armored text into lines suitable for pasting in an email (e.g. five words wide) why bother splitting them with newlines at all?
Here's a screenshot of
cat
of a long armored file. You can clearly see the giant line lengths with infrequent newlines.https://share.getcloudapp.com/YEuojbpR
From the saltpack spec:
https://saltpack.org/armoring
The text was updated successfully, but these errors were encountered: