Lol my meme worked! :D
My unaltered meme now passes!
this post was submitted on 20 Dec 2024
166 points (97.2% liked)
Lemmy.World Announcements
29156 readers
4 users here now
This Community is intended for posts about the Lemmy.world server by the admins.
Follow us for server news ๐
Outages ๐ฅ
https://status.lemmy.world
For support with issues at Lemmy.world, go to the Lemmy.world Support community.
Support e-mail
Any support requests are best sent to [email protected] e-mail.
Report contact
- DM https://lemmy.world/u/lwreport
- Email [email protected] (PGP Supported)
Donations ๐
If you would like to make a donation to support the cost of running this platform, please do so at the following donation URLs.
If you can, please use / switch to Ko-Fi, it has the lowest fees for us
Join the team
founded 2 years ago
MODERATORS
Finally, the oppressive censorship of our right to free speech has been lifted! Parenthood!
I don't get it. Did the old filter used to censor images containing the word parenthood or something?
Yea, I know of it doing it on the words parenthood, children and kids because I also had an earlier meme about before and after kids and all three of those would fail without censoring
6.7% is still very high
Any details about the system? Is it something off-the-shelf, or custom-made? Is it using something fancy like transformer models? I'm guessing that would be too expensive
I still can't upload unedited pictures from my pixel 3a via Jerboa :( For whatever reason, uploading them as-is results In a 403 response. Editing them in google photos (minor cropping), saving, and trying again would often result in success.
Have you tried another Lemmy client? For scanner rejected media boost would report an error 400, Unknown error, not 403
You can double check by going to lemmy.world , click create post and then skip to upload an image (you don't need to fill anything out) and if you get a red popup with "External Validation Failed" that's when it got rejected
I tried using the lemmy.world web UI and got the following error: json.parse unexpected character at line 1 column 1 of the JSON file.
I also get an error using the web UI - json.parse unexpected character at line 1 column 1 of the JSON file.
a JSON parsing error is certainly unexpected. I wonder if you happen to be triggering some automatic Cloudflare WAF rule.
could you try uploading the same file from a computer? before uploading, please open your browser dev tools (F12) and visit the network tab. it should show some more details in there. especially the response tab should show an actual error message. in the headers tab, you could also share the value of the cf-ray header with us and we can take a look at our logs. please be careful not to share everything you see in that network tab, as there are values visible there that allow taking over your lemmy account. specifically cookies and the jwt value; in some cases also an authorization header. cf-ray is not sensitive, it's just an identifier associated with the individual request.
feel free to pm me the cf-ray value rather than posting it publicly.
Thanks for the reply and apologies for getting back to you. I typed that out right before going to bed :(
Looking in developer tools, it does look like Cloudflare is what's blocking me. Here's the cf-ray value: 8f4ffe74bffc22f1-ORD
Now that I'm on a PC, I can simply open the file in an image editor, resave it without making any intentional modifications, and the upload succeeds. It makes me think that it has something to do with the image metadata (maybe EXIF?).
I'll send you a pm you a link to the unmodified image momentarily.
thanks for the image. for some reason i can't see the firewall event for your attempt, but when i tried to upload the image myself i found the event. it's a rule related to a php file upload vulnerability in software we're not even using, it's disabled now.
Very cool, thanks! This will make it a lot easier for me to post OC.