This feature request has similar goals to another one I made, but involves the blacklist instead of the search bar. Here's the search bar version for reference: https://e621.net/forum_topics/27360
.
.
.
Requested feature overview description.
Being able to limit specific (and all) tags using favcount and/or score—in the blacklist. Not ALL metatags (unless you really want to), but at least one or both of those in particular.
I know the score and favcount can be set in a search, but it will only apply for that specific search run. And I assume the blacklist is only tied to tags and not metatags, but this would be a cool feature in my opinion.
Default posts page, nothing in the search bar, but your blacklist has:
tag1 -favcount:>200
tag2 -score:>150
So tag1 only appears anywhere if the favcount is over 200, and tag2 only appears anywhere if the score is over 150.
Also, in addition to specific tags, you could have this feature active for everything else, like:
-favcount:>100
-score:>50
You get the idea. Basically everywhere you go on the site, you only see things if your requirements are met. Both the specific ones and the 'everything else' stuff.
.
.
.
Why would it be useful?
1.) It would be great for keeping everything up to personal standards 'constant.' Instead of keeping multiple searches bookmarked with the requirements you prefer.
2.) Would be really helpful if you're trying to slow the endless flow of new stuff (so you aren't behind, having to catch up too often, or wasting too much time as it is).
3.) Would help guarantee you’d never see anything with a favcount or score below zero. Not all of those posts 100% deserve it, but eh. Most do. So better off not seeing them.
4.) Maybe you only use the site for a handful of tags and block everything else, but if some posts have too high a favcount/score to miss out on, you can allow those through at least.
5.) It may help people by realizing how much time they were wasting digging through sub-par stuff trying to find things they’d actually look at. Even your favorite tags have crap.
6.) If you want less work to do blacklisting things in general, this feature could basically shrink the site. The higher your 'broad' requirements, the less often you'll have to add to the blacklist.
.
.
.
What part(s) of the site page(s) are affected?
The Settings page and all pages with images that have favcounts/scores.
.
.
.
Me poking holes in my own feature request and solving them.
- This relies on the majority bothering to fav and upvote things, so there’s a chance that you’d be blacklisting things you would like but currently don’t have enough upvotes to meet your requirements. But I’m sure too many people make use of favs and upvotes for that to be a problem. If it’s a post you’d like, chances are it’ll eventually get enough to become visible to you :P
- I still don't know if favcount or score usually 'means more' in terms of quality for the majority around here (that's probably in the realm of opinion). My personal guess would be favcount, since I usually see that number being bigger than the score. So if you can only make one of the two work in the blacklist, I suppose try making it work for favcount at least. I could be wrong though :]
- Without also setting 'broad' metatags for all tags, there's a chance your requirements set for specific tags might lead to you not seeing them until they've passed Page 1. For this I'd just bookmark a default post page far enough away from 1 so new stuff has time to make the requirements. That's only on the default posts page, though. But I'd just use the broad metatags so everything slows down. Like a slow-motion feature in a chat with way too many people to read what anyone's saying. Is that possible to do for an entire site like this? That'd be cool; this place is fast. Anyway...
- One slight problem I can see happening is you put a broad metatags on your blacklist, go to default page (or any page, really), and it's just a handful of thumbnails to click on, and everything else has been hidden. But they're still THERE because they count as apart of the images-per-page counter, creating this issue. For this I have two solutions, one being more doable than the other:
Solution A: So for an extreme example if your blacklist has a broad metatag like favcount:>1000 (greater than a thousand), do a search run with '-favcount:<1000' So everything with less than a thousand on the favcount won't even occur for the images-per-page count to get used up in the first place. Then just bookmark it. Problem solved; at least on that particular search run you use.
Solution B: As an option or update somewhere down the line, make the blacklist not just hide posts, but work like a negative search (like '-whatever') so even if your blacklist is all over the place or just has one big broad metatag, every page will still have a full set of images packed to the limit you set it to. I think I may have already suggested this feature before. It would be great, imo.
.
.
.
Me coming up with a different approach.
If making something new is easier than updating the current setup, another thing you could do is make a 'second blacklist' just for broad and tag-specific metatags.
So things like favcount, score, width, height, freakin' comment count. The things you normally type in the search bar to organize results. That stuff :U
So you can have the regular blacklist, and then this new thing that does fun extra stuff if you want to use it. Maybe call it 'Constant Metatag Settings' or something like that.
.
.
.
EDIT:
Thanks to bitWolfy for some info on both my feature requests in this thread: https://e621.net/forum_topics/27380
Updated
