Posts

@Boxless  
Hopefully! It can be annoying as a service provider when something upstream causes problems.

@Damaged  
We’ll see if it holds true.

@Derpy Whooves  
@Boxless  
Possibly related  

@Derpy Whooves  
I’ve been running into 5xx errors pretty consistently every, oh, fiveish hours? It’s weird.

@Boxless  
I ran into inexplicable logoffs a couple of times this week, too. Plus more than the usual 5xx errors. Not sure if it’s related to transients or more of the usual background noise of ddos attacks.

@byte[]  
Two months later it finally happened again. Should i just treat the Remember Me box like it doesn’t exist and just log in every time i use the site? I’m aware it’s probably an accident but i just…
 
pls.

@byte[]  
oh neat

@Boxless  
Just to update you on the status, this was merged and deployed today.

@Wellwater  
I just did some experimenting. I first noticed on Android Chrome, but I was able to reproduce the same result on Chrome for Windows on my laptop as well as Edge (blech). The same results were even obtained after clearing my cached data.
 
I noticed it was locking onto images which I had faved, so I tried filtering them out, with the result that it would now choose one of two images when random image was pressed. They were not picked in equal proportions (about 2 or 3 times more often for one than the other).
 
@byte[]
 
I admit I have a fairly complex list involving several terms which have * on each end to force it to match tags which contain specific words, as well as forcibly adding all of my faved images to the list. I just tried constructing a search which would be equivalent, and obtained the same result, but a different search with just a single term of that type works fine.
 
Edit: Further experimentation seems to reveal a similar behaviour to a lesser extent on any search with an OR. The random image produced does change, but always seems to be one with as many of the search terms as possible. Try searching fluttershy || rainbow dash, and see if random image ever produces one which doesn’t contain both, because I haven’t seen any.

@T12  
What’s in your complex watchlist

@T12  
Now I wonder if the problem is just that your phone browser is aggressively caching /images/random (one copy for each query string) without recognizing that it’s a redirect that can’t usefully be cached. What browser is it?

@Wellwater
 
No, none. I’m on a phone which doesn’t support them.
 
I just checked and my:upvotes does the same thing.

@T12  
I can’t reproduce (with my:watched or my:watched,my:upvotes). Do you have any userscripts enabled?

When trying to go to a random image from any search containing my:watched as one of the search terms, I always get the same image. When I try to go to another random image from that image I still get that same image. If I set up the search to exclude the normal image, a different one is chosen but it only ever picks that one instead.
 
This does not happen in other searches which do not involve my:watched.

@Boxless  
None is intended. Nothing is worse than thinking everything is working perfectly, when in actuality all your users are stewing about problems and not reporting them.

@Damaged  
I’m getting a vibe of sarcasm through text here.

@Boxless  
Yeah. And we appreciate you keeping on top of it.
 
This news came through just yesterday, so I figured I’d give you an update. :)

@Damaged  
I’m doing what i said i’d do, and given my significant dislike of reading Git after something broke on some of my own changes to make the site more readable for me, haven’t bothered to really look after the Changelog started pointing there.
 
Nice update, but still doesn’t resolve the issue until they push the fix.

@Boxless  
The session manager’s (called Pow) devs are working on it, and have a fix they are testing to ensure it doesn’t break the everything. I believe Byte[] is waiting for them to be done with testing before applying it to Philomena/Derpibooru.

@Joey  
That’s three more marks of random signout, two in the last three hours and the third about a day ago. Unless someone is deliberately fucking with me which i’m not ruling out just on the basis of ‘humans gonna human’ it’s starting to become a problem.

@Rene_Z  
Ah, you’re right, must’ve missed it on examples I was trying out… Well, in this case all’s well 👌

@Angius  

 
I don’t think anything has changed in that regard. For example >>2282548, compare old API and new API. Both have the tags including namespaces, e.g. artist:batonya12561, oc:mark wells and fanfic:off the mark. More information about tags, like description, category, etc. were never included in responses for images.

@Angius
 
Okay, so, tested it, and for those who wonder – replacing .webm with .gif in image.representations.thumb does, in fact, allow you to use a GIF.

spanish:
 
pero porque a cada rato exigen los tags, algunas veces no se que poner, pero pongo los mas importantes que son nombre del personaje, si es oc o no, si se ve algo o no (ya saben a que me refiero) deberían no ser tan especifico en ese aspecto

@Angius  
Tags don’t change too much, and classifications on them change even less often. I’d suggest caching them personally. Maybe do a daily refresh of tag data to keep coherent.