I guess the question to ask is, what is the most natural graph underlying a blog. I think it is the graph of internal references. Hereβs the ribbonfarm graph.
Conversation
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.
5
5
19
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?
3
1
7
The blogchain concept is something like an attempt to jury-rig an explicit graph structure as 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
1
1
6
I think you could get a bit further down this track with the notion of content-aware version histories, as in Codeq blog.datomic.com/2012/10/codeq.
1
1
1
Git is just too coarse. It can tell you that there's a new file, or that a file has changed, but you need another layer to work out what the changes mean.
1
1
2
Alternatively, really embrace the graph concept and make the individual units of content really small. Paragraphs or even sentences?
1
3
This Tweet was deleted by the Tweet author. Learn more
This Tweet was deleted by the Tweet author. Learn more

