Hey! I apologize for the inconvenience. We've adjusted some of the rules after it appears they're impacting a lot more users and were overly aggressive, I'm hoping this resolves the issue and I'm really sorry for the trouble this caused.
It's alright, I was just a bit confused lol. I wonder if there's a way to identify Lemmy clients to be able to at least whitelist normal users, to prevent false positives
Paradoxically, Voyager is what I use myself, so it was allowlisted! There were a ton of rules added during the DDoS, so I’ve trimmed it down a bit 😅
Ah, I see
Accessing pawb.social with Voyager 2.34.0 rn.
I saw mention in Telegram announcements the other day that Crashdoom was doing his best to deflect a DDoS attack on the instance. Maybe it's related, but I'm not having any issues at the moment.
Hmm, I did notice that I'm getting a cloudflare message when accessing this instance from a browser. So that could be related.
Yes, the instances are protected by Cloudflare.
Pawb.Social Feedback
An official community for users of Pawb.Social services (furry.engineer, pawb.fun, and pawb.social) to provide feedback and suggestions.