Joey 
PM me your cute OCs
Site is fine, you may be having issues with Cloudflare, but I can’t help you much with that.
Report site bugs here
Zaknel 
Mods-Ezekiel 33:11
Mobile data seems to have better luck using the site. I guess it is something with Cloudflare, or whatever. Sorry.
The Frowning Pony
Administrator
13 blinks per minute
From byte[]
Level 3 (CenturyLink) in both Paris and Washington D.C. is suffering from extreme packet loss as I write this (upwards of 60% aggregate based on my testing). Our site in the US is suffering 502 errors because Cloudflare’s TCP retry interval exceeds its maximum timeout for the site to respond, and so this is why you are getting intermittent error pages.This packet loss could be the result of a denial-of-service attack, or it could be the fault of some other reason. Level 3 would have to withdraw its BGP announcements or stop dropping packets for the issue to subside. We’ve investigated; this isn’t an issue with the server or Cloudflare, and there is nothing else we can do about this.
Background Pony #DDCC
I found a broken image.
Full image is loading fine, but both thumbnail and preview are broken. Returns 404 when I try to load them directly.
Full image is loading fine, but both thumbnail and preview are broken. Returns 404 when I try to load them directly.
Mildgyth 
Senior Moderator
Humata, Hukhta, Hvarshta
The fetcher needs to be fixed; since yesterday, DA has been hosting some of its images outside of its own server, in a site called “wixmp-ed.appspot.com”; attempting to upload a image from it the normal way fails, it’s also impossible to upload a image from it with its URL raw address, which means that you’d have to download it yourself and then upload locally. Yesterday, i only found one with this problem; now out of the five images i uploaded today, three had this problem.
Wiimeiser
So it seems to be a measure specifically to thwart fetchers like ours…
FYI this is the first time I’ve ever seen an error that’s not 403, 404, 500, 502, 503, and I think 504.
(Foil Hat)
@Mildgyth
Accessing that link gives me the error “{“message”:“token expired”,“code”:401,“payload”:null}”
According to Google, a 401 error means “unauthorized access”, essentially identical to a 403 error AFAIK:
Accessing that link gives me the error “{“message”:“token expired”,“code”:401,“payload”:null}”
According to Google, a 401 error means “unauthorized access”, essentially identical to a 403 error AFAIK:
The request has not been applied because it lacks valid authentication credentials for the target resource.The server generating a 401 response MUST send a WWW-Authenticate header field1 containing at least one challenge applicable to the target resource.If the request included authentication credentials, then the 401 response indicates that authorization has been refused for those credentials. The user agent MAY repeat the request with a new or replaced Authorization header field2. If the 401 response contains the same challenge as the prior response, and the user agent has already attempted authentication at least once, then the user agent SHOULD present the enclosed representation to the user, since it usually contains relevant diagnostic information.
So it seems to be a measure specifically to thwart fetchers like ours…
FYI this is the first time I’ve ever seen an error that’s not 403, 404, 500, 502, 503, and I think 504.
The Frowning Pony
Administrator
13 blinks per minute
@Mildgyth
Their server expects a token from the requesting client to show the image. It’s a way to prevent hotlinking, and by the side stop scrappers like ours that try to circumvent DA’s shitty API and oembed impementation (which this change appears to have been broken even further).
It’s not the first time they’ve done this.
Their server expects a token from the requesting client to show the image. It’s a way to prevent hotlinking, and by the side stop scrappers like ours that try to circumvent DA’s shitty API and oembed impementation (which this change appears to have been broken even further).
It’s not the first time they’ve done this.
Zaknel
Mods-Ezekiel 33:11
I used to use the “Random Image” button to constantly find images found under either a very broad tag that could very easily have a ton of older images missing a few tags, or under a very specific complex filter which, by the definitions of its own tags, has to be incorrectly tagged.
But, now, I have learned that this feature doesn’t work like it used to anymore. Now, I enter in the tag(s) i want to find a series of random images on, and after I press the “Random Image” button while still in the image gallery, it takes me to a random image having the tag(s) I entered, but then when I press the random image button again, while I’m at the image in question, I get taken to an image using the *. It used to be I could just keep pressing the “Random Image” button again and again, and get taken to new image using that tag(s) I specified.
But, this seems to be an issue with complex tools. I found this using the following complex search:
But, now, I have learned that this feature doesn’t work like it used to anymore. Now, I enter in the tag(s) i want to find a series of random images on, and after I press the “Random Image” button while still in the image gallery, it takes me to a random image having the tag(s) I entered, but then when I press the random image button again, while I’m at the image in question, I get taken to an image using the *. It used to be I could just keep pressing the “Random Image” button again and again, and get taken to new image using that tag(s) I specified.
But, this seems to be an issue with complex tools. I found this using the following complex search:
(solo male OR solo female OR solo futa OR females only OR males only OR futas only), -(suggestive OR questionable OR explicit)
Moderator Zeb found the same issue with this search as well as with just [bq=”Zeb’s Test Search](solo male OR solo female OR solo futa OR females only OR males only OR futas only)[/bq]So, it may be an issue with the parenthesis. If you could fix this, that might be nice.
Background Pony #FAFE
@Zaknel
I think the problem with your search is that you’re negating tags in parentheses instead of individually negating them. Should be able to work as [
I think the problem with your search is that you’re negating tags in parentheses instead of individually negating them. Should be able to work as [
(solo male OR solo female OR solo futa OR females only OR males only OR futas only), -suggestive, -questionable, -explicit
](/search?q=28solo+male+OR+solo+female+OR+solo+futa+OR+females+only+OR+males+only+OR+futas+only292C+-suggestive2C+-questionable%2C+-explicit)
Interested in advertising on Derpibooru? Click here for information!
Help fund the $15 daily operational cost of Derpibooru - support us financially!