ive tried adding things such as date:week and date:7_days_ago, but it has no effect on blacklist entries.
Posted under General
ive tried adding things such as date:week and date:7_days_ago, but it has no effect on blacklist entries.
Interesting question. I thought the "meta-tags" all worked for blacklists too (I've blacklisted specific post IDs before, like id:12345 and that works fine), but I tested date:week in my blacklist on its own line and nothing happened as well.
not possible. the client-side blacklist only supports a very limited set of metatags like fav:me.
lafcadio said:
not possible. the client-side blacklist only supports a very limited set of metatags like fav:me.
darn... I was trying to blacklist hyper_muscles and it can get posts which arent a severe example of the tag, and might be something I would like. theres probably some number of mistags too. im blacklisting by -score:>=150 to try and get posts people like, but sadly that means newer posts can get caught in the blacklist.
lafcadio said:
not possible. the client-side blacklist only supports a very limited set of metatags like fav:me.
The full list of supported metatags is here: https://e621.net/help/blacklist#metatags
It's not as limited as it used to be. But yes, not everything is supported.
It's theoretically possible to add support for the dates – the blacklist has access to that information.
But it's a lot of work, which simply does not seem worth it. The vast majority of users have very simple blacklists.
dinbyy said:
darn... I was trying to blacklist hyper_muscles and it can get posts which arent a severe example of the tag, and might be something I would like. theres probably some number of mistags too. im blacklisting by -score:>=150 to try and get posts people like, but sadly that means newer posts can get caught in the blacklist.
My only suggestions are to either set the score part to a negative so new posts are less likely to be affected, or look into perhaps a more specific related tag you can narrow down on to blacklist or exclude.
cinder said:
The full list of supported metatags is here: https://e621.net/help/blacklist#metatags
It's not as limited as it used to be. But yes, not everything is supported.It's theoretically possible to add support for the dates – the blacklist has access to that information.
But it's a lot of work, which simply does not seem worth it. The vast majority of users have very simple blacklists.
Sorry for the necro, but I figure this is better than creating another thread with the same topic, and I wanted to add something.
I expected the date metatags to work when used as a blacklist item because the score:<n metatag does. Does this mean that there are two separate and different implementations of the parsing and application of metatags, one for blacklists and one for searches?
subtlereminder said:
Sorry for the necro, but I figure this is better than creating another thread with the same topic, and I wanted to add something.
4 days is not a necro, the general consensus is >1 year or >6 months
I expected the date metatags to work when used as a blacklist item because the score:<n metatag does. Does this mean that there are two separate and different implementations of the parsing and application of metatags, one for blacklists and one for searches?
Yes. Blacklists are client-side.
subtlereminder said:
I expected the date metatags to work when used as a blacklist item because the score:<n metatag does. Does this mean that there are two separate and different implementations of the parsing and application of metatags, one for blacklists and one for searches?
Yes, this is correct.
The search is handled server-side in Ruby and passed on to ElasticSearch.
The blacklist is handled client-side in JavaScript.
cinder said:
Yes, this is correct.The search is handled server-side in Ruby and passed on to ElasticSearch.
The blacklist is handled client-side in JavaScript.
Huh.
Hey, does that mean I could hack on it in my browser? I mean, I'm obviously going to try, but I'm curious if there are any guides or docs, or if you're aware of any stumbling blocks I should know about.