This was suggested before by Kayako back in forum #12295 and I'm already thinking of making a help wiki called "howto:pools." But before I would lay down the ground work, and put what I have in mind into the wiki, I might ask everyone first to discuss or comment on the following, which I may put in that page later:
"Posts to be included in a pool should have a theme. This should be made obvious by the description of the page or by a common trait on the posts themselves. A pool can also be made for an image series that tell a single story or a group of images that use a common template."
"Pools cannot be used to group favorites. This already defeats the purpose of the favorites function."
"A pool can be made if a tag search cannot satisfactorily show all requisite posts to be contained in that pool, or if results from a tag search include extraneous/non-requisite posts."
"Pools with either no or problematic content, especially if all posts in a pool can be easily be found through a tag search, should be reported to the Pointless Pools thread (forum #12295)."
That's all what I have in mind right now and I may add more. For now, tell me what you think.
"Pools cannot be used to group favorites. This already defeats the purpose of the favorites function."
Try: Pools should not be used to group your favorites. Do this using the 'Add to favorites' function.
(Just to make it clearer.)
"A pool can be made if a tag search cannot satisfactorily show all requisite posts to be contained in that pool, or if results from a tag search include extraneous/non-requisite posts."
This can probably be simplified: Pools should only be made if the content can not be accurately retrieved with a regular tag search.
(Or something like that. Either way it overlaps a bit with your next point.)
I'm sure others can improve. Sometimes a simple tag search can bring up the entire contents of a pool, but the benefit the pool offers is in the ordering of those images. We should probably work that in somehow.
I'm sure others can improve. Sometimes a simple tag search can bring up the entire contents of a pool, but the benefit the pool offers is in the ordering of those images. We should probably work that in somehow.
Especially if the pool includes a doujinshi that passed quality standards or a series of comics. Yes. But sometimes, posts don't have to be ordered, especially if they're random posts that form a common theme.
Anyway, Kayako made the suggestion and made me think of making the entry because, of course, of the problem pools and the pool vandalism that we've seen in the past few months.
nanami said: Anyway, Kayako made the suggestion and made me think of making the entry because, of course, of the problem pools and the pool vandalism that we've seen in the past few months.
Whatever the wiki entry does, it will not stop people from doing this.
Look at how many problems the well written howto:comment guide fixed. None?
Granola said: Whatever the wiki entry does, it will not stop people from doing this.
Look at how many problems the well written howto:comment guide fixed. None?
It was a given that many Members would ignore the sized "Before commenting, read the how to comment guide" message that conveniently links to the howto:comment wiki entry and still bump posts with shitty 4chan one-liners and/or whatever else violates the guidelines detailed there.
That's not to say that I think nanami's idea for howto:pools is a wasted effort. The wiki entry should serve as both a help guide for users new to Pools and as set of rules for all users to follow when using Pools. Anyone abusing the Pools and breaking the established guidelines detailed there should be punished according to those guidelines.
Granola said: Whatever the wiki entry does, it will not stop people from doing this. Look at how many problems the well written howto:comment guide fixed. None?
Even if people don't abide by it, it helps a lot to have something there.
It's a lot harder to justify penalizing someone if they can legitimately say "but there weren't any rules spelled out". Get more of these guides in place and that excuse vanishes.
And not *everyone* is a jerk, of course. Some people want these how to entries because they genuinely would like to understand how things work.
I agree that the wiki should be made, don't get me wrong.
I would also like to suggest that these wikis be placed in a more obvious place. Its difficult to know that there is a wiki for such a thing if it doesn't appear right next to it.
Just like we have a howto:comment next to comments, these should be placed right next to pools, as should be the howto:tag and howto:rate be placed next to post uploading.
jxh2154 said: Even if people don't abide by it, it helps a lot to have something there.
It's a lot harder to justify penalizing someone if they can legitimately say "but there weren't any rules spelled out". Get more of these guides in place and that excuse vanishes.
Fully agree. Having rules about it justifies punishment for breaking them. As an extra bonus, more guides should lead to less stupid questions by genuinely interested posters.
jxh2154 said: I'm sure others can improve. Sometimes a simple tag search can bring up the entire contents of a pool, but the benefit the pool offers is in the ordering of those images. We should probably work that in somehow.
This quote give me another idea, somewhat as a subset for the rule "Pools should only be made if the content can not be accurately retrieved with a regular tag search."
"Image sequence sets, even if they can be found through a simple image search, can be placed into a pool for ordering, especially if each image in the set was uploaded out of order."
