How would you reimagine blogs around graph databases as the foundation?

(Roam, Notion, Gatsby all seem to have blog like functionality in their sights but it feels like a stepchild use case relative to their core use cases of notes, wikis, collaboration, static pages) https://twitter.com/vgr/status/1200097087746011136
The key tension in a blog is between the irreversibility of the log stream in time and the evolving internal reference structure. There is a natural asymmetry as old posts don’t get updated to point to future posts that reference them.
I think codebase evolution on git has a similar natural structure. The “diff” maps to the “post” and “parent version” to “backlink”

Maybe pull request = comment?
The blogchain concept is something like an attempt to jury-rig an explicit graph structure as @tomcritchlow pointed out yesterday, but still with temporality as strictly dominant organizing principle. The basic DAG must be an approximate partial temporal order. Cycles are add-ons
You can follow @vgr.
Tip: mention @twtextapp on a Twitter thread with the keyword “unroll” to get a link to it.

Latest Threads Unrolled: