http://tilde.club/~whir/d/ 2026-10-08T14:15:24Z whir http://tilde.club/~whir/d/before-this/ 2026-10-08T00:00:00Z 2026-10-08T14:15:24Z <p>An earlier blog, <a href="http://tilde.club/~whir/q/">here</a>, will no longer be posted to nor changed. I kicked away that ladder (after climbing down). The Markdown is gone.</p> http://tilde.club/~whir/d/introducing/ 2026-10-07T00:00:00Z 2026-10-07T14:12:07Z <h2>jouissance</h2> <p>After looking at and trying too many blogging tools, many of which aren’t all that happy in a shared space like ours, I did what some in ’26 who aren’t 10× developers might try, I gave a 132-word prompt to a chatbot for its LLM to triangulate to a tool, a tool that fit my criteria better. I have good friends in both camps — strongly anti-AI and those who enthusiastically use these tools, even pay for them.</p> <p>I am on the fence and consequently will not release it in the usual way. You’re free to use the executable. Further detail about sharing the source hasn’t been thought through.</p> <h2>technically</h2> <p>It’s simple — so simple I don’t think it needs any doc.</p> <p>Nonetheless, I’ll say this much:</p> <ul> <li>run as <code>/home/whir/bin/blog</code></li> <li>It’s easy to play with, blow away, begin again. The learning curve should be quick and nearly painless. Please let me know either way</li> <li>It doesn’t do all Markdown. Tables, footnotes, math and strikethrough (at least) are not supported</li> <li>nearly 7× smaller than Zola</li> </ul> <p>The only gotcha is you are free to “misalign” web space and file space. It does not fail safe. If line 3 and 4 in <code>~/.blog/config</code> are</p> <pre><code>url = http://tilde.club/~ford/p3 out = /home/ford/public_html/a/b/c/d </code></pre> <p>you will not find your blog at that URL, it will 404.</p> <h2>extruded from the LLM</h2> <p>I haven’t tested these.</p> <p>Slugs and URLs: the slug is fixed when you create the post, so editing the title doesn’t move the URL. Renaming a file to change its date or slug creates a page at the new URL and leaves the old page in place, so unpublish with <code>p</code> first.</p> <p>Images: drop them into the output directory under the post’s slug, for example <code>public_html/blog/my-post/pic.jpg</code>, and reference them as <code></code>. Unpublishing or deleting a post leaves them there.</p> <p>Stylesheet and raw HTML: <code>style.css</code> is written once and never overwritten, so edit it freely. Raw HTML in posts passes through unescaped.</p> <p>Config changes: after editing <code>~/.blog/config</code> or <code>style.css</code>, press <code>r</code> to rewrite every page, as the status line shows.</p> <p>p.s. I’m not a developer at all.</p>