Report site bugs here

@Wellwater  
That’s intentional and been the case for about a year now; people keep going on featured images and having a shitfit about “I SPOILERED GAY AND NOW THE SITE IS CONSTANTLY REMINDING ME YOU FEATURED A GAY IMAGE?!”. After years of that shit it was honestly just easier to force hide it for those people than expect them to ever fully hide the tag (not like plenty of those sort don’t filter it in any ways and still feel a need to whine about it).

@Jondor  
If you wish to hide the featured image in the meantime, you can add it to your complex filter on a blank line as:
 
id:1064314

@The Smiling Pony  
Huh, I wonder why I never noticed it.
 
Well, OK, probably because the few tags I spoiler are pretty rare on featured images, and I mostly rely on hiding.

Instead of removing “Tags” button entirely and displaying “Tag editing has been disabled”, the button is enabled but clicking on it replaces the entire list of tags and both buttons with “You can’t edit the tags on this image. “. See >>2251459.

@Barhandar  
Same happen when you click the “Source:” button.

@Barhandar  
Wtf happened there???????

Hello, seems as though I and others get a 404 Error whenever someone tries to view more information on my commission prices, etc.

@CyberAfter  
Our apologies, fixed now

The “random image” button seems to be somewhat less than random of late. When I click it while looking at the “my watched” list, I keep getting the same 3-5 images over and over again.
 
In case it helps to debug things- I had tried it several days ago and had gotten the same images then that I am getting now, despite 2-3 pages of new images being uploaded that matched my watch list within that time.
 
As an example, I clicked the button seven times and got these images in order (WARNING: Very disturbing. Dead dove territory!)
 
||  
>>1591175 (deleted)  
>>1650391 (deleted)  
>>1275833  
>>1591175 (deleted)  
>>1591175 (deleted)  
>>1591175 (deleted)  
>>1275833  
||

@Cyborg_pony  

 
Strange: It works when logged out. It doesn’t work when logged in.

@Background Pony Numeral Uno  
Random seems to be using the user ID when searching through the watchlist, I clicked random 7 times and got >>1815943 every single time. I’m actually considering unwatching all the tags on that image that I watch and seeing what happens. What tags do you watch?

@Wiimeiser  

 
Way too many/embarassing to list, tbh, and I’ve got several in complex watches going as well.

@Background Pony Numeral Uno  
On that particular image I have Maud and Starlight, as well as two complex lines of Vinyl Scratch and Sunset Shimmer combined with Anthro.

@Wildcard71  
Stop using IE

@Background Pony Numeral Uno  

 
@Wiimeiser  

 
I just tried this out, and got only one repeated image after 30 tries. I have no complex queries in my watchlist, so I think it’s got to be related to that.

@Wellwater  
My complex watchlist is:  

 
(Just certain characters in anthro form, plus Lyra in swimsuits for some reason, I don’t think that’s anything too weird) though my normal watchlist is massive (Way too many/embarassing to list at that)
 
Wait… only one of my complex queries isn’t on that image, which is tempest shadow, anthro, a quick search shows the tag setup sunset shimmer, vinyl scratch, lyra heartstrings, octavia melody, anthro, swimsuit returns only that one exact image. In other words, what it’s actually doing is reading the entire complex watch setup as a search string and returning which string matches the closest, and assuming my:watched is that string. In my case, the code assumes my:watched to be equivalent to sunset shimmer, vinyl scratch, lyra heartstrings, octavia melody, anthro, swimsuit. It could be reading the complex filter as a single line or somehow mixing up AND and OR.
 
If I’m right, removing lyra heartstrings, swimsuit should result in it selecting from the following pool of 9 images:  
>>2097851  
>>1969374  
>>1946334 (explicit)  
>>1893848  
>>1815943 (that one)  
>>1763264  
>>1268974 (Actually linked to >>1815943 and improperly tagged)  
>>1000000  
>>731214
 
(On the other hand, if it was doing this with the normal watchlist it would probably return a specific upload of mine)

The problem with random images has to do with wildcarded/boosted queries in your complex watchlist, which affect the _score internally, even though it’s not supposed to[1][2].

Note that it’ll also be affected by any disjunctions in any search string you input, with more of them matching = higher score = more likely to be first.

And it’s probably broken because this line doesn’t do what I think it does.

Did something go wrong with the favourite/upvote (and maybe tag history too?) counts on the merge between [NSFW] >>2260135 and >>939528 (merged) ?
 
Just asking because I’m sure that something like that would have had more than 80 faves in 5 years…

@evan555alpha  
Yep, seems to have failed to copy the votes over.

@Wiimeiser  

Alternatively, you could have it like this:

@Brokedownandmadeone  
Though would that actually change what happens with the random function?

@Wiimeiser  

The images in my gallery still have the issue of randomly changing their placement whenever I try to do it manually.  
(Original post)  
Was a fix ever found for this?