Report site bugs here

Image 3121425 was uploaded five hours ago, yet it still has the

notice.

Using the usual image reporting functionality. Select “other” as the reason and explain the situation in the comments.

@Neko Majin C
Yes. We’ve been working for a few hours on and off to try to fix it. We need to give each attempt to fix it enough time to work or fail before starting the next. I’m about to do what is basically our very last but biggest hammer fix though, so hopefully that will get it working.

UPDATE: Oh, nevermind. The artist already re-uploaded it. >>3121426

a search for “*” sometimes shows newer posts than does /images (and the front page), which take several minutes longer to update

If I recall correctly, when upload pre-screening for new/accountless uploads was implemented, it was said that the position of these posts in the default sort order (which is “initial post date”) would be the moment they are approved and become visible, yet I’m certain that I see new posts appear further down the page in between other posts that I’ve already seen, upon refreshing the /images page. This is with the Everything filter.

Not sure if a bug but this image was uploaded four years ago; yet still shows the “optimizing the filesize” message underneath.

@☬ ᏝᏆᏁᏨᎾᏝᏁᏰᏒᎬᎳᏕᎿᎬᏒᎱᎯᏁ ☬
1.72 MB.

Checks out.

Trying to repair it.

Yeah… I know :o 🙃

@☬ ᏝᏆᏁᏨᎾᏝᏁᏰᏒᎬᎳᏕᎿᎬᏒᎱᎯᏁ ☬
Fixed.

@Ciaran
Thanked you there too ^_^

@☬ ᏝᏆᏁᏨᎾᏝᏁᏰᏒᎬᎳᏕᎿᎬᏒᎱᎯᏁ ☬
My pleasure :)

⊂^‿^つ

Is just me, or merging reporting does not work properly? I remember long time ago you couldn’t send a report for 1 image more than one time. Also are mods even aware of them? These reports can stay a few days still not being accepted.

For example this image: >>3125471 had an automatic report, that get rejected, but I sent a report too, and it’s still not done. I sent it second time already.

@Markiz93
There’s nothing wrong with the system but yes, the queue is stalling. Our main dupe handling force is out of commission for reasons. Other staff members, who aren’t as experienced in handling dupes, do what they feel comfortable with to help keep the queue down (merges require a LOT of attention to detail), and reject obvious false hits. Sometimes they also reject superfluous auto-dupe hits when there’s a manually submitted dupe report for the same pair of images, since a pair can only be approved once, and the manually submitted report is always more helpful than the automatic one.

@saby
BTW, your description on the staff page looks like it’s cut off.

@Background Pony #62CA
Cheers m8.

So I checked the tag changes I just made on an image, and I got the time stated as
“less than a minute from now”
I reloaded and it went away, but that was hella weird.
Did I just have a cause and effect glitch happen in my life or something?

@Toastypk
50% of the time the estimates are 100% correct.

@Toastypk
It was “less than a minute from now”, except backward, not forward in time.

@Toastypk
I’ve seen those too lately.

(Reminds me a bit of Ponibooru’s “-30 seconds ago” timestamps.)

I tried adding the stallion tag to >>2386035, but it says I can’t edit the tags on that image. What gives? Are they locked or something? And is it possible that someone else can add the stallion tag then?
And the mare tag too to be sure?

Looking at the comments and mimi tag-war that went on, its clear to say the tags more than likely got locked as people kept adding aka tag waring.

@Toastypk
I reported the image, asking for these and other tags to be added.

@Background Pony #A3B6
Done.

>>3127685 (deleted) and >>3127686 (deleted) by Dingo Patagonico are both not showing; both have the

message.

@☬ ᏝᏆᏁᏨᎾᏝᏁᏰᏒᎬᎳᏕᎿᎬᏒᎱᎯᏁ ☬
Both look like malformed JPEG. I’ll fix them later, but really we should just make checks that would reject uploads that contain bad jpeg.