6 ms·
This is done. A summary of the issue and apology can be found here: https://gitlab.com/gnachman/iterm2/wikis/dnslookupissue https://gitlab.com/gnachman/iterm2/w
by gnachman 9y ago
This is done. A summary of the issue and apology can be found here: https://gitlab.com/gnachman/iterm2/wikis/dnslookupissue https://gitlab.com/gnachman/iterm2/wikis/dnslookupissue
- lobster_johnson 9y agoThank you. Will you be releasing a new beta, too?
- gnachman 9y agoYep. I'll put that out tonight.
- zbobet2012 9y agoMistakes happen. Quick responses and honest apologies are always appreciated!
- beager 9y agoThanks for owning it and thanks for fixing it. Better response than you're likely to get almost anywhere!
- ak217 9y agoThank you for building the best terminal app in the world, and for responding to user feedback so quickly.
- kahlonel 9y agoiTerm2 is the only terminal I like in every way. Thanks for that.
- Exuma 9y agoTHANK YOU for being so awesome and responding to feedback so quickly. That is a breath of fresh air
- dylanz 9y agoThank you for addressing this so quickly. Great find and great response.
- Waterluvian 9y agoI love iterm2. It's like I'm responding to a celebrity. Thanks for making mistakes.
- k_sze 9y agoThanks for the quick response. How does this coincide with the 3.1.1 release though? I was still on 3.0.15 and there are new features and other fixes in 3.1.x. Do the new features and the other fixes happen to be reasonably tested and ready already?
- gnachman 9y ago3.1.1 is well tested. Everyone should upgrade. If you find regressions they'll be my highest priority.
- scubbo 9y agoLogging in to HN for the first time in several years to say thank you for your swift and responsible action.
- puredlx 9y agoAwesome, thank you for the swift fix!
- teddyh 9y agoWhy didn’t you do this two years ago, when the first bug report about this was made? (https://gitlab.com/gnachman/iterm2/issues/3688 https://gitlab.com/gnachman/iterm2/issues/3688) Or a year ago, when a second report was made? (https://gitlab.com/gnachman/iterm2/issues/5303 https://gitlab.com/gnachman/iterm2/issues/5303) Note that the first bug report explicitly mentions the leaking of passwords. Was it really all about the “level of concern”, as you say, and you wouldn’t have changed this without the exposure?
- yanokwa 9y agoThis is a deeply unkind thing to say to someone who donates their free time to provide a public good. George apologized for his oversight and fixed the problem. Take him at his word and thank him.
- woof 9y agoPlease don't call this "oversight". He was (made) aware of the problem and chose to keep the default.
- nolok 9y agoUhh, to be fair both reports were answered with appropriate concerns. First made it sound like a very specific issue for that one user, and was given a way to disable it for him. Second made it sound like an entire class of users would need it off, and an option switch was provided. What do you think is more probable, that he intentionally left that hole open despite not directly benefitting from it, or simply that when he answered both original reports and provided an appropriate solution, he didn't fully think about the details and implications of what those issues meant? Have you really never have a closed issue come back to you "went from bad to worse, abort!“ ?
- yanokwa 9y agoThanks for doing this George! In addition to donating at https://iterm2.com/donate.html https://iterm2.com/donate.html, what can HN users do to help you with iTerm2?
- yashap 9y agoYou're awesome, and so is iTerm2. Thanks for the great work!
- VeejayRampay 9y agoGreat reaction and thanks for producing such a great piece of software, it's making my life better everyday.
- trapperkeeper74 9y agoHooray!
- jorge-d 9y agoThank you ! iTerm2 is amazing and this quick fix only proves it !
- m5badger 9y agoFastest fix ever.