Deprecating minimum and maximum score

@Nuke  
Is this really the place to risk political baiting?

 
A better explanation would be:
 
– If you don’t want images with a score higher than 500 to be displayed, you would add this to your complex filter: score.gt:500  
– If you don’t want images with a score lower than 25 to be displayed, you would add this to your complex filter: score.lt:25

@Background Pony #2713  
Updated, thanks.

@byte[]  
Aw crap. Sorry about that, thanks. I am okay with reading manuals, but very bad at finding them.

I always thought these were pointless. If everyone set a filter that took out everything with a score below 100 no zeros would ever be seen. Nothing would ever be upvoted and your feed would be empty.

@Lavender Love
 
Good Point!

@Lavender Love  
I personally only ever used it to filter out images with a negative score.
 
@byte[]  
Glad to help! :)

EDIT: Derp. Nevermind!

I think I’m happy with this change.
 
I knew the previous setting existed but I couldn’t figure out how to work it when I did. If I understood what’s going on, these are now tags we can use to search and simply add to our filters?  
(Tests) this is amazing!

tl;dr Users are too dumb to understand search syntax, so we will remove it entirely.

@Background Pony #4470  
We’re not removing any search syntax

@Background Pony #4470  
Before saying something with “TL:DR”, you might to check, if the thing that you’re saying is actually the summary of the stuff. Otherwise it might sound stupid.
 
We’re not removing syntax. We are removing this
 

 
Because adding syntax “score.gt:(number)” for minimum score. And “score.lt(number)” for maximum number on complex filter do the same function.

This change has now been deployed.

Why would you remove this feature, its a feature that Ive been using for years and is one of the most useful on this site! Ive had it set so I don’t have to see anything below a score of +20. You say I’m supposed to insert some code into something called a “complex filter” what even is that? I tried putting “score.lt:25” as a tag in my custom filter but that does nothing. Why do people have to remove a simple feature and replace it with a more complex and less user friendly one?

Ive figured out what the complex filter is (I think) but now that I’ve inserted the proper code “score.lt:20” in my case, now the are pages are mostly just row after row of “tag hidden” images! I thought there were supposed to go away! How can I get them to disappear!?

@byte[]  
So how do I make these images actually go away like the did with the old system?

@下げ髪  
You put the score filter in your complex spoiler expression, which spoilers images.
 
I edited your filter to place it in the complex filter expression, which removes them from image results.

@byte[]  
Jesus wept! see how complicated things get when you start expecting others to just know how to code for the site! You said the old system was causing confusion, and few people even knew it was there, but now how is a new user going to know how to hide low (or high) scoring images in this site? Will they know to look for this thread here to explain it to them? What about a new user 5 years from now when this thread is dead and buried!? I’m certainly too stupid to have figured it out it was theoretically possible in the new system had I not already been doing so in the old system. But if I’d never known the feature existed before I would have been at a complete loss.

You certainly have a point how, in all likelihood, nearly nobody will even know about being able to filter images by score once this thread fades into obscurity.
 
A better idea to consider would be to add some kind of button to the complex filter section that allows the user to generate the correct tag for score filtering in the correct place, so that less tech-savvy people can make use of it without having to look into the wall of text that the Search Syntax Guide is and somehow figure out that they CAN put the score tags into their filters. Heck, some kind of system that makes creating a complex filter more approachable in general would be helpful as well.

@下げ髪  
The point of this change wasn’t just to remove duplicate functionality - it was also to fix several filtering related bugs, which depend on this change.
 
Derpibooru has a lot of functionality that most users have no idea exists. Ultimately, there isn’t a lot we can really do about that, because despite what Linus says, most users really are confused by functionality.
 
Users also often suffer acute banner blindness, often ignoring almost every element on the page except what they are concerned with. For an example of this, users with 2FA enabled often email us saying that they did not realize they were supposed to write down their backup codes when they signed up, even though there is a very prominent warning on the 2FA page saying that you will permanently lose access to your account if you don’t make a hard copy of your backup codes.
 
There also these regular gems that pop up in the forums, demonstrating just how acute the banner blindness of users is.
 
This is not to say we’re not trying to let people know how you should use the site. For example, on the search page, there’s a query builder, that has, among other things, score. There is a question mark next to the search box which thoroughly explains search syntax. There are multiple question and answer threads in the forums for how to build complex filters, both by users and staff.
 

 
We can’t make everyone pay attention to what we’re trying to tell them, but not for lack of trying.

I put score.lt:300 into the complex filter but all it’s doing is spoilering images below that score. How do I remove them from the page entirely?

Never mind I figured it out.

@Cyan Lightning  
My feed is now getting low quality images pouring in, and it’s a hassle to search it each time? Yes you could do it manually before, but why remove it? The filtering makes it easy to see the better stuff (And yes, I know that if no one sees the low fresh posted images, it can’t get the high ratings. Well aware of that.). Honestly, this wasn’t a good move. You took away an automatic process and now force everyone to do it manually, most not knowing how.

@Zheben  
No functionality was removed, just moved. Please read the thread, as in the first post I describe how to modify your filter to filter by score.
 
And on that note, I added score.lt:25 to your complex filter. Feel free to adjust it.

@byte[]  
Can show a step-by-step thing or something, because I am still lost on how to set up and change this. That’s my main complaint, before it was so easy, but now I can’t even find out HOW to put these without having to learn code to do it.