3 ms·
That possibly works for quiet discussions, say <30 total posts. For these with high level of engagement you often get distinct subtrees of threads which have l
by playingalong 2y ago
That possibly works for quiet discussions, say <30 total posts.
For these with high level of engagement you often get distinct subtrees of threads which have little to do with each other.
For the latter the linear structure is awful.
- basil-rash 2y agoThat’s where the UI affordances come in, for instance a button on each node to hide/show all comments that are descendants of that node.
- stavros 2y agoSo a tree, but worse.
- barbarr 2y ago4chan threads are more like DAGs
- krapp 2y agoThe graph of 4chan threads are definitely cyclical, since they can include back-references.
- basil-rash 2y agoTo be cyclical they’d need to have elements in reply to a post made after they were created. Including back references is a way of adding more parents, not children.
- philosopher1234 2y agoYou can reference posts that haven’t happened yet
- basil-rash 2y agoYou are referring to providing a sequential post ID past the current latest? That is more of a quirk of their naming convention than a product feature. UUID's, for instance, would not support this, and checks could be made in either case to prevent it.
- basil-rash 2y agoWhat makes you say it’s worse?
- stavros 2y agoThe underlying conceptual structure is still a tree, but now you have to unfold it into a line, with one reply potentially having nothing to do with the one before it (because they're on very different branches).
- basil-rash 2y agoNo, the underlying structure is a DAG. I've already stated this, and that heavy UI affordances should be made to support ease of interaction with this model.