Found these posts

Soo, should they all have one parent for the sake of order, or be parented to the one most similiar to them, aka post #1460459 child to post #1460456 and so on.

MyNameIsOver20charac said:
Found these posts

Soo, should they all have one parent for the sake of order, or be parented to the one most similiar to them, aka post #1460459 child to post #1460456 and so on.

Would it not make sense to pool them?

wous said:
Would it not make sense to pool them?

Not my picture of how pools are to be used; it's not a sequence of images that tell a story when in the right order, just a bunch of similiar pics.

MyNameIsOver20charac said:
Not my picture of how pools are to be used; it's not a sequence of images that tell a story when in the right order, just a bunch of similiar pics.

then put them in a set

These things are bit problematic, because if you do start doing parent-child relations in way that more similar posts are linked like that, then it will turn into daisy chained mess which is much harder to navigate.

If unsure, keep one variation as parent to the rest. Ensuring that users can easily navigate to other versions is the main priority and second one is to make it as easy as possible. As child posts are ordered by ID, the list of child post will always stay the same and show thumbnails, where daisy chaining you need to start remembering what IDs as parent post is shown as ID only and you need to navigate trough several pages instead of single one.

MyNameIsOver20charac said:
Not my picture of how pools are to be used; it's not a sequence of images that tell a story when in the right order, just a bunch of similiar pics.

If there's some sort of series of pictures, pools can also be used for those even if they aren't continuation like comic would be. Simply order with the time of release instead of sequence. It's only when the pool is "pictures of character Y by artist X" or "best Y pictures" it's not supposed to exsist, as you can search first one and second one doesn't need to be available for everyone (favorites and sets are for that one).

In this case there does seem to be some level of continuation. Character is clearly going clothed -> undressing -> nude -> after sex and then have same set but with cloaca instead of breasts and pussy. So I would make pool, put clothed variations at the beginning as those are same for both, put pussy version first and cloaca version second, then parent-child similar looking pussy/cloaca posts with each other. Another reason for pooling is that artist did put couple other images in the set which aren't direct alternate versions of the main post.

Like Munkelzahn said, set could also be used, but problem is that regular users would need to go and search for the set instead of seeing it directly and in this case the main point is linking similar posts for everyone.

I see a "branching story".. or rather, the same series, with one alternative:

This is the start: post #1460444

Path 1, Humanoid: post #1460450 post #1460456 post #1460459
Path 2, Reptilian: post #1461474 post #1461477 post #1460516

now, how to tag/pool/set/denote/mark/magic/whatever this? beats me. I'd probably have two parent-chains up to the first image. but I dunno.

Oh, nice, this artist made some more. Almost picked them out from the thumbnails.

I'm at a point where I don't want to click up/down through a set of posts just to see all the variants because they've been daisy-chained. The worst part is switching tabs each time and waiting for page load to open the next post in the set: click, switch tab, wait, click, switch tab, wait, click, switch tab, wait, click, switch tab, wait... Then I need to confirm my tabs are sensibly ordered from left to right before, as in most cases, I pick out the "superior" version and close the rest. I'd rather open all variants at once.

It's especially bad when a multi-image set has, like, 4 post parented to one post, but one of those child posts has another 2 child variants not connected to the main parent. Easy to miss. Don't do that please.

SnowWolf said:
[snip for size]
This is the start:

Path 1, Humanoid:
Path 2, Reptilian:

That is one way to do it.

There's one more version: rating:q, without the dialogue in the corner.

post #1461470

The top parent should be the rating:q one with dialogue (post #1460444), the one you already picked.

Usually, the top parent should have the "most stuff" or be the earliest point of a sequence, where the child posts remove "stuff" (e.g., clothing, sound effects) or naturally progress (e.g., before sex, sex, cum). For gender variants, if the top parent isn't obvious, I might defer to how the artist presented the set in their gallery or use whichever version the artist posted first.

TL;DR Don't daisy chain. It should never be wrong to parent all the posts to a single, "top parent", but sometimes those child posts can be organized better regardless.

abadbird said:
Oh, nice, this artist made some more. Almost picked them out from the thumbnails.

I'm at a point where I don't want to click up/down through a set of posts just to see all the variants because they've been daisy-chained. The worst part is switching tabs each time and waiting for page load to open the next post in the set: click, switch tab, wait, click, switch tab, wait, click, switch tab, wait, click, switch tab, wait... Then I need to confirm my tabs are sensibly ordered from left to right before, as in most cases, I pick out the "superior" version and close the rest. I'd rather open all variants at once.

It's especially bad when a multi-image set has, like, 4 post parented to one post, but one of those child posts has another 2 child variants not connected to the main parent. Easy to miss. Don't do that please.

I'll be honest: My account was made in 2010. I'm former staff. Parent/child posts still confuse the hell out of me.

If it were up to me, I'd... actually i was gonna say reinvent the system so it operates differently, but after rambling a bit, I realized that what I'd do would be to basically use pools for everything. Pools are easy. They have an order and forward/back buttons. I understand pools. Pictures can belong to multiple pools, so that you can easily say "cloaca version" and "pussy version".

Pools are great.

parent/children... they're confusing.

I find it most intuitive to just link them all in each description but it takes longer to do. Looks really nice though.

Clean: normal
Cloaca: normal, penetration, cum version
Herm: normal, penetration, cum version

Bonus points for removing the links on the one you are currently viewing on each pic (like I did above).

Alternatively stuff like this where there's actually progression looks nice:

<<Prev | Page 17 / Textless ver. | Next>>

(taken from post #1324157)

parasprite said:
I find it most intuitive to just link them all in each description but it takes longer to do. Looks really nice though.

Bonus points for removing the links on the one you are currently viewing on each pic (like I did above).

Alternatively stuff like this where there's actually progression looks nice:

I guess this boils down the thing I said, that main goal is to just make everything as easy to navigate for user as possible, were it parent/child, pool, description or all at once. Or looking at some uploads, at least one method would be nice at least.

As we are kinda on the topic, description field is also really good to use if you want to have all possible sources in all possible ways, see post #1327473 for example as that had 7 available sources.