diff options
author | bryan newbold <bnewbold@robocracy.org> | 2024-08-12 00:00:52 -0700 |
---|---|---|
committer | bryan newbold <bnewbold@robocracy.org> | 2024-08-12 00:00:52 -0700 |
commit | 941256cc5f89d5e7d66981abb61f33993e3597c4 (patch) | |
tree | 947ef4bd1635bf374f9e39b05e447d86e7cdcfcb /posts/merkle-design.md | |
parent | b841907a5e9cb1f9e6e45a43800690f7abf4ee5b (diff) | |
download | bnewnet-941256cc5f89d5e7d66981abb61f33993e3597c4.tar.gz bnewnet-941256cc5f89d5e7d66981abb61f33993e3597c4.zip |
typos
Diffstat (limited to 'posts/merkle-design.md')
-rw-r--r-- | posts/merkle-design.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/posts/merkle-design.md b/posts/merkle-design.md index b388dab..707e194 100644 --- a/posts/merkle-design.md +++ b/posts/merkle-design.md @@ -15,7 +15,7 @@ My interest in these systems is as infrastructure for the commons of cultural and intellectual works: making it cheap and easy to publish content that becomes easily accessible and woven in to the web of reference and derivative works. From my work at the Internet Archive collecting Open Access -publications and datasets, I have a particular interest in dereferencable links +publications and datasets, I have a particular interest in dereferenceable links (and/or citations) that will work in the future, [wp-merkle]: https://en.wikipedia.org/wiki/Merkle_tree @@ -27,7 +27,7 @@ system: the wire. If every distinct file can be identified by only a single, reproducible name, then discovery, indexing, and de-duplicaiton is made easier. If the same file can end up with different names, then that file might be -transfered or stored separately by default; this creates pressure for the +transferred or stored separately by default; this creates pressure for the application layer to support the concept of "many identifiers for the same file", and requires additional coordination at scale. @@ -94,7 +94,7 @@ folks love to think about re-inventing "everything" on top of such a system. I think this is because git supplies specific semantic features people love, while being deeply entangled with files and file systems. Computer engingeering is All About Files, and git is both made out of files (look in .git; it's -simple files and directories all the way down!) and accomodating files. +simple files and directories all the way down!) and accommodating files. Consider: |