WikiWe

Hashing Algo Prompt

2 min read

Create an Obsidian Templater template that implements an idempotent hashing system for document content. The template should:

  1. Ignore any content before the first header. Processing should start from the first header encountered.

  2. Process the document content block by block, where a block is defined as the content from one header to the next header or end of the document.

  3. For each block (except the last header, which is assumed to be the Footer): a. Hash the header title using SHA-256. b. Hash the content of the block using SHA-256, but first:

    • Strip out any footnotes (text matching the pattern ”[^…]“)
    • Ignore any lines that start with ”- [#]” c. Generate short hashes (first 8 characters) for both the header and content hashes.

  4. After processing each block (except the Footer), append a line in the following format:

    - [#] #YY/MM [^headerHash] / [^contentHash]

    Where:

    • YY/MM is the current year and month
    • headerHash is the short hash of the header title
    • contentHash is the short hash of the block content

  5. Ensure the process is idempotent:

    • If a hash line already exists at the end of a block, replace it instead of adding a new one.
    • Running the template multiple times should produce the same result.

  6. Ignore the content in the last header (assumed to be the Footer). Do not hash or modify this content.

  7. In the Footer section, add a table of content hashes linked to headers in the following format:

    [^contentHash]: [[#header-link|header-link]]

    Where:

    • contentHash is the short hash of the block content
    • header-link is the header text formatted as an Obsidian internal link

  8. At the end of the document (after the table in the Footer), add a hash directory in footnote format:

    [^shortHash]: #YY/MM SHA-256 hash: fullHash

    Include entries for all header and content hashes used in the document.

  9. Preserve all original document content, only adding or updating hash lines and the Footer table.

  10. Handle edge cases gracefully:

    • Empty documents
    • Documents with only headers and no content
    • Documents without a Footer section

  11. Use JavaScript for the implementation, leveraging Obsidian Templater’s capabilities.

  12. Include clear comments in the code explaining each step of the process.

  13. Optimize for performance where possible, considering that documents may be large.

Please provide the complete JavaScript code for this Obsidian Templater template, ensuring it meets all the above requirements and is ready to be used in Obsidian.

Graph View