Because it was implemented using WebSockets, which was torn out for 0.18. They need to reimplement a captcha using HTTP instead. Not the most difficult job or anything, just didn’t make the cut for 0.18 in the interests of getting it out there.
EDIT: I’m wrong, just double-checked github after reading what @[email protected] said. See below for his comment or here for the discussion on github.
I’m pretty sure it was removed because they had concerns with the current implementation being too easy for bots and too hard for humans (including accessibility concerns), and was entirely unrelated to the WebSockets issue. AFAIK they are replacing their custom implementation with mCaptcha which is a fully-automated solution that will basically pass so long as your browser runs JavaScript. I am unconvinced that this solves the “too easy for bots” problem, but it certainly solves the “too hard for humans” one.
Because it was implemented using WebSockets, which was torn out for 0.18. They need to reimplement a captcha using HTTP instead. Not the most difficult job or anything, just didn’t make the cut for 0.18 in the interests of getting it out there.EDIT: I’m wrong, just double-checked github after reading what @[email protected] said. See below for his comment or here for the discussion on github.
I’m pretty sure it was removed because they had concerns with the current implementation being too easy for bots and too hard for humans (including accessibility concerns), and was entirely unrelated to the WebSockets issue. AFAIK they are replacing their custom implementation with mCaptcha which is a fully-automated solution that will basically pass so long as your browser runs JavaScript. I am unconvinced that this solves the “too easy for bots” problem, but it certainly solves the “too hard for humans” one.
Just double-checked, you’re completely right. Edited my comment.
All good, both of those changes landed in 0.18.0 so I totally understand how they might seem related.