Network Administrator for Pawb.Social, furry, and a programmer
Mastodon: @crashdoom@furry.engineer
ℹ️ 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
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/
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!
Good question, and I’ve not thought about it previously other than that we would remove content if the original artist requested us to do so. Though, we don’t have a formal list of DNP content, we just expect that users post content they’re permitted to or that is already otherwise shared on other sites (like e621).
I’m not against a DNP list, but I think I’d lean more towards respecting an existing DNP like https://e621.net/wiki_pages/85. Though, if we did end up getting to the point of having a lot of DNPs that don’t appear on their list, we’d probably move to making our own.
I’ll bring this up to the rest of the team too for feedback!
Phlox’s amazing smile absolutely sends me every time XD
I’m not able to replicate this myself as it’s showing on both the Create Post and editing modes. I’ve cleared the site cache on Cloudflare as it could be it’s caching an old version of the UI. I’d also encourage clearing your browser cache / force refreshing.
We’ve got a fix deployed that’ll allow the NSFW box to be toggled again for new and existing posts – Is there any chance you’d be able to facilitate that on your existing posts? We’re hoping that’ll alleviate reports and complaints in the interim while we wait for the permanent backend fix x3
We’ve updated Lemmy UI to a hotfix version of 0.19.11 that re-enables the NSFW field on the Create Post form for NSFW communities. This should once again allow users to correctly mark posts explicitly with the NSFW tag.
While a permanent fix is in development by the Lemmy team, please ensure you check this NSFW toggle if you’re posting to a NSFW community.
Thank you for your understanding and patience.
I believe there was a change to some Lemmy communities where if the community itself is marked as “NSFW” there’s no ability to toggle it off anymore: https://github.com/LemmyNet/lemmy-ui/pull/2887 (https://join-lemmy.org/news/2025-04-08_-_Lemmy_Release_v0.19.11).
If the post isn’t flagging automatically as NSFW in a NSFW community, then there may be a backend bug that needs to be reported to the Lemmy developers via GitHub.
Update: Turns out a security feature we enabled to block “AI Bots” (like ChatGPT) was blocking federation traffic… Since it’s affecting stuff right now, I’ve disabled it again until I can get time after LVFC to take a look into building a comprehensive “allow list” of different federation traffic headers.
tl;dr Give it a little bit and things should hopefully catch up with new posts, but I don’t know if Lemmy post-syncs old posts without someone searching for them on our instance.
Restarting the federation pods appears to have at least lowered the failure queue a little, but it’s showing that while we’ve sent things to lemmit.online (as the example), it hasn’t seen anything from them since 4/14/2025, 10:14:27 PM. So I’m presuming the next time they try to sync and send something to us it SHOULD update…
The federation state checker seems to be indicating that we’re not behind in sending them posts anymore so outgoing should be fixed, but I’m unsure how to troubleshoot incoming further. I’m wondering if there’s a bug with the latest version of Lemmy?
Morning all! It does appear like we’re not getting some instances posts (you can find a list by using https://phiresky.github.io/lemmy-federation-state/site?domain=pawb.social). I’m currently investigating and I appreciate folks poking on this :3
via here (I’m setting up an RSS feed monitor), via email (network[at]pawb.social), or with a DM message to highlight it. It seems like mentions in the original post don’t alert the mentioned person, so I only got a notice when you replied to a message from me / mentioned me in a comment. >~<;
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!