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

Clear contents button #27

Open
grempe opened this issue Jul 31, 2020 · 0 comments
Open

Clear contents button #27

grempe opened this issue Jul 31, 2020 · 0 comments

Comments

@grempe
Copy link

grempe commented Jul 31, 2020

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:

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.

https://saltpack.org/armoring

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

No branches or pull requests

1 participant