Topic: [Feature] Having a blacklist tag

Posted under Site Bug Reports & Feature Requests

Description
I had another forum post which pretty much told me already, that the blacklist operates on my device but I thought maybe it's still possible.
Being able to having the blacklisted posts not only hide but don't even show. Maybe something like an individual tag called blacklist or making it possible to + - from the blacklist rows which would be similar to be able to use ( ) in the search bar

Why would this be usefull?
I show 100 posts per page and I have sometimes (often enough to be disturbing) 50 posts not showing because of blacklist, which makes my page effectivly to 50 posts page. This could be solved with a blacklist tag.
Also when I filter out the most significant case for example to thin out this problem I also filter out my exceptions normaly set in the blacklist like for example (male/male -female -herm)

Which part/s of the page/s would be affected?
If a blacklist tag is possible:
Everything which would be affected with a new tag, too, but the implementation is surely another level than just a new tag
If + - becomes available it would be same or similar to be able to use ( ) in the search bar

Theoretically, results from the following pages can be loaded and appended to the current page until the specified number of non-blacklisted results were shown.

This could probably be done for all possible queries, but efficiency would vary. In particular queries using order: metatag. I don't remember the exact details. But, what you want is to be able to use the after=POSTID api (getting the exact '100 next results after this particular post') and not the page=PAGENO api; after=POSTID is not available with certain order: settings.

Apps which provide 'infinite scroll' on e621 also have to cope with this, AFAICS what you are describing is like a weirdly limited version of infinite scroll (in the reality of how it works, not the outside appearance). I think there are also browser addons which do similar things.

The chance of getting this on the site itself rather than through an app or addon is almost zero though IMO -- things that abstract away real page boundaries tend to be a bit dodgy in practice.

An entirely different strategy is to just up your posts/page from 100 to 200. Works for me, but I understand people browsing from their phone using mobile data would want to avoid this.

Updated

First thx for the reply ;D

Adding results till x would make the problem a great bit smaller but wouldn't solve it. They would be still there. So you couldn't use the next button for example. Also like you said if the paid price is performance and if that gets to disturbing levels, it would've be from the frying pan to the fire.

Changing my posts/page would be disturbing for me if I have almost non blacklisted posts. 100 is a nice number of posts for me :)

I already thought that this will most likely not be possible but asking can't hurt and maybe someone already has another solution like you.
My hope lies know in the search bar being able to understand ( )

I did thank you for the reply but I also liked the inside and ideas. So thank you again :D

savageorange said:
This could probably be done for all possible queries, but efficiency would vary.

in the general case it's not really feasible;
consider that hypothetically you could run a search which yields 1000 pages of results, then apply a blacklist which happens to filter out every result except one appearing on page 1000.

you have to draw the line at some point, so currently that's at one page (i.e. up to 250 results at a time).

bipface said:
in the general case it's not really feasible;
consider that hypothetically you could run a search which yields 1000 pages of results, then apply a blacklist which happens to filter out every result except one appearing on page 1000.

you have to draw the line at some point, so currently that's at one page (i.e. up to 250 results at a time).

Doesn't seem like a significant problem to me. Draw the line at whatever, remake the 'next pages' list accordingly (say you got 20 results, from 10 pages starting at page 1, then the first 'next page' item would be displayed as '11', it would get results from pages 11..21)
Sure, the user will not be perfectly happy, but it's better to show them the limits of the abstraction than to pretend it doesn't exist.

savageorange said:
Doesn't seem like a significant problem to me. Draw the line at whatever, remake the 'next pages' list accordingly (say you got 20 results, from 10 pages starting at page 1, then the first 'next page' item would be displayed as '11', it would get results from pages 11..21)

the problem is you'd have to download 2500 post records to determine that there are 20 non-blacklisted results among them.
in my extreme example you'd have to download 250000 records to find the first result

What I'm saying is that isn't necessarily a problem, you just tell the user to deal with it rather than continuing to look for more records, at whatever point you decide is reasonable. If 2500 is too much, make it less; like I said, make it whatever. Insisting to get exactly 100 records with this strategy is a pointless example of 'the great is the enemy of the good'. You give up at some point and that point should be empirically determined, rather than preemptively dismissed because perfect results aren't practical to achieve, and if the user still insists on perfect results then they should be dismissed because THEY aren't practical. You can still probably get 'a lot closer to the desired # of results' without working too hard, in many cases.

What you mention WOULD be an obstacle for implementing it in the site itself, since then it is applied to all users, not only those who specifically go out of their way to get it. But I was never suggesting to implement it in the site itself.

I understood the/one problem of this method thankfully but being not aware of the downsides of this method is quiet possible I believe. Therefore the continuation of the idea can be profitable for new readers.

Also I agree with the case that there are reasonable and unreasonable requests and/or persons. If the unreasonable part stays after stating the problems you can discard the idea or quit arguing with that person.

You can still probably get 'a lot closer to the desired # of results' without working too hard, in many cases.

While I also agree that you need to be ready to make compromises but where you have to make a compromise is something subejctiv. Also in this specific problem showing the # of results is the main problem but not the only aspect. You still can't use the next or previous buttons effectively because the blacklisted posts show up and also you would be able to use such a tag in other ways too. How big those problems/advantages are is something subjectiv again.
Formost what we do is a discussion which can help in the decision making. The decision making itself is done by the appropriat persons.
But I agree, too, this problem will most likely not realized.

  • 1