Oddbean

But the question still stands that there's a sort of list and app designers would want to know where the top-level entry is. (Might be multiple top-levels.) Like, if I publish a book, how can I ensure that the chapters aren't listed parallel to the book?

If someone else embedded that top-level 30040, then I guess we'd have to Display both as top-level. Like, someone could print the New Testament and Old Testament as individual books, and someone else could join them into a Bible and add Luther's commentary.

That should be fine, because they are distinct articles on their own. I think a single user would be less likely to publish their incrementally growing book one in a way that clutters the feed, or the design can incentivize that behavior. Def would like to avoid the "nostr plays" type of cluttering. Viral publications could unravel something like this: 1)user posts 🔥 article 2) many users share - nothing different 3) many users edit, fork and integrate the existing article. But because these kinds are slower moving than kind1, i don't expect it to be a huge problem considering what is already being delt with. Even better is when specialized clients connected to themed relays/communities use this. Members of that community can decide on best practices for posting and writing.