Turn off force-push and have the SHA1 of the repo revision used for the build of the site in the site

[paul-hammant]

So that ...

1. a print version of a page on https://freeolabini.org/ can show the revision it was pertinent to
2. the source for the site become a living tamper-evident timeline for the episode in history

... can we ...

a) turn off force-push in the repo - protecting the master branch
b) show in the footer of each page the SHA1 used to build it.

#MerkleTreesForWorldPeace

[claucece]

Hey!

turn off force-push in the repo - protecting the master branch

I'm unaware if this happened in the past, but we can do it for sure.

show in the footer of each page the SHA1 used to build it.

Mmm.. unsure about this. I don't see why we need it to be a tamper-evident timeline for the episode in history.. can you explain why is needed?

Thanks!

[paul-hammant]

It has not happened, but the the intersection of humanity and democracy require it increasingly going forward - Merkle trees validate truth, but only of they are added to and not obliterated with each push.

Say you link to an article, and summarize it in a timeline you're creating on the site, but then add to many other pages in a hundred following commits. If you'd also tweeted the SHA1 of HEAD at intervals, then things you write in a timeline are a merkle-tree verifiable statement/claim on your part. Not a univeral-truth as such, but something you're disclosing as what you know in public, with a decent timestamp. Opposition layers can't accuse you of backdating the same thing, because the SHA1 is in public (Twitter - that y'all CANNOT back-insert) allowing the Git repo to be verifyable at any stage in the future. All without blockchain, all without decentralization as such.