Upgrade reCAPTCHA to v3

[jc00ke]

Just saw the announcement. Something to consider since we're going to be upgrading things around here.

Docs

[jc00ke]

Or switch to hCaptcha

[jc00ke]

We should prioritize switching to hCaptcha, as there's been a lot of spam lately.

[jc00ke]

@reidab @aeschright there's been a ton of spam lately. What are you thoughts to switching to hCaptcha or some other form of spam detection?

[aeschright]

I’m in favor of switching to a different option. I haven’t looked into what’s available for a while, so if you have recommendations (or time to make the swap) I’m happy to give that a try.

…

On Sep 17, 2021, at 5:32 PM, Jesse Cooke ***@***.***> wrote:  @reidab @aeschright there's been a ton of spam lately. What are you thoughts to switching to hCaptcha or some other form of spam detection? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

[jc00ke]

hCaptcha looks to be a direct replacement for reCAPTCHA v2, which may not be what we want now that I think about it. Seems like reCAPTCHA v3 with a high score would be good to pair with more blocked words, but I feel like I'll just be playing whack-a-mole.

If we extracted the blocked words to a database table then at least I could script something to easily add instead of having to commit and redeploy. Thoughts there?

[aeschright]

I think having a table for blocked words is a good idea. I'm still working on the Rails 5 update, but since I want to clean up wording for things like "blacklist" in the code before I do a release, we could bundle this along with it.

[jc00ke]

Awesome, thanks for refactoring out that word and also doing the upgrade.