Vamp@lemmy.world to Lemmy.world Support@lemmy.world · 1 year agoThere's a person who is spam creating hundreds of communites with impossibly long descriptions on world, why haven't they been banned yet?lemmy.worldimagemessage-square62fedilinkarrow-up1431arrow-down121
arrow-up1410arrow-down1imageThere's a person who is spam creating hundreds of communites with impossibly long descriptions on world, why haven't they been banned yet?lemmy.worldVamp@lemmy.world to Lemmy.world Support@lemmy.world · 1 year agomessage-square62fedilink
minus-squaredelirium@lemmy.worldlinkfedilinkarrow-up24·1 year agoI guess it’s achievable with hosting you’re using (with nginx ip block list for example if you’re using it)
minus-squaredust_accelerator@discuss.tchncs.delinkfedilinkarrow-up15·edit-21 year agoWhat you’re looking for is functionality like fail2ban, but probably with a filter set to the HTTP endpoint for creating communities. Not sure if it will work, I haven’t really looked into the Lemmy code/architecture yet.
minus-squareABeeinSpace@lemmy.worldlinkfedilinkarrow-up11·1 year agoIf they’re using Cloudflare it can do this too. Even the free tier, you can have one monstrously long WAF rule to ban a bunch of IPs
I guess it’s achievable with hosting you’re using (with nginx ip block list for example if you’re using it)
What you’re looking for is functionality like fail2ban, but probably with a filter set to the HTTP endpoint for creating communities. Not sure if it will work, I haven’t really looked into the Lemmy code/architecture yet.
If they’re using Cloudflare it can do this too. Even the free tier, you can have one monstrously long WAF rule to ban a bunch of IPs