Report site bugs here

@Wiimeiser
 
You can add &hidden=1 to the end of the URL to show hidden images.

@T12  
Wait, are you sure unhiding images doesn’t unhide every image?

@Phoenixflambe
 
I don’t know. I don’t tend to use the hide functions very much, but I know that adding that to the URL worked when I hid something by mistake.

@Phoenixflambe
 
@T12  
it’s just a filter that lets you view the images you have hidden. From there you can go to them and click the button to unhide the specific ones you don’t want hidden any more.

Twitter upload fetching seems to be down for me.

@Litrojia  
Working for me. What image did you try?

@byte[]  
It seems to be fine now. There might’ve been internet issues on my end. I tried uploading this image, and I tried it with this post as well (without the intent of uploading it) as a test, and neither worked at the time.

@Litrojia  
It may have been due to this.

@byte[]  
I tried uploading the image just now and got a Cloudflare error, so you’re probably right.

Any particular reason some searches would be getting 5XX errors and not others, or is it just CloudFlare being CloudFlare?  
eg. this search works  
this search 500s

@Background Pony #62CA  
Catastrophic backtracking

@byte[]  
Ah, I will try to be smarter with wildcards then.

Good friend of mine can’t recover the password. When he press “Forgot password” he get “You are currently banned” error or “Bad request” http error

@ShadowGuy  
They should either join our Discord server and tell us more in #support channel, or Email us at ops[at]derpibooru.org with the ban ID (if they are accidentally caught by an IP ban)

@Princess Celestia  
Thank you your majesty! <3

In the search syntax page, the text "width:1920" in the section about Escaping Special Characters has the wrong link: it links to “faved_by:k_a” instead.
 
Some posts have invisible characters in their source URLs: I’ve already encountered (and fixed) two that had a line break at the end, and found two where a line break is the entire string. I don’t know how to search for other possible manifestations…
 
Am I doing it wrong, or shouldn’t the query search_url:\*\\?\* find posts which have a question mark in their source URLs? (it doesn’t)

@Background Pony #62CA  
Someone with access will have to fix that.
 
You can use the SQL data dumps (linked from the API page) to find the rest.
 
According to Elasticsearch it doesn’t seem like the wildcard query supports escape sequences. Sorry about that.

@byte[]  

 
Well, I happened to wander upon this page which seemed to indicate double-escaping is needed, and indeed, source_url:\*\\\\?\* seems to find URLs with question marks in them. So, thanks for the accidental help. ^^

@Background Pony #62CA  
Interesting. Philomena doesn’t use the query_string query for anything.

@Background Pony #62CA  
fixed search syntax page

hello, i think i found a bug regarding notifications from merged images.  
https://sharing.rainbowdash.cc/sharex/chrome_gldew1kqJO.jpg  
first one not have a correct thumbnail anymore at the left side of the notification.  
probably not a huge problem, but could it not have a working thumbnail, possible from the new image?  
the second problem is, if one clicks on the link, normally the notification will automatically go away.  
in this case if one clicks on the link, it redirects to the new number/image and the notification will stay.  
one probably has to unsubscribe or remove the notification manually.

Reverse search from deviantArt seems to have a problem:  
Example on dA and on Derpi >>2428408  

Galleries are bugging up and I have no idea why… The first page doesn’t display recent changes unless you explicitly put page 1 in the URL…

Somebody put a comment on >>2439345 (merged), which I was subscribed to and which then got merged into >>2344316. Going to the new image doesn’t clear the notification, and I can’t unfollow the old image. I was eventually able to delete the notification, and it shouldn’t be possible for people to put new comments on the old image, but still, there’s a bug there.

So it seems that whenever you try to post during the 30-second wait, the wait timer resets to the full 30 seconds. Is that a bug or a feature?