{"blyg":"0.4","id":"25xx1prexhzw3hremh1a6dydst","kind":"thread","origin":"https://blyg.blygger.org/","page":"t/25xx1prexhzw3hremh1a6dydst/","author":{"name":"Venkatesh Rao","url":"https://blyg.blygger.org/"},"created":"2026-10-11T00:05:10Z","updated":"2026-10-11T00:05:11Z","version":1,"content_md":"\n# Soapbox for Blygger 0.1.2 is on WordPress.org\n\n*Released 2026-10-10 by Robert Peake, an independent client. [Soapbox for Blygger on WordPress.org](https://wordpress.org/plugins/soapbox-for-blygger/) · [source](https://github.com/cyberscribe/soapbox-blyg).*\n\nSoapbox for Blygger makes a WordPress site a blyg. Every post you publish also becomes an item, with a permanent id that survives edits, renames and moves, a new version each time its visible content changes, and withdrawal when a post goes back to draft. It needs WordPress 6.6 and PHP 7.4.\n\nIt's the client the manifest-template construct was written for (§16.6e, decision #51). WordPress serves the item and pin documents from its REST API rather than at the default paths, so the manifest says where they are, with `item` and `pin` URL templates. robertpeake.com was where that construct was exercised: a Blygger Studio node subscribed, quoted an item, and the mention verified on the WordPress side (gate G9).\n\nAt WordPress.org's request the plugin is now named Soapbox for Blygger (slug `soapbox-for-blygger`). Nothing a reader sees has changed; the manifest's `generator` now reads `soapbox-for-blygger/<version>`.\n\nLive at [robertpeake.com/blyg/](https://www.robertpeake.com/blyg/).\n\n\n\n*Releases of independent clients are announced here by hand. To comment, respond to this item from your own blyg.*\n","content_html":"<div class=\"blyg-tk-gen\"><h1>Soapbox for Blygger 0.1.2 is on <a href=\"http://WordPress.org\">WordPress.org</a></h1>\n<p><em>Released 2026-10-10 by Robert Peake, an independent client. <a href=\"https://wordpress.org/plugins/soapbox-for-blygger/\">Soapbox for Blygger on WordPress.org</a> · <a href=\"https://github.com/cyberscribe/soapbox-blyg\">source</a>.</em></p>\n<p>Soapbox for Blygger makes a WordPress site a blyg. Every post you publish also becomes an item, with a permanent id that survives edits, renames and moves, a new version each time its visible content changes, and withdrawal when a post goes back to draft. It needs WordPress 6.6 and PHP 7.4.</p>\n<p>It's the client the manifest-template construct was written for (§16.6e, decision #51). WordPress serves the item and pin documents from its REST API rather than at the default paths, so the manifest says where they are, with <code>item</code> and <code>pin</code> URL templates. <a href=\"http://robertpeake.com\">robertpeake.com</a> was where that construct was exercised: a Blygger Studio node subscribed, quoted an item, and the mention verified on the WordPress side (gate G9).</p>\n<p>At <a href=\"http://WordPress.org\">WordPress.org</a>'s request the plugin is now named Soapbox for Blygger (slug <code>soapbox-for-blygger</code>). Nothing a reader sees has changed; the manifest's <code>generator</code> now reads <code>soapbox-for-blygger/&lt;version&gt;</code>.</p>\n<p>Live at <a href=\"https://www.robertpeake.com/blyg/\">robertpeake.com/blyg/</a>.</p>\n</div>\n<div class=\"blyg-tk-gen\"><p><em>Releases of independent clients are announced here by hand. To comment, respond to this item from your own blyg.</em></p>\n</div>\n","content_hash":"sha256:a7579062d989154a4042bfacbde362df1babca34a2b5d761d5b1917ad99aed36","media":[],"transclusions":[],"generated":[{"sources":[],"model":"claude-opus-5-5"},{"sources":[],"model":"claude-opus-5-5"}],"changelog":[{"version":1,"at":"2026-10-11T00:05:11Z","note":"Soapbox for Blygger 0.1.2 released."}]}