When using pools, I prefer to stay outside the search screen, just navigating in pool order by progressing to the next image in said pool. A recent change to banned images, which now only has the page state that the image was taken down, disrupts that and has me questioning what actions I should take, if any.
On a takedown page, there's only text, and nothing related to the image that used to be there functions. This includes pool navigation, so advancing to the next pool image as I normally would isn't possible here.
A search could exclude the banned images (e.g. "ordpool:5019 -status:banned"), but the pool navigation doesn't take the status exclusion from the search into consideration, so circumventing a banned image this way only works until the next banned image, at which point it has to be done again.
There's also the option of removing banned images from pools as I encounter them. However, while this makes sense for a user of common status like myself, I don't know what the current visibility levels are for users of higher permissions (who, for all I know, could see the image despite the takedown request and navigate through a pool normally in this scenario). Said users might want the banned image to remain in place.
With all that said, is there a more convenient workaround I'm unaware of? (Can I create a pool navigation that also acknowledges the status clause?) Should I remove banned images from pools, or would that end up detracting from the pool for a minority of users?