search

WebWeWant / webwewant.fyi

If you build websites, you inevitably run into problems. Maybe there’s no way to achieve an aspect of your design using CSS. Or maybe there’s a device feature you really wish you could tap into using JavaScript. Or perhaps the in-browser DevTools don’t give you a key insight you need to do your job. We want to hear about it!
https://webwewant.fyi
MIT License
76 stars 23 forks source link

Improved spam filtering #310

Open aarongustafson opened 3 years ago

aarongustafson commented 3 years ago

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:

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 commented 3 years ago

I am open to trying to both.

captainbrosset commented 3 years ago

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[bot] commented 3 years ago

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

onaralili commented 3 years ago

Another option, use OOPSpam on Integromat similar to Zapier.