Disgustingly Adorable pool: Should be a tag?

This pool is really really huge. The bloat is extreme, really. I am thinking it might be better served as a tag than a pool.

And having paged through the pools a bit, Dat Ass and Badass are also really huge.

See forum #34668
Tags must not be subjective, so there are pools that cover those.

It's really too subjective to be a tag.

I'd think the whole bloat matter can be bypassed by simply doing a pool:903 search and looking at the images that way.

dat ass, do a pool:1214 search.
badass, do a pool:1277 search.

The Disgustingly Adorable pool is almost pointless at this point, people add anything that's even remotely cute.

That aside, this thing with the clocks seems to be getting worse:

gnome7 - 12 minutes ago
gnome7 - 6 minutes ago
s1eth - 14 minutes ago

It messes up with the Mark all read button occasionally too (threads keep showing up as unread) and it's quite annoying.

I'm generally against the deletionist stance we seem to be adopting towards pools. "It's really big" shouldn't be a sufficient reason for deletion.

I disagree, most emphatically.

"Disgustingly Adorable" is an extremely subjective term (really, it's two subjective terms in one), and with tags being intended as an indexing tool based on objectively observable elements and metadata, that would not be the right way to go.

Besides, the last thing we need is a tug-of-war with users fighting over whether post number X is cute/adorable or not.

Shinjidude said:
I'm generally against the deletionist stance we seem to be adopting towards pools. "It's really big" shouldn't be a sufficient reason for deletion.

I don't think pool size is even considered valid reason for deletion. Rather, it's the bloating of pools - the overuse of pools due to loose (or mis-)interpretation of the pools' respective guidelines - that is a problem, and that's not grounds for pool deletion so much as for pool gardening.

Alright, that makes sense. It seemed like something worth considering.

It is. It's just that what these pools need at this point is coding. Until then there's not much to do to cure them.

Fred1515 said:
It messes up with the Mark all read button occasionally too (threads keep showing up as unread) and it's quite annoying.

You need to use Mark all? I find as soon as I open any thread, all other threads are also marked as read.

And yes, this is why we don't have a "cute" tag.

wanchan said:
I find as soon as I open any thread, all other threads are also marked as read.

Oh, so it's not just me?

It only tracks the most recently read post so if you're not reading from the bottom up it will mark everything read on your first click.

There also seems to be an issue I have noticed where if that weird date issue pops up, and an older post shows up after an older one, that the recently read date doesn't update properly, and the thread doesn't get marked as read. At least I think that's what's happening.