Danbooru

Pointless Pools

Posted under General

LonelyMagnet said:

pool #3306

Too subjective, IMO. It's basically a favorites pool. +1 for deletion.

pool #10135

Redundant to quite a lot of tags, and it's a bad sign when most of the edits to a collection pool are by the same person. I'm slightly leaning towards delete, but make sure the posts in the pool are tagged properly, e.g., post #3607700 is hatching_(texture).

Also could anyone explain the difference between pool #5768 (Telling Tanlines) and pool #11746 (Unfortunate Tanlines) and why we should keep them separate?

Besides both pool descriptions being completely useless (seriously people, that's not a place to be witty or beat around the bush, the point is to explain what sort of posts belong in the pool), these pools also seem to be covered by tags. Besides sun_tattoo and the generic tanline, we have a wealth of *_tan tags for tanlines left by various garments or accessories. I'd eradicate both of them.

Updated

I would suggest keeping but merging the tan pools. Most of the images are too specific to be worth starting new tanline tags over. It seems like there was intended to be a distinction between "tans from odd outfits" and "tans from something else weird or embarrassing", but that really doesn't matter in the long run.

There are actually quite a lot of pools like that. See list of Megami issues and list of Dengeki Moeou issues. There was also an abortive attempt by user #450156 to create several Newtype pools as well, but with the exception of pool #14131 this turned out to be kind of pointless as they only have one post apiece. And then there are all the artbook and anthology pools, many of which weren't meant to be read in sequence (or even have the same artist throughout), but which we keep pooled together anyway.

I have no strong feelings about these pools myself, but for some, deleting them may mean the loss of valuable metadata regarding the original source of each image. Most of the scans in these pools are simply sourced to Yande.re, which would leave us reliant on that site for keeping track of sources.

iridescent_slime said:

In general I'm not a fan of pools based on character combinations, but I don't see how this one is any worse than older groupings like pool #4623 or pool #11430. If we're going to delete one pool of this type, we might as well get serious about it and eliminate the rest of them as well.

I am totally on board with this idea, especially with pool #11430. These kind of pools are already bending the "don't make pools just to circumvent the tag search limit" rule enough.

Since we're already on the subject — it's funny in hindsight just how prophetic forum #74289 turned out to be:

S1eth said:

...and we'll soon have the inevitable creations of the 3 fairies pool, the prismriver sisters pool, the dog/wolf character pool, the SDM family pool, the chireiden family pool, etc.
(EDIT: and the future "touhou bunny girls" pool. I'd rather we discuss all these possible future pools now BEFORE they are created)

pool #15544
pool #5206
pool #15449

I think at the least all character group pools should be converted to tags and they should have rules that a) they're only used when the full group is present (not just one person), and b) the entire picture is specifically about that group and only that group (and not just a few characters from that group incidentally being in the same picture). I don't think chartag searches are a good replacement, since there are cases where a post is very intentionally about a certain group.

We have a lot of precedent for using tags over pools for this. See other Touhou groups (Team 9), Pokemon groups (Elite Four, Team Rocket, etc), Idolmaster units (LiPPS), Girls Frontline squads (404, Anti-Rain, etc), Sailor Moon groups (Sailor Senshi, Inner Senshi, Outer Senshi). I'm certain we have more, but it's nightmare to find them since we don't have a list of them anywhere and all the pools have dumb cutesy names. A lot of these tags do need gardening though, since in many cases they're used too broadly (Pokemon tags are especially bad about this).

evazion said:

I'm certain we have more, but it's nightmare to find them since we don't have a list of them anywhere

That may be a problem for most copyrights, but there is at least a list of Pokémon pools: pool group:pokemon.

evazion said:

I think at the least all character group pools should be converted to tags and they should have rules that a) they're only used when the full group is present (not just one person), and b) the entire picture is specifically about that group and only that group (and not just a few characters from that group incidentally being in the same picture).

Sure, tags could do that job, it doesn't have to be pools. Still, it appears some of the group tags are commonly used even when a single character is incidentally somewhere in the picture. But pools are generally used when they affect the whole picture. So I guess that would be at least one big advantage of using pools.

Another separate idea would be "focus" tags. We have things like text focus and bird focus. So it may be worth discussing something like elite four focus when the image is entirely about the Elite Four. (rather than one incidental Elite Four member somewhere)

Alternatively, maybe using words like "all" or "trio" or "duo" sometimes. Like all inner senshi instead of inner senshi. The wiki of inner senshi has a few usage rules that aren't followed by the currently tagged posts. I'd prefer to lean towards using tags with a clear title that doesn't need much clarification from wikis.

BUR #2344 has been approved by @evazion.

mass update pool:kantai_collection_-_shitty_t(-shirt)_naval_base -> shitty_t-shirt_naval_base -pool:kantai_collection_-_shitty_t(-shirt)_naval_base

Reason: This pool is for the クソT鎮守府 meme. Memes should be tags. This is how memes are usually treated. Among other reasons, it allows translated tags to be used. There are many posts that should have this tag but don't because of the lack of translated tags.

EDIT: The bulk update request #2344 (forum #163868) has been approved by @evazion.

Updated by DanbooruBot