... (according to Slashdot, Chrome/Chromium v. 59 handles this and I looked it up; it's due by early June, but according to Google's IDN documentation, it's fixed in 58, which is due at the end of April).

Honestly if you use Chrome, I wouldn't recommend assuming you're safe. Perhaps try Chrome Canary, or use Firefox (after you fix its settings) or Safari until this blows over. And/or avoid unreliable sites with shitty or no security.