iTerm2: Please disable 'Perform DNS lookups to check if URLs are valid'

Re:iTerm2: Please disable 'Perform DNS lookups to check if U... by yanokwa on Wednesday September 20, 2017 @02:33AM (#15291279)

Thanks for doing this George! In addition to donating at https://iterm2.com/donate.html, what can HN users do to help you with iTerm2?

[ Parent | on HN ]

Re:iTerm2: Please disable 'Perform DNS lookups to check if U... by Exuma on Tuesday September 19, 2017 @06:59PM (#15289499)

THANK YOU for being so awesome and responding to feedback so quickly. That is a breath of fresh air

[ Parent | on HN ]

Re:iTerm2: Please disable 'Perform DNS lookups to check if U... by zbobet2012 on Tuesday September 19, 2017 @06:01PM (#15289201)

Mistakes happen. Quick responses and honest apologies are always appreciated!

[ Parent | on HN ]

Re:iTerm2: Please disable 'Perform DNS lookups to check if U... by k_sze on Tuesday September 19, 2017 @08:43PM (#15289914)

Thanks 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?

[ Parent | on HN ]

Re:iTerm2: Please disable 'Perform DNS lookups to check if U... by gnachman on Tuesday September 19, 2017 @09:50PM (#15290147)

3.1.1 is well tested. Everyone should upgrade. If you find regressions they'll be my highest priority.

[ Parent | on HN ]

Re:iTerm2: Please disable 'Perform DNS lookups to check if U... by dylanz on Tuesday September 19, 2017 @07:23PM (#15289593)

Thank you for addressing this so quickly. Great find and great response.

[ Parent | on HN ]

Re:iTerm2: Please disable 'Perform DNS lookups to check if U... by Waterluvian on Tuesday September 19, 2017 @08:17PM (#15289817)

I love iterm2. It's like I'm responding to a celebrity. Thanks for making mistakes.

[ Parent | on HN ]

Re:iTerm2: Please disable 'Perform DNS lookups to check if U... by yashap on Wednesday September 20, 2017 @03:41AM (#15291546)

You're awesome, and so is iTerm2. Thanks for the great work!

[ Parent | on HN ]

Re:iTerm2: Please disable 'Perform DNS lookups to check if U... by VeejayRampay on Wednesday September 20, 2017 @03:44AM (#15291561)

Great reaction and thanks for producing such a great piece of software, it's making my life better everyday.

[ Parent | on HN ]

Re:iTerm2: Please disable 'Perform DNS lookups to check if U... by scubbo on Wednesday September 20, 2017 @12:43AM (#15290911)

Logging in to HN for the first time in several years to say thank you for your swift and responsible action.

[ Parent | on HN ]

Re:iTerm2: Please disable 'Perform DNS lookups to check if U... by ak217 on Tuesday September 19, 2017 @06:44PM (#15289434)

Thank you for building the best terminal app in the world, and for responding to user feedback so quickly.

[ Parent | on HN ]

Re:iTerm2: Please disable 'Perform DNS lookups to check if U... by jorge-d on Wednesday September 20, 2017 @04:29AM (#15291717)

Thank you ! iTerm2 is amazing and this quick fix only proves it !

[ Parent | on HN ]

Re:iTerm2: Please disable 'Perform DNS lookups to check if U... by kahlonel on Tuesday September 19, 2017 @06:56PM (#15289485)

iTerm2 is the only terminal I like in every way. Thanks for that.

[ Parent | on HN ]

Re:iTerm2: Please disable 'Perform DNS lookups to check if U... by lobster_johnson on Tuesday September 19, 2017 @05:58PM (#15289184)

Thank you. Will you be releasing a new beta, too?

[ Parent | on HN ]

Re:iTerm2: Please disable 'Perform DNS lookups to check if U... by gnachman on Tuesday September 19, 2017 @06:12PM (#15289268)

Yep. I'll put that out tonight.

[ Parent | on HN ]

Re:iTerm2: Please disable 'Perform DNS lookups to check if U... by beager on Tuesday September 19, 2017 @06:41PM (#15289427)

Thanks for owning it and thanks for fixing it. Better response than you're likely to get almost anywhere!

[ Parent | on HN ]

Re:iTerm2: Please disable 'Perform DNS lookups to check if U... by m5badger on Wednesday September 20, 2017 @08:59AM (#15293217)

Fastest fix ever.

[ Parent | on HN ]

Re:iTerm2: Please disable 'Perform DNS lookups to check if U... by puredlx on Wednesday September 20, 2017 @01:59AM (#15291162)

Awesome, thank you for the swift fix!

[ Parent | on HN ]

Re:iTerm2: Please disable 'Perform DNS lookups to check if U... by trapperkeeper74 on Wednesday September 20, 2017 @04:13AM (#15291655)

Hooray!

[ Parent | on HN ]

Re:iTerm2: Please disable 'Perform DNS lookups to check if U... by teddyh on Wednesday September 20, 2017 @02:13AM (#15291209)

Why didn’t you do this two years ago, when the first bug report about this was made? (https://gitlab.com/gnachman/iterm2/issues/3688) Or a year ago, when a second report was made? (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?

[ Parent | on HN ]

Re:iTerm2: Please disable 'Perform DNS lookups to check if U... by yanokwa on Wednesday September 20, 2017 @02:30AM (#15291273)

This 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.

[ Parent | on HN ]

Re:iTerm2: Please disable 'Perform DNS lookups to check if U... by woof on Wednesday September 20, 2017 @06:41AM (#15292282)

Please don't call this "oversight".

He was (made) aware of the problem and chose to keep the default.

[ Parent | on HN ]

Re:iTerm2: Please disable 'Perform DNS lookups to check if U... by nolok on Wednesday September 20, 2017 @08:11AM (#15292804)

Uhh, 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!“ ?

[ Parent | on HN ]