-
Notifications
You must be signed in to change notification settings - Fork 49
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
Showterm must ask for confirmation before uploading #12
Comments
I don't know that I would go so far as "unacceptable", but I agree that this would be a very useful feature. However, I can also imagine that some users would feel the other way and resent being asked to confirm what they know they will want to confirm. So a compromise might be that |
@telemachus Absolutely, +1 for such a switch! Then people could just
|
@samuell Just in case you haven't noticed, there is already an indirect way to control uploading. I mention this only because I just noticed it myself while browsing the source code.
|
@telemachus Ok, great! ... that solves my immediate problem at least! :) ... but still I feel I would need tell this instruction every time I recommend it to someone else, so I really liked your suggestion for the flag to enable sharing, and no sharing by default. |
Agreed. I don't think it should be too hard to add the flag, but I want to see what @ConradIrwin thinks before going any further. |
Hi guys. I appreciate the secrecy concern, however I'm convinced that the default behavior should be to upload with no confirmation. I would love for the showterm client to be able to delete showterms, which would require setting up a shared secret on first use, and should mostly solve the concern. I'd also be happy adding a flag that enables confirmation mode for people dealing with secrets so secure that a few seconds in heroku Postgres is still unacceptable (or who don't trust me to implement deletion properly :p) |
@ConradIrwin Sounds good to me. Then people who wanted to default to confirming can simply You've kept |
That sounds awesome! I'd rather keep it dependency free to ease OSX install for non-rubyists, but it's not a hard requirement. |
lol... this thread didn't exist when I started my implemented #15 of this feature (and a It seem I took the same approach, more or less - no change in default behavior, ask only on "-a/--ask" , and no new dependencies for compatability. I switched to OptionParser for clarity given the rising number of options; hopefully that's not a compatability issue. |
@pdkl95 Cool. I'll stop working then and see how your pull request plays out. Thanks! |
I've implemented deletion instead; so if you make a mistake you can always undo. I don't think we need both |
It is critical and unacceptable that showterm does not ask for permission before uploading the session!
it so easily happens that you will reveal some "secrets" on your shell by mistake, and then when Ctrl + D:ing out of showterm, it will immediately upload the session ...
(Otherwise a really awesome thing, thanks for sharing!)
The text was updated successfully, but these errors were encountered: