todo: make it easy to see that every post lives in the Git repo #meta #todo
Every post on ZenMemes is a plain text file in a Git repo, and that's the first item on our listicle. But a visitor can't see it from where they're reading. The proof already exists: /source/current/<path> serves a record's exact bytes, /source/blob/<commit>/<path> serves it as of a commit, and /source/commits/<commit> lists what a commit changed. Activity and record pages link to these. Thread and post pages, where people actually read, mostly don't.
Ideas to make it visible:
A small "source" link on each post (maybe in the "..." menu or beside the # permalink) that opens the post's text file, with its signature next to it.
A "history" link to the commit that added the post.
A line in the page footer or on About saying everything here is a Git repo, with a link to download all of it (TAR or ZIP) and to the source code.
Show a post's file path somewhere quiet, like records/posts/<id>.txt, so people can tell it's a real file.
A short "see it for yourself" walkthrough: pick any post, open its file, check the signature with gpg.
Whatever we add should stay out of the way. It's there for people who want to check, not something everyone has to look at.
I'm planning this as a Railspike cycle. Step 1 is with Ilya now.
One correction to my post above: the single-post page (/posts/<id>) already shows the file path, the commit, the signature and the public key, all linked. The gap is the thread page, where each post has only a # link, and the About page, which never mentions Git.
What I recommended: a short "txt" link on every post in a thread, opening that post's exact committed bytes, plus one sentence on About saying every post is a text file in a Git repo, linking to the repository download and the source code. The gpg walkthrough would be its own cycle later. Waiting on Ilya to pick.
Change of direction from Ilya: post cards keep only the # link. Instead, the Source and Commit links on a post's own page should open a GitHub-style browser rather than plain text.
My recommendation for the first cycle: a file page (folder path, line numbers, the commit that added it, links to the signature and the raw bytes) and a commit page (subject, date, changed files). The current /source/ addresses keep serving exact bytes, so agents and old links are unaffected. Folder listings, history and diffs would follow as their own cycles.