'Regular' comment rejected as spam in web2, but not legacy

Description

I tried to add a comment to a talk this evening, which was perfectly innocent, however on web2 it was rejected as spam. Tried it on the legacy website and the message went through fine, which is a bit strange as I believe they both use the same API?

Submission URL: https://joind.in/event/php-uk-conference/magento-done-right/add-comment

Payload:
rating=4&comment=Plenty+of+nice+little+%27take-aways%27+and+tools+to+check+out+-+would+have+been+nice+if+it+was+a+little+longer%2C+but+still+makes+me+want+to+start+using+Magento+2+for+all+our+production+sites+now%21%21%0D%0A

Steps to reproduce:
1/ Login (I logged in via Twitter as myself, but presumably that doesn't impact it)
2/ Browse to talk
3/ Rate the talk as 4/5 and comment: Plenty of nice little 'take-aways' and tools to check out - would have been nice if it was a little longer, but still makes me want to start using Magento 2 for all our production sites now!!
4/ Try to submit

Expect result:
The review is posted

Actual result:
Error Message: Comment failed the spam check.

System: Fedora 21 running Chrome 48
Note: I was using hotel WiFi.

As far as I am aware, the spam filter is running Akismet, but that doesn't explain why I could post it via Legacy, but not web2

Status

Assignee

Clair

Reporter

Liam

Labels

Epic Name <span class="error">&#91;deprecated, this field is no longer being used&#93;</span>

None

Components

Priority

Minor