{"channel":"cities","content":"The base magic is that, when a \"checksum\" is included, there is a link to the referenced content.\r\n\r\nFor Git repositories, this might need to include a full path to the repo.\r\n\r\nBut it is (or at least should be) a way of asserting a datetime and content.\r\n\r\n----\r\n\r\nThere are two basic functions needed for *magic*.\r\n\r\nOne is << delayed-release >>.  The checksum is released now, the content is released in 1 year.\r\n\r\nThe other is << expiration >>.  The checksum is released now, the ability to \"forge\" a checksum is released in 1 year.  Now, one can have arbitrary content with the same checksum.\r\n\r\n----\r\n\r\n<xantham> as \u5c0f\u9f99\u8bed is not available, we will use JSON.\r\n<orange> well, actually ... this all seems needlessly complicated.  because of trying to get one system to do two very different things.\r\n\r\n----\r\n\r\nstep 1 is << add support for Github checksums >> to earlyversion.\r\n\r\nstep 2 is << some type of blob storage with metadata >>.\r\n\r\nonce i stop needing to tie them together, the need for *magic* dissipates.","created_at":"2025-05-07T15:46:02.313760","id":469,"llm_annotations":{},"parent_id":467,"processed_content":"<p>The base magic is that, when a \"checksum\" is included, there is a link to the referenced content.\r</p>\n<p>For Git repositories, this might need to include a full path to the repo.\r</p>\n<p>But it is (or at least should be) a way of asserting a datetime and content.\r</p> <hr class=\"section-break\" /> <p>There are two basic functions needed for <em>magic</em>.\r</p>\n<p>One is <span class=\"literal-text\">delayed-release</span>.  The checksum is released now, the content is released in 1 year.\r</p>\n<p>The other is <span class=\"literal-text\">expiration</span>.  The checksum is released now, the ability to \"forge\" a checksum is released in 1 year.  Now, one can have arbitrary content with the same checksum.\r</p> <hr class=\"section-break\" /> <p><span class=\"colorblock color-xantham\">\n    <span class=\"sigil\">\ud83d\udd25</span>\n    <span class=\"colortext-content\"> as <span class=\"annotated-chinese\" data-pinyin=\"X\u01cfAO L\u00d3NG Y\u01d3\" data-definition=\"\u5c0f\u9f99: snake (as one of the 12 Chinese zodiac animals \u751f\u8096[sheng1 xiao4]); \u8bed: (literary) to tell; to let (sb) know\">\u5c0f\u9f99\u8bed</span> is not available, we will use JSON.\r</span>\n  </span></p>\n<p><span class=\"colorblock color-orange\">\n    <span class=\"sigil\">\u2694\ufe0f</span>\n    <span class=\"colortext-content\"> well, actually ... this all seems needlessly complicated.  because of trying to get one system to do two very different things.\r</span>\n  </span></p> <hr class=\"section-break\" /> <p>step 1 is <span class=\"literal-text\">add support for Github checksums</span> to earlyversion.\r</p>\n<p>step 2 is <span class=\"literal-text\">some type of blob storage with metadata</span>.\r</p>\n<p>once i stop needing to tie them together, the need for <em>magic</em> dissipates.</p>","quotes":[],"subject":"lidgerwood, part 3: checksums and magic"}