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

an "input method" for /secure decrypt? #536

Open
unhammer opened this issue Jan 26, 2022 · 2 comments
Open

an "input method" for /secure decrypt? #536

unhammer opened this issue Jan 26, 2022 · 2 comments

Comments

@unhammer
Copy link

If I do /secure decrypt hunter2 then the string hunter2 is stored by the predictive keyboard and also shows up in the input history (shown on long-press). It'd be nice if there were a way to enter /secure data in private mode (e.g. the weechat terminal UI shows stars on typing the password). If it's hard to hook into the input box to override how text is shown, perhaps a specific button in the menu for sending the /secure decrypt message to the weechat buffer would make sense.

@oakkitten
Copy link
Collaborator

perhaps it would be nice if we could conditionally exclude the input field from contributing to user dictionary, e.g. if input starts with /, that would be easy enough—that is if it was possible, which i am not sure it is. other then than, it is also not impossible to replicate WeeChat's behavior (masking out parts of text) but it would require quite a bit of effort that is probably not worthwhile.

i suppose we could—with not too much of an effort—let the user define a few strings such as /secure decrypt or /nickserv identify which would turn off autocompletion completely. this probably should prevent the field from storing anything in any dictionary... right?

i am not sure how a special menu item would look like. do you want it to send pre-filled /secure decrypt yourpassword or show an input field? either way this sounds like something that would be in low demand...

@unhammer
Copy link
Author

i suppose we could—with not too much of an effort—let the user define a few strings such as /secure decrypt or /nickserv identify which would turn off autocompletion completely.

That would be great :-) I'm not so worried about seeing them while typing, but it's worse if the keyboard app sends passwords to Someone Else's Cloud.

i am not sure how a special menu item would look like

me neither :-) just throwing ideas out there to see what sticks.

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

No branches or pull requests

2 participants