Crashdoom (he/him)
Network Administrator for Pawb.Social, furry, and a programmer
Mastodon: @crashdoom@furry.engineer
- 64 Posts
- 70 Comments
Joined 3 years ago
Cake day: June 2nd, 2023
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
6·1 month agoMaintenance has concluded!
3·2 months agoWhoops-- Turns out, no it wasn’t. I didn’t realize public channels weren’t searchable by default over federation XD
The #pawb:pawb.social space and its channels should be public to everyone + federated; If you’re still getting issues, let me know!
Yes! We’ve got one up at https://matrix.pawb.social/ via web, or pawb.social via apps. You should be able to sign in using your Lemmy (pawb.social), furry.engineer, or pawb.fun account :3
Apologies-- I’m still trying to find a way of properly integrating the images back into Pict-rs, but I’m going to look at making a stop-gap to make the previous images visible again via Nginx. I suspect this could cause some image conflicts since the old image IDs may / may not be re-used, but it should at least fix some of the broken image icons in the meantime.
✅ Closing as no further action is required.
Code of Conduct Update — December 23, 2025
- Added preamble section covering jurisdiction for legal matters against Pawb Social
We haven’t yet got the images reimported so existing images and profile pictures will still be broken. The base URL without the format link would have been cached most likely, but the format link would error as pict-rs isn’t aware of the file you’re trying to reference.
For now, reuploading things like profile pictures is my recommendation rather than waiting for us to get the images reimported.
We did discuss briefly with Asonix but they weren’t sure it’d be possible, so we’re exploring options using an external database for pict-rs but that seems relatively new.
tl;dr we have the files, but are still working on getting them reimported!
ℹ️ Thanks to the efforts of one of our moderators, @southernwolf@pawb.social, we’ve been able to recover some of the lost data from pawb.social that was still active in Cloudflare’s regional caches.
Currently, this is about 25% of all of the known uploaded media files stored on pawb.social.
We’ll be reviewing the final tally of recovered data in the morning and trying to work on getting what we can reimported into Pict-rs.
Code of Conduct Update – Sept 9, 2025
Removed Rule 9 (DNP (Do Not Post) Content): We decided this rule was very heavy handed and have retracted it.
To clarify, e621’s additional rules on the DNP page, like the no “content that is not furry or furry-related” under “Avoid posting these things” do not apply. Non-furry posts are still permitted and encouraged as much as furry posts!
That would be linking, and we’d ask you also include the source in the text description of the post. Direct uploads to Pawb.Social are the only things affected by the rule change.
Code of Conduct Update – July 18, 2025
- Added Rule 9 (DNP (Do Not Post) Content)
Feedback can be provided in the c/meta community, or on the rule announcement post at https://pawb.social/post/28273201
Just found out this was happening and sad I missed it, but must say… seeing the results of y’all’s work is damn impressive! There was also stats linked on the canvas@toast.ooo community: https://pawb.social/post/28021100, so for the name I saw first at #2 out of all 638 users, well done @tblFlip@pawb.social with 4598 pixels and thank you to everyone who contributed and organized \o/
1·11 months agoStrangely… I was tweaking with Cloudflare rules again but I didn’t think I changed anything that should affect that… Please do let me know if it occurs again, but I’m glad it’s fixed now x3
Investigating – I’m not able to find anything obvious in our logs, and it doesn’t look like requests from Jerboa are getting rejected per se. When it occurs again, could you try to access the same content via a browser and see if a message comes up from Cloudflare?
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 😅
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.
Appreciate this… I’m wondering if there’s some kind of race condition that’s causing the DB (or your client) to retry posting. Will investigate once I’m back from a work trip early next week!
👋 Apologies-- I think I just re-discovered the Scunthorpe Problem in real-time. You should be good to attempt to create an account again without issue! :3