Feature overview

Option to view related posts as a tree.

Examples

parent
-child
--grandchild
--grandchild
-child

or

parent
child child
grandchild grandchild

Ideal location would be in place of the current parent/child links or on a separate page altogether, like pools. If the former, highlight the current post in some way.

Usefulness

Many child posts will have their own child posts. A blacklisted parent may have unblacklisted child posts. Being able to just click a post further in a daisy chain removes the need to open a preceding post first.

Affected

1) Every post with a parent or child(ren) or 2) an entirely new page. Since it's an option, the settings page would also need an update in the former scenario.

Edit: Tried to show a family tree using nodes for the second example. I don't care enough right now to find out how to make it display correctly.

Parent-child chains should be avoided. Such chains usually indicate a sequence of three or more images, which should be made into a pool instead of having previous pages being set as a parent, or are unnecessarily nested and should all have the same parent instead.

In either case, this may not be easy to implement or be that efficient, since it would require every viewing of a post to query details about each of its child posts to find their child posts recursively.

Parent child chains of 4 or longer should usually be a pool instead.

watsit said:
Parent-child chains should be avoided. Such chains usually indicate a sequence of three or more images, which should be made into a pool instead of having previous pages being set as a parent, or are unnecessarily nested and should all have the same parent instead.

snpthecat said:
Parent child chains of 4 or longer should usually be a pool instead.

If it were up to me, parent/child posts wouldn't exist at all. Unfortunately, a huge number of posts are linked via complex daisy chains with no pool containing them all.

watsit said:
In either case, this may not be easy to implement or be that efficient, since it would require every viewing of a post to query details about each of its child posts to find their child posts recursively.

Not unless this data was stored separately and only updated when a new post has been added into an existing tree. This would be necessary if the tree were being presented on a separate page, as a pool would.

An alternative would be to automatically add every post in large tree to a new pool titled with the root post ID. It wouldn't show how posts relate to one another, but they'd at least be grouped together on the same page.

Better yet, just allow the tree format on pool pages and let users manually determine how posts should be associated.