Strangely… 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 😅

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 given it a stern talking to and helped it recover through a restart, and image uploads appear to be working as normal again!

Honestly, like you said, I genuinely have no idea what the US will do; Currently things are being so shaken up that anything is plausible right now.

For outside the US, I don’t really know what reach other countries have. The UK’s Online Safety Act is the current one I’m watching for since that would require “highly effective age assurance” which… if the folks writing the law had been online like, ever, they’ll have realized is an utterly stupid statement unless they plan to enforce integrating ID Verification via a Credit Agency (Experian, Equifax) which does personal question-based verification (which imo is a huge breach of user privacy since while WE might not know who you are still, the credit agency does and where you signed up).

Yes, several US states along with other nations have been considering porn ban laws, along with the rather blatant anti-LGBTQ stance of the currently elected US party.

In the works! We’re planning to have some info very soon, though we’re still building out an improvement for the NAS to allow us to expand the storage capacity for long term, high size file storage specifically for Pixelfed!

Previously, we were just operating under myself as a sole proprietor. I hadn’t formalized things as I hadn’t expected the big growth, but we’re big enough to justify it to ensure the long-term security of all of our instances, as well as my own personal protection against the changing political climate.

Yeah, it’s been on my plate for a while, and honestly I really should have

Yeah, I have to admit, I spent a while trying to workshop how to make it sound less ominous and I’m really sorry I failed in that; Definitely something for me to work on in the future, and I apologize for it coming across rather legal and scary.

Thank you for doing your part, and thank you for the cute sticker!! :3

Looking like I had an off-by-one error, it’s actually fixed in the beta for 0.19.6; Will look at upgrading to that to fix the issue, just reviewing the changes to make sure there’s nothing else major there.

Looks really, really well done! :D