this post was submitted on 23 Jun 2023
117 points (99.2% liked)
Lemmy
2172 readers
23 users here now
Everything about Lemmy; bugs, gripes, praises, and advocacy.
For discussion about the lemmy.ml instance, go to [email protected].
founded 4 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I had it turned off today as a test but I just enabled it (registrations were disabled over the past week or so). I guess I'll see tomorrow if it makes a difference
Thanks again - when the bots came for my instance, they were stopped because all the email addresses were fake and they couldnt pass validation. I'm hoping the combination of email and manual verification helps to stop the wave. Seeing what you've posted in the image is really useful, im going to look back at our applications and see if any are similar, which would mean they may have got around the email validation.
Are Email addresses kept and logged anywhere, or are they discarded after registration?
For privacy reasons, it'd be nice if we could somehow have a reliable bot blocking/spam blocking method that doesn't require Email.
While Email adds a good layer of spam blocking just from the spam blocking the email providers are doing themselves, having an option to verify with Email OR jump through multiple hoops instead would be cool. Hoops that are difficult for a bot to be programmed to defeat all of them. Such as captcha, with a simple math equation, and something else all combined.
Just tossing ideas around, because this is all still being built out.
Yeah they're kept in the database.
A sufficiently complex captcha might do it. I've seen something else that verifies you're not a bot based on PoW calculation, although I don't know how reliable that would be personally.
A split verification method might be a good way forwards for the privacy conscious instances.