Improved spam filtering

[aarongustafson]

Despite having the honeypot in place, we’re still getting a considerable amount of spam through the form and into GitHub. Some of the indicators that something is likely spam are:

• want title & body match
• want title is very short (1-2 words)

We could address this in a few ways:

1. Add client-side checks for these features and block submission (the first would require JS, the second could be done using pattern)
2. Add checks in Zapier that flag these items as spam and do not let them pass

Honestly, I’m inclined to try both approaches, but wanted to get y’all’s thoughs.

[ststimac]

I am open to trying to both.

[captainbrosset]

Those 2 proposals sound good to me too.

Also, I'd be more than happy to help triage incoming wants if they were to end up in a "to-review" stage before getting turned into real issues. The spam wants I've seen so far are pretty easy to detect, so I'm imagining that having a moderation step in the process wouldn't be too time consuming.

[github-actions]

This has gotten stale. Take a look or close it out.

[onaralili]

Another option, use OOPSpam on Integromat similar to Zapier.