Comment by apitman

Do they really need to work that differently though? It seems to me that almost all of them can be represented as trees of text entries. Blog+comments, HN/reddit threads, Stackoverflow QAs, DMs, Discord/Slack, forums. These are all just text trees with optional attachments and/or links to other content (images and videos etc). Why not build that tree structure into the protocol (all you need is 1 parent and 0+ children for each entry)?