This is indeed not an ideal situation, but I guess on most instances this isn't possible. I agree instances should require a captcha of some sort for signing up.
Lemmy
Everything about Lemmy; bugs, gripes, praises, and advocacy.
For discussion about the lemmy.ml instance, go to !meta@lemmy.ml.
Unfortunately lemmy devs removed captchas recently https://github.com/LemmyNet/lemmy/issues/2922 so email verification and/or rate limiting is probably the only real option for protection.
That’s a major bad call. Companies like Google who maintain Captcha know the state of AI and will update captcha continuously to adapt.
With tools like this (https://nopecha.com/) existing they might be right. This is not even the only tool, it really looks like captchas are no longer useful because of AI.
I saw some small instance owners saying they were going to enable open registration and I couldn't help thinking how bad an idea that sounded all around... For exactly a situation such as this inevitably emerging.
I was playing a bit with the API today and yea it might even be a bit too easy at the moment. You can easily use that army of Lemmy bots to upvote all your posts.
We should probably make it very clear in tutorials and setup guides that no email verification is insecure and leaves your instance open to bots.
Stupid of me, I hadn't thought about upvotes, but it's clear that this is perhaps the most "quiet" and dangerous type of abuse.
Not sure how email verification should help. Just add a couple of line to role a email address and then open the verification link.
If you don't have your own domain, it's hard to generate mass email addresses, at least with large providers.
So if someone uses his custom domain to mass-generate emails, it's easier to delete all accounts that use this same email provider.
https://duckduckgo.com/?q=10+min+mail+api&t=fpas&ia=web
There are enough options out there. No need selfhost.
Fuck captcha