I pulled my post from earlier today. git reset –hard. It was too much, too close, and too painful… to others if read. I could feel it while I was writing it, but I went ahead and pushed the button anyway: git add, git commit, and git push from the laptop.

Behind the scenes, the machinery whirls: the git push triggers a webhook at the repository; the webhook signals out to the edge; and a listener at the edge does a git pull for the latest. To verify, lynx gopher://nolineage.com … and there it was, my previous post.

Shit. Alright, lynx gopher://localhost looks fine. git fetch and status? Fine. Login to the machine running gitea – no problem. Send a curl -X POST from here to the front? Clean response. New terminal window. Login out to the edge and netstat – the receiver is listening. tcpdump on the select interface and port? Yup, there it is.

Alright – manual execution… fails. Permissions problem in the gopherhole. It just takes a few minutes to have find run through the directory tree, flip all the right switches, and verify the view. But after all that?

If I was absolutely resolute to publish that post, these obstacles would have been challenges from the gods to test my dedication. Instead, they were a sequence of fail-safe gates: Initial here, here, and here; acknowledge that you’ve been warned, acknowledge you’re aware of the consequences, and acknowledge that you’ve decided to exercise your free will anyway.

git reset –hard

I encrypted that post and stashed it away. It was heartfelt, after all – not meant to be forgotten, just not meant to be shared – at least at this time.