User blog comment:Rappy 4187/Technical Update: May 25, 2015/@comment-126761-20150527140850/@comment-126761-20150527152517

Regarding that kind of workaround - it wouldn't suddenly open your computer to all sorts of serious issues, but it is certainly inadvisable for anyone without good technical knowledge. As I understand it, the effect is to unconditionally trust the socket.io domain - if someone sneakily managed to put bad content on that site, your browser would continue to tell you it was safe.

Essentially, if in doubt, don't do it. Plus, you don't need to now anyway, now that our fix is live :) (And, it turns out, socket.io fixed the original issue on their side a few minutes later)