Merge branch 'main' of github.com:svemagie/blog
This commit is contained in:
svemagie
@@ -0,0 +1,80 @@
|
||||
---
|
||||
date: 2025-05-02T00:00:00.000Z
|
||||
title: Anarchistische Anthropologie
|
||||
category:
|
||||
- on/politics/anarchism
|
||||
- on/mutualaid
|
||||
gardenStage: cultivate
|
||||
visibility: public
|
||||
aiTextLevel: "0"
|
||||
updated: 2026-03-22T13:02:42.539Z
|
||||
syndication:
|
||||
- https://blog.giersig.eu/articles/anarchistische-anthropologie/
|
||||
- https://bsky.app/profile/did:plc:g4utqyolpyb5zpwwodmm3hht/post/3mhnckm474u2v
|
||||
webmentionResults:
|
||||
sent: 0
|
||||
failed: 0
|
||||
skipped: 1
|
||||
details:
|
||||
sent: []
|
||||
failed: []
|
||||
skipped:
|
||||
- target: https://bsky.app/profile/did:plc:g4utqyolpyb5zpwwodmm3hht/post/3mhnckm474u2v
|
||||
reason: No webmention endpoint found
|
||||
timestamp: 2026-03-22T10:44:13.275Z
|
||||
webmentionSent: true
|
||||
mpUrl: https://blog.giersig.eu/articles/anarchistische-anthropologie/
|
||||
permalink: /articles/anarchistische-anthropologie/
|
||||
---
|
||||
|
||||
## Anarchistische Anthropologie: Warum der Vorwurf der Naivität fehlgeht
|
||||
|
||||
Anarchistinnen und Anarchisten werden gemeinhin als weltfremd wahrgenommen, als Träumer, die glauben, Menschen könnten ohne Gesetze und Polizei, Staaten und Hierarchien friedlich koexistieren. Dieses Bild hält jedoch einer genaueren Betrachtung nicht stand. Die bedeutendsten Vordenker des Anarchismus – Michail Bakunin, Peter Kropotkin, Errico Malatesta und viele andere – entwickelten früh ein erstaunlich realistisches Menschenbild: geprägt durch Bedürfnisse, Umwelt und Veränderungsfähigkeit. Nicht nur zeitgenössische Anarchisten, sondern auch Wissenschaftler verschiedener Disziplinen untermauern dieses Menschenbild.
|
||||
|
||||
## Was Anarchist:innen über den Menschen dachten
|
||||
|
||||
Anarchistisches Denken basiert auf einem einfachen Konzept: **Der Mensch ist ein soziales Wesen**. Obwohl wir grundlegende Bedürfnisse nach Nahrung, Schutz und soziale Nähe haben, sind unser Lebensstil, unsere Denkweise und unsere Handlungen nicht dadurch determiniert. Vielmehr sind sie veränderlich und werden durch unsere Erfahrungen und die gesellschaftlichen Strukturen, in denen wir leben, geprägt.
|
||||
|
||||
David Graeber betonte stets, dass Freiheit und Selbstbestimmung nicht in Isolation, sondern in reziproken Beziehungen verwirklicht werden. In seinem Werk „Fragments of an Anarchist Anthropology“ (Graeber, 2004) schreibt er: „The ultimate, hidden truth of the world is that it is something that we make, and could just as easily make differently.“ Es ist die zentrale anarchistische Überzeugung, dass gesellschaftliche Ordnungen nicht naturgegeben sind, sondern das Resultat von Entscheidungen und Handlungen sind. Daraus schließt die Möglichkeit, bestehende Strukturen zu hinterfragen und alternative Formen des Zusammenlebens zu gestalten, die auf Kooperation, Gleichheit und gegenseitiger Hilfe basieren.
|
||||
|
||||
Peter Kropotkin betonte, dass sich Menschen nicht nur durch Wettbewerb, sondern vor allem durch gegenseitige Hilfe entwickelt haben. Für ihn war Kooperation kein Ideal, sondern eine überlebenswichtige Strategie, die tief in der Geschichte der Mens
|
||||
chheit verwurzelt ist (Kropotkin, 1902). Er stützt seine Thesen auf biologische und ethnologische Studien, die zeigen, dass Tierarten mit ausgeprägter kooperativer Verhaltensweise oft erfolgreicher überleben als solche mit rein wettbewerbsorientierten Strukturen.
|
||||
|
||||
Luigi Galleani und Errico Malatesta wiesen darauf hin, dass Fähigkeiten und Wünsche keine festen Größen sind. Sie verändern sich im Laufe der Zeit, je nach den Umständen und den Erfahrungen, die Menschen als Gemeinschaft machen (Malatesta, 1891). Sowohl individuelle als auch kollektive Entwicklungen werden durch Faktoren wie Bildung, sozialem Umfeld, kulturellen Einflüssen und technologischen Fortschritten geprägt. Menschen lernen und passen sich an, was zu einer dynamischen Entwicklung ihrer Fähigkeiten und Wünsche führt.
|
||||
|
||||
## Zwischen Konflikt und Gemeinschaft, Macht und Organisation
|
||||
|
||||
Die anarchistische Perspektive auf die menschliche Natur ist nicht idealistisch. Sie geht davon aus, dass wir zu positiven und negativen Handlungen fähig sind, wie z. B. Fürsorge und Aggression. Malatesta beschrieb dies als einen ständigen Kampf zwischen dem Drang zu herrschen und der Fähigkeit zur Solidarität (Malatesta, 1891). Kropotkin zeigte in seinem Werk „Gegenseitige Hilfe“, dass diese beiden Seiten der menschlichen Natur in allen Gesellschaften vorkommen, wobei die Umstände bestimmen, welche Seite vorherrscht (Kropotkin, 1902).
|
||||
|
||||
Charlotte Wilson und andere anarchistische Theoretiker:innen betonten bereits Ende des 19. Jahrhunderts, dass selbst autoritäre Gesellschaftssysteme auf Kooperation beruhen. Wilson (1887) argumentiert, dass jede Form autoritärer Herrschaft aktive Zusammenarbeit voraussetzt, um bestehende Machtstrukturen aufrechtzuerhalten. Kooperation bildet somit nicht nur ein anarchistisches Ideal, sondern die fundamentale Bedingung jeder sozialen Ordnung – autoritäre Systeme zentralisieren sie, während freiheitliche Gesellschaften sie autonom entfalten lassen. Auch Hannah Arendt hebt hervor, dass Macht auf kollektiver Unterstützung beruht und nicht allein durch Zwang existiert:
|
||||
|
||||
> Macht entsteht nur dort, wo Menschen sich zusammenschließen und gemeinsam handeln (Arendt, 1970).
|
||||
|
||||
David Graeber hebt dazu hervor, dass viele Formen von sozialer Ordnung historisch ohne zentrale Autorität oder staatliche Gewalt existierten, was die Flexibilität und Vielfalt menschlicher Organisationsformen unterstreicht (Graeber, 2011). Auch James C. Scott betont in „The Art of Not Being Governed“ (2009), dass Gesellschaften oft bewusst dezentral organisiert werden, um staatlicher Kontrolle zu entgehen
|
||||
|
||||
> Die Abwesenheit des Staates ist nicht gleichbedeutend mit Chaos, sondern kann eine bewusste soziale Strategie sein (Scott, 2009).
|
||||
|
||||
Diese Perspektiven verdeutlichen, dass Kooperation und Organisation grundlegende Merkmale des menschlichen Zusammenlebens sind, die in unterschiedlichsten politischen und sozialen Kontexten zum Tragen kommen. Robert Sapolsky liefert in „Behave: The Biology of Humans at Our Best and Worst“ (2017) fundierte Argumente, die diese Thesen stützen. Sapolsky betont den Einfluss von Umweltfaktoren auf biologische Grundlagen, was die Wechselwirkung von Genetik und sozialem Umfeld unterstreicht. Seine Analysen zur Neurobiologie von Aggression und Fürsorge zeigen, dass Menschen sowohl zu positiven als auch negativen Handlungen fähig sind – abhängig vom Kontext und den sozialen Strukturen.
|
||||
|
||||
## Warum Anarchist:innen Hierarchien ablehnen
|
||||
|
||||
Die Kritik der Anarchist:innen richtet sich primär gegen Strukturen, die negatives Verhalten begünstigen. Staatliche Gewalt, wirtschaftliche Ausbeutung und soziale Kontrolle fördern Eigennutz, Machtmissbrauch und Entfremdung. Dies geschieht nicht etwa aufgrund einer angeborenen menschlichen Schlechtigkeit, sondern weil diese Systeme negatives Verhalten systematisch belohnen (Scott, 1998).
|
||||
|
||||
Die Antwort darauf ist nicht Chaos, sondern eine alternative Gesellschaftsform: Netzwerke freiwilliger Zusammenarbeit, in denen niemand über andere herrschen kann. Anstelle von Institutionen, die Macht konzentrieren, fordern sie Strukturen, die Gleichheit, Verantwortung und Selbstbestimmung ermöglichen (Graeber, 2004).
|
||||
|
||||
## Fazit: Wer ist hier wirklich naiv?
|
||||
|
||||
Anarchist:innen werden als Träumer abgetan. Wer sich jedoch eingehender mit ihren Ansichten auseinandersetzt, erkennt, dass ihr Menschenbild alles andere als naiv ist. Es basiert auf empirischer sorgfältiger Beobachtung, historischen Erkenntnissen und einer tiefgreifenden Skepsis gegenüber der Vorstellung, dass Herrschaft jemals von Vorteil sein könne. Der wahre Irrglaube liegt nicht bei den Anarchist:innen, sondern bei jenen, die an die Möglichkeit einer gezähmten Macht glauben.
|
||||
|
||||
## Literaturverzeichnis
|
||||
|
||||
* Arendt, H. (1970). *Macht und Gewalt*. München: Piper.
|
||||
* Galleani, L. (1925). *The End of Anarchism?* Übersetzt von Max Sartin. Oakland: AK Press.
|
||||
* Graeber, D. (2004). *Fragments of an Anarchist Anthropology*. Chicago: Prickly Paradigm Press.
|
||||
* Graeber, D. (2011). *Debt: The First 5,000 Years*. Brooklyn: Melville House.
|
||||
* Kropotkin, P. (1902). *Mutual Aid: A Factor of Evolution*. London: Heinemann.
|
||||
* Malatesta, E. (1891). *Anarchy*. Übersetzt von Vernon Richards. London: Freedom Press.
|
||||
* Sapolsky, R. M. (2017). *Behave: The Biology of Humans at Our Best and Worst*. New York: Penguin Press.
|
||||
* Scott, J. C. (1998). *Seeing Like a State: How Certain Schemes to Improve the Human Condition Have Failed*. New Haven: Yale University Press.
|
||||
* Scott, J. C. (2009). *The Art of Not Being Governed: An Anarchist History of Upland Southeast Asia*. New Haven: Yale University Press.
|
||||
* Wilson, C. (1887). *Social Democracy and Anarchism*. In: *Freedom*, Juli 1887.
|
||||
@@ -4,9 +4,8 @@ title: For the Love of Obsidian and IndieWeb
|
||||
summary: "I spent a few hours building a bridge between my favourite writing tool and my self-hosted corner of the web. Here is what came out of it: an Obsidian Micropub plugin with IndieAuth, and a Digital Garden living alongside my blog."
|
||||
category:
|
||||
- on/memex
|
||||
- smallweb/dev
|
||||
- indieweb
|
||||
- dev
|
||||
- smallweb/indieweb
|
||||
visibility: Public
|
||||
ai:
|
||||
- - 'textLevel: "0"'
|
||||
@@ -39,7 +38,7 @@ webmentionResults:
|
||||
reason: No webmention endpoint found
|
||||
timestamp: 2026-03-14T17:24:52.339Z
|
||||
webmentionSent: true
|
||||
updated: 2026-03-21T13:19:54.058Z
|
||||
updated: 2026-03-22T08:52:13.966Z
|
||||
syndication:
|
||||
- https://bsky.app/profile/did:plc:g4utqyolpyb5zpwwodmm3hht/post/3mh22kjy5d227
|
||||
- https://blog.giersig.eu/articles/for-the-love-of-obsidian/
|
||||
@@ -52,70 +51,70 @@ mpUrl: https://blog.giersig.eu/articles/for-the-love-of-obsidian/
|
||||
permalink: /articles/for-the-love-of-obsidian/
|
||||
---
|
||||
|
||||
There is a version of the web that most people never see. No algorithms, no growth hacking, no engagement metrics. Just people writing on their own domains, linking to each other, publishing in open formats that anyone can read. It has a name **the IndieWeb** and once you find it, it is very hard to go back to anything else.
|
||||
|
||||
I have been running my own site for a while. Powered by [Indiekit](https://getindiekit.com/), it receives posts via the [Micropub](https://www.w3.org/TR/micropub/) protocol, stores them as Markdown files, and publishes them through Eleventy. I can write from any Micropub-capable client, publish to my own domain first, and syndicate out to Bluesky or Mastodon afterwards. POSSE “Publish on your Own Site, Syndicate Elsewhere” as the IndieWeb calls it.
|
||||
|
||||
The missing piece was my beloved [Obsidian](https://obsidian.md/).
|
||||
|
||||
## Where I Actually Write
|
||||
|
||||
Obsidian is where my thinking lives. Notes, drafts, research, half-formed ideas, links I want to remember, an archive of articles, podcasts, movies I enjoyed - all of it ends up in a local vault of Markdown files. I have been using it long enough that it has become genuinely hard to think outside of it. The graph view, the backlinks, the way you can just follow a thread of thought without worrying about structure fits the way my brain works.
|
||||
|
||||
The problem is that publishing from Obsidian to an IndieWeb blog involves too many steps. Copy text, paste it somewhere, add frontmatter, upload images, submit. Every extra step is a reason not to publish. Friction kills to flow of writing.
|
||||
|
||||
There is an [existing plugin called obsidian-microblog](https://github.com/otaviocc/obsidian-microblog) that publishes to Micro.blog specifically. But Micro.blog, while lovely, is not my stack. I wanted something that would talk to any Micropub endpoint - including my own Indiekit instance, of course.
|
||||
|
||||
## Building the Plugin
|
||||
|
||||
The plugin lives at [github.com/svemagie/obsidian-micropub](https://github.com/svemagie/obsidian-micropub). It is written in TypeScript, uses the Obsidian plugin API, and implements the full Micropub spec for creating and updating posts. The Plugin is fully Co-Authored by Claude, I just assisted.
|
||||
|
||||
The core of it is straightforward: read a note’s frontmatter, map the properties to Micropub’s vocabulary, POST them to your endpoint. The interesting parts were the edges.
|
||||
|
||||
**Image handling.** When a note contains local images — `![[photo.jpg]]` syntax — the plugin finds them, uploads them to your media endpoint first, replaces the local references with the returned URLs, and only then sends the post. You never have to think about it.
|
||||
|
||||
**Post types.** Micropub supports a whole vocabulary of post types beyond just articles. A bookmark has `bookmark-of`. A like has `like-of`. A reply has `in-reply-to`. The plugin reads these from frontmatter in either camelCase (`bookmarkOf`) or hyphenated (`bookmark-of`) and builds the right Micropub payload for each type. The entire range of IndieWeb post types is covered: articles, notes, photos, bookmarks, likes, replies, reposts.
|
||||
|
||||
**Updates.** Once a post is published, the plugin writes the resulting URL back into the note’s frontmatter as `mp-url`. Publish the same note again and it sends an update request instead of creating a duplicate. The note stays the canonical source of truth.
|
||||
|
||||
## The Authentication Problem
|
||||
|
||||
This was the hard part.
|
||||
|
||||
Logging into an IndieWeb site uses [IndieAuth](https://indieauth.net/), an OAuth 2.0 profile built on top of your own domain. The flow looks like this: you enter your site URL, the client discovers your authorization endpoint, opens a browser window, you log in with your blog password, and get redirected back with an access token. The same flow iA Writer uses when you connect it to a Micropub endpoint.
|
||||
|
||||
Implementing this in a desktop app (Obsidian runs on Electron) runs into a fundamental problem: OAuth requires a redirect URI — a URL the auth server will send the code back to. On the web, that is easy. In a desktop app, you need somewhere for the browser to redirect *back to*.
|
||||
|
||||
The naive approach is to spin up a local HTTP server on a random port (`http://127.0.0.1:PORT/callback`). But it fails immediately when the auth server is remote: Indiekit fetches your `client_id` URL server-side to get app metadata, and `127.0.0.1` is not reachable from the cloud. The auth server returns an error before the user even sees the login screen.
|
||||
|
||||
The solution was a GitHub Pages relay. The plugin’s `client_id` is `https://svemagie.github.io/obsidian-micropub/` - a real, publicly accessible URL that Indiekit can fetch to get the app name and icon. The `redirect_uri` is `https://svemagie.github.io/obsidian-micropub/callback` - same host, which satisfies Indiekit’s validation. The callback page is a few lines of JavaScript that reads `?code=…&state=…` from the URL and immediately forwards to `obsidian://micropub-auth?code=…&state=…`.
|
||||
|
||||
Obsidian handles custom URI schemes natively. The plugin registers `obsidian://micropub-auth` as a protocol handler, receives the code, exchanges it for a token via PKCE, and the sign-in is complete. The whole flow takes about ten seconds and feels exactly like signing in to iA Writer.
|
||||
|
||||
## A Digital Garden in the Blog
|
||||
|
||||
While working on the plugin, it made sense to also add something I had been wanting for a while: a [Digital Garden](https://maggieappleton.com/garden-history).
|
||||
|
||||
A garden is a different metaphor from a blog. A blog is like a stream: posts flow past in reverse chronological order, finished and sealed. A garden is a space you tend over time. Notes are planted, cultivated, questioned, repotted when they need restructuring. The emphasis shifts from *when* something was written to *how developed* the thinking is.
|
||||
|
||||
I use Obsidian tags for this: `#garden/plant`, `#garden/cultivate`, `#garden/question`, `#garden/repot`, `#garden/revitalize`, `#garden/revisit`. The plugin maps these to a `garden-stage` Micropub property, and the blog renders them as colourful badges: a small seedling icon for a newly planted thought, a question mark for something still open, a refresh icon for something that needs revisiting.
|
||||
|
||||
There is a dedicated `/garden/` page that groups posts by stage, so you can see what is actively growing, what is dormant, and what is being actively restructured. It fits well alongside the chronological blog - the same posts, but viewed through a different perspective.
|
||||
|
||||
The two things together - publishing directly from Obsidian with a single command, and being able to mark a post as a living document rather than a finished one - change how I think about writing publicly. The bar is lower, which is good. A seedling thought shared is always better than a perfect thought kept private.
|
||||
|
||||
## What It Feels Like
|
||||
|
||||
I am writing this post in Obsidian. It is the first post using this Ecosystem :-)
|
||||
|
||||
The frontmatter at the top has a `gardenStage: cultivate` field, because this is an idea I am actively working through rather than a finished piece. When I run the publish command, it will go to my Indiekit instance, get saved as Markdown, and appear on the blog. If I add something later, I run the command again and it updates the existing post.
|
||||
|
||||
This is what the IndieWeb promises: you own the tools, the data, and the publishing pipeline. You are not dependent on any platform’s continued existence or willingness to keep hosting your old posts. The words live on your server, in your format, under your control.
|
||||
|
||||
It took a few hours of work, fighting OAuth edge cases, debugging IndieKit’s endpoint discovery, figuring out Eleventy’s Tailwind JIT pipeline for the garden badges. The usual stuff. But on the other side of it is a workflow that genuinely gets out of the way and lets me think and write.
|
||||
|
||||
That is worth a lot.
|
||||
|
||||
* * *
|
||||
|
||||
There is a version of the web that most people never see. No algorithms, no growth hacking, no engagement metrics. Just people writing on their own domains, linking to each other, publishing in open formats that anyone can read. It has a name **the IndieWeb** and once you find it, it is very hard to go back to anything else.
|
||||
|
||||
I have been running my own site for a while. Powered by [Indiekit](https://getindiekit.com/), it receives posts via the [Micropub](https://www.w3.org/TR/micropub/) protocol, stores them as Markdown files, and publishes them through Eleventy. I can write from any Micropub-capable client, publish to my own domain first, and syndicate out to Bluesky or Mastodon afterwards. POSSE “Publish on your Own Site, Syndicate Elsewhere” as the IndieWeb calls it.
|
||||
|
||||
The missing piece was my beloved [Obsidian](https://obsidian.md/).
|
||||
|
||||
## Where I Actually Write
|
||||
|
||||
Obsidian is where my thinking lives. Notes, drafts, research, half-formed ideas, links I want to remember, an archive of articles, podcasts, movies I enjoyed - all of it ends up in a local vault of Markdown files. I have been using it long enough that it has become genuinely hard to think outside of it. The graph view, the backlinks, the way you can just follow a thread of thought without worrying about structure fits the way my brain works.
|
||||
|
||||
The problem is that publishing from Obsidian to an IndieWeb blog involves too many steps. Copy text, paste it somewhere, add frontmatter, upload images, submit. Every extra step is a reason not to publish. Friction kills to flow of writing.
|
||||
|
||||
There is an [existing plugin called obsidian-microblog](https://github.com/otaviocc/obsidian-microblog) that publishes to Micro.blog specifically. But Micro.blog, while lovely, is not my stack. I wanted something that would talk to any Micropub endpoint - including my own Indiekit instance, of course.
|
||||
|
||||
## Building the Plugin
|
||||
|
||||
The plugin lives at [github.com/svemagie/obsidian-micropub](https://github.com/svemagie/obsidian-micropub). It is written in TypeScript, uses the Obsidian plugin API, and implements the full Micropub spec for creating and updating posts. The Plugin is fully Co-Authored by Claude, I just assisted.
|
||||
|
||||
The core of it is straightforward: read a note’s frontmatter, map the properties to Micropub’s vocabulary, POST them to your endpoint. The interesting parts were the edges.
|
||||
|
||||
**Image handling.** When a note contains local images — `![[photo.jpg]]` syntax — the plugin finds them, uploads them to your media endpoint first, replaces the local references with the returned URLs, and only then sends the post. You never have to think about it.
|
||||
|
||||
**Post types.** Micropub supports a whole vocabulary of post types beyond just articles. A bookmark has `bookmark-of`. A like has `like-of`. A reply has `in-reply-to`. The plugin reads these from frontmatter in either camelCase (`bookmarkOf`) or hyphenated (`bookmark-of`) and builds the right Micropub payload for each type. The entire range of IndieWeb post types is covered: articles, notes, photos, bookmarks, likes, replies, reposts.
|
||||
|
||||
**Updates.** Once a post is published, the plugin writes the resulting URL back into the note’s frontmatter as `mp-url`. Publish the same note again and it sends an update request instead of creating a duplicate. The note stays the canonical source of truth.
|
||||
|
||||
## The Authentication Problem
|
||||
|
||||
This was the hard part.
|
||||
|
||||
Logging into an IndieWeb site uses [IndieAuth](https://indieauth.net/), an OAuth 2.0 profile built on top of your own domain. The flow looks like this: you enter your site URL, the client discovers your authorization endpoint, opens a browser window, you log in with your blog password, and get redirected back with an access token. The same flow iA Writer uses when you connect it to a Micropub endpoint.
|
||||
|
||||
Implementing this in a desktop app (Obsidian runs on Electron) runs into a fundamental problem: OAuth requires a redirect URI — a URL the auth server will send the code back to. On the web, that is easy. In a desktop app, you need somewhere for the browser to redirect *back to*.
|
||||
|
||||
The naive approach is to spin up a local HTTP server on a random port (`http://127.0.0.1:PORT/callback`). But it fails immediately when the auth server is remote: Indiekit fetches your `client_id` URL server-side to get app metadata, and `127.0.0.1` is not reachable from the cloud. The auth server returns an error before the user even sees the login screen.
|
||||
|
||||
The solution was a GitHub Pages relay. The plugin’s `client_id` is `https://svemagie.github.io/obsidian-micropub/` - a real, publicly accessible URL that Indiekit can fetch to get the app name and icon. The `redirect_uri` is `https://svemagie.github.io/obsidian-micropub/callback` - same host, which satisfies Indiekit’s validation. The callback page is a few lines of JavaScript that reads `?code=…&state=…` from the URL and immediately forwards to `obsidian://micropub-auth?code=…&state=…`.
|
||||
|
||||
Obsidian handles custom URI schemes natively. The plugin registers `obsidian://micropub-auth` as a protocol handler, receives the code, exchanges it for a token via PKCE, and the sign-in is complete. The whole flow takes about ten seconds and feels exactly like signing in to iA Writer.
|
||||
|
||||
## A Digital Garden in the Blog
|
||||
|
||||
While working on the plugin, it made sense to also add something I had been wanting for a while: a [Digital Garden](https://maggieappleton.com/garden-history).
|
||||
|
||||
A garden is a different metaphor from a blog. A blog is like a stream: posts flow past in reverse chronological order, finished and sealed. A garden is a space you tend over time. Notes are planted, cultivated, questioned, repotted when they need restructuring. The emphasis shifts from *when* something was written to *how developed* the thinking is.
|
||||
|
||||
I use Obsidian tags for this: `#garden/plant`, `#garden/cultivate`, `#garden/question`, `#garden/repot`, `#garden/revitalize`, `#garden/revisit`. The plugin maps these to a `garden-stage` Micropub property, and the blog renders them as colourful badges: a small seedling icon for a newly planted thought, a question mark for something still open, a refresh icon for something that needs revisiting.
|
||||
|
||||
There is a dedicated `/garden/` page that groups posts by stage, so you can see what is actively growing, what is dormant, and what is being actively restructured. It fits well alongside the chronological blog - the same posts, but viewed through a different perspective.
|
||||
|
||||
The two things together - publishing directly from Obsidian with a single command, and being able to mark a post as a living document rather than a finished one - change how I think about writing publicly. The bar is lower, which is good. A seedling thought shared is always better than a perfect thought kept private.
|
||||
|
||||
## What It Feels Like
|
||||
|
||||
I am writing this post in Obsidian. It is the first post using this Ecosystem :-)
|
||||
|
||||
The frontmatter at the top has a `gardenStage: cultivate` field, because this is an idea I am actively working through rather than a finished piece. When I run the publish command, it will go to my Indiekit instance, get saved as Markdown, and appear on the blog. If I add something later, I run the command again and it updates the existing post.
|
||||
|
||||
This is what the IndieWeb promises: you own the tools, the data, and the publishing pipeline. You are not dependent on any platform’s continued existence or willingness to keep hosting your old posts. The words live on your server, in your format, under your control.
|
||||
|
||||
It took a few hours of work, fighting OAuth edge cases, debugging IndieKit’s endpoint discovery, figuring out Eleventy’s Tailwind JIT pipeline for the garden badges. The usual stuff. But on the other side of it is a workflow that genuinely gets out of the way and lets me think and write.
|
||||
|
||||
That is worth a lot.
|
||||
|
||||
* * *
|
||||
|
||||
The plugin is open source: [github.com/svemagie/obsidian-micropub](https://github.com/svemagie/obsidian-micropub). It works with any Micropub endpoint, not just Indiekit. If you run your own IndieWeb site and use Obsidian, I would be happy to hear whether it works for you. If you want to develop it, too!
|
||||
|
||||
@@ -4,13 +4,23 @@ title: Memex Chat - Obsidian Plugin I built for myself
|
||||
summary: Memex Chat is an Obsidian plugin that lets you chat with your vault using Claude AI with proper context retrieval, not just keyword search.
|
||||
category:
|
||||
- dev
|
||||
- indieweb
|
||||
- on/memex
|
||||
gardenStage: revisit
|
||||
visibility: Public
|
||||
aiTextLevel: "1"
|
||||
aiTextLevel: "2"
|
||||
aiCodeLevel: "2"
|
||||
aiTools: Claude
|
||||
webmentionResults:
|
||||
sent: 0
|
||||
failed: 0
|
||||
skipped: 0
|
||||
details:
|
||||
sent: []
|
||||
failed: []
|
||||
skipped: []
|
||||
timestamp: 2026-03-21T20:20:27.043Z
|
||||
webmentionSent: true
|
||||
updated: 2026-03-22T09:14:22.055Z
|
||||
mpUrl: https://blog.giersig.eu/articles/memex-chat-obsidian-plugin-i/
|
||||
permalink: /articles/memex-chat-obsidian-plugin-i/
|
||||
---
|
||||
|
||||
@@ -9,7 +9,7 @@ category:
|
||||
- dev
|
||||
gardenStage: cultivate
|
||||
visibility: Public
|
||||
updated: 2026-03-21T16:48:18.034Z
|
||||
updated: 2026-03-22T09:14:51.507Z
|
||||
syndication:
|
||||
- https://bsky.app/profile/did:plc:g4utqyolpyb5zpwwodmm3hht/post/3mh3mbhauf42o
|
||||
- https://blog.giersig.eu/articles/thinking-in-public/
|
||||
@@ -38,345 +38,344 @@ mpUrl: https://blog.giersig.eu/articles/thinking-in-public/
|
||||
permalink: /articles/thinking-in-public/
|
||||
---
|
||||
|
||||
## Core Concept
|
||||
|
||||
**Thinking in Public** is the practice of making your thinking process – not just finished conclusions – visible. It means:
|
||||
|
||||
* Publish **seedling ideas**, not just polished essays
|
||||
* Show **uncertainty** and **open questions** explicitly
|
||||
* Make **iterations visible** (Garden Stages)
|
||||
* Allow **reader feedback** on incomplete thoughts
|
||||
* Treat your blog as an **extended mind**, not a portfolio
|
||||
|
||||
The opposite: perfectionism-driven publishing. “I only publish when it’s finished.” This is **risk-averse** and **isolating**.
|
||||
|
||||
* * *
|
||||
|
||||
## Why It Matters
|
||||
|
||||
### 1. Authenticity
|
||||
|
||||
Finished thoughts are often polished, sales-like, optimized. Unfinished thoughts are **real thoughts** – with questions, doubts, contradictions.
|
||||
|
||||
Readers can distinguish: “Okay, this is a well-considered opinion” vs. “This is an experiment, take a look.”
|
||||
|
||||
### 2. Faster Iteration Loop
|
||||
|
||||
If you have to wait until “finished”, the feedback latency is weeks or months. If you publish-while-thinking:
|
||||
|
||||
```
|
||||
Day 1: Publish #garden/plant (seedling)
|
||||
Day 3: Reader comment → new perspective
|
||||
Day 5: Update to #garden/cultivate
|
||||
Day 10: Publish #garden/revitalize (new insights)
|
||||
Day 30: Promote to #garden/evergreen (stable, reference-worthy)
|
||||
```
|
||||
|
||||
This is **resonance-driven**, not archive-driven.
|
||||
|
||||
### 3. Lower Barrier to Writing
|
||||
|
||||
> “A seedling thought shared is always better than a perfect thought kept private.”
|
||||
|
||||
Every additional requirement (“It must be finished”) is a **reason not to publish**. Thinking in Public removes this barrier.
|
||||
|
||||
### 4. Building in Public
|
||||
|
||||
Not just ideas, but **processes**: How I built the plugin, what problems I solved, which are still open.
|
||||
|
||||
Readers don’t just see “the result”, but also “how people actually develop.”
|
||||
|
||||
* * *
|
||||
|
||||
## The Garden Metaphor
|
||||
|
||||
Implemented with [Digital Garden](https://maggieappleton.com/garden-history) stages:
|
||||
|
||||
```
|
||||
🌱 #garden/plant → Brand new thought, just emerged
|
||||
🌿 #garden/cultivate → Active thinking, developing
|
||||
❓ #garden/question → Unresolved, asking for input
|
||||
⚙️ #garden/repot → Restructuring, reframing
|
||||
🔄 #garden/revitalize → Old idea, new life
|
||||
🌲 #garden/evergreen → Mature, stable, foundational (reference material)
|
||||
```
|
||||
|
||||
This makes **development stage visible** without saying “this is bad” or “this is good”.
|
||||
|
||||
An old idea can become relevant again. A seedling can lie dormant for years. A cultivated thought can mature into **evergreen reference material**. That’s **okay and transparent**.
|
||||
|
||||
* * *
|
||||
|
||||
## Understanding the Stages
|
||||
|
||||
### 🌱 Plant
|
||||
|
||||
A brand new thought, barely formed. Hypothesis-stage. “I’m wondering about…”
|
||||
|
||||
**Characteristics**:
|
||||
|
||||
* Low barrier to publish
|
||||
* Likely to change significantly
|
||||
* Invites early feedback and discussion
|
||||
* Short half-life
|
||||
|
||||
### 🌿 Cultivate
|
||||
|
||||
Active development. You’re thinking through it, refining, testing against reality.
|
||||
|
||||
**Characteristics**:
|
||||
|
||||
* Regular updates
|
||||
* Growing clarity but still evolving
|
||||
* Reader input shapes direction
|
||||
* “Works in progress” feeling
|
||||
|
||||
### ❓ Question
|
||||
|
||||
Deliberately unresolved. You’re asking for help, missing pieces, or exploring contradictions.
|
||||
|
||||
**Characteristics**:
|
||||
|
||||
* Explicitly unfinished
|
||||
* Invites expertise
|
||||
* May stay this way indefinitely (that’s okay)
|
||||
* High reader engagement potential
|
||||
|
||||
### ⚙️ Repot
|
||||
|
||||
Restructuring. The idea was good but needs new framing, different context, or fundamental reorganization.
|
||||
|
||||
**Characteristics**:
|
||||
|
||||
* Shows evolution of thinking
|
||||
* Breaks old patterns
|
||||
* Vulnerable moment (might fail)
|
||||
* Growth through friction
|
||||
|
||||
### 🔄 Revitalize
|
||||
|
||||
Returning to an old idea with fresh perspective. New relevance, new connections, new maturity.
|
||||
|
||||
**Characteristics**:
|
||||
|
||||
* Acknowledges time passing
|
||||
* Shows how thinking evolved
|
||||
* Often triggered by external event
|
||||
* Second (or third) life for an idea
|
||||
|
||||
### 🌲 Evergreen
|
||||
|
||||
Mature, stable, foundational. Reference material. This thought has been tested, refined, and stands on its own merit.
|
||||
|
||||
**Characteristics**:
|
||||
|
||||
* Unlikely to change fundamentally
|
||||
* Serves as reference/foundation for other ideas
|
||||
* High evergreen value (useful months or years later)
|
||||
* Can still be updated, but updates are minor refinements
|
||||
* Often becomes a “hub” for related posts
|
||||
* Attracts consistent traffic and citations
|
||||
|
||||
**When to promote to Evergreen**:
|
||||
|
||||
* Thought has been through plant → cultivate → revitalize cycle
|
||||
* Stability: hasn’t needed major updates in 3+ months
|
||||
* Utility: others reference it, it appears in multiple contexts
|
||||
* Maturity: feels foundational, not provisional
|
||||
* Clarity: explanations are clear enough for newcomers
|
||||
|
||||
* * *
|
||||
|
||||
## How It Changes Reader Relationship
|
||||
|
||||
**Traditional Blog**: “Author publishes finished thought. Reader reads. Maybe comments. Static.”
|
||||
|
||||
**Thinking in Public**: “Author works in public. Reader watches process. Reader contributes. Post evolves. Reader sees their input mattered. Some thoughts become trusted reference material.”
|
||||
|
||||
This isn’t just technically different. It’s **culturally** different:
|
||||
|
||||
* Less “author as authority”
|
||||
* More “author + reader as collaborative thinking”
|
||||
* Posts are **conversations**, not broadcasts
|
||||
* Some conversations crystallize into **reference material**
|
||||
|
||||
* * *
|
||||
|
||||
## Practical Mechanics
|
||||
|
||||
### In Obsidian + obsidian-micropub
|
||||
I wrote a [Obsidian Plugin](https://blog.giersig.eu/articles/memex-chat-obsidian-plugin-i/) which helps me publish from Obsidian to this micropub blog.
|
||||
|
||||
```yaml
|
||||
---
|
||||
title: Some Half-Formed Idea
|
||||
tag: garden/cultivate
|
||||
excerpt: "I'm exploring..."
|
||||
---
|
||||
|
||||
## Initial Thoughts
|
||||
[...]
|
||||
|
||||
## Questions
|
||||
- What about X?
|
||||
- Does this connect to Y?
|
||||
- Still unclear: Z
|
||||
```
|
||||
|
||||
**Publish** → Blog shows with 🌱 badge. RSS reader sees `garden-stage: plant`.
|
||||
|
||||
Later:
|
||||
|
||||
```yaml
|
||||
tag: garden/cultivate
|
||||
```
|
||||
|
||||
**Update** → Post evolves. History visible.
|
||||
|
||||
Eventually:
|
||||
|
||||
```yaml
|
||||
tag: garden/evergreen
|
||||
excerpt: "A foundational exploration of..."
|
||||
```
|
||||
|
||||
**Promotion** → Visual indicator changes, post moves to reference section.
|
||||
|
||||
### In the Blog Template
|
||||
|
||||
* Post shows **clear stage indicator**
|
||||
* Maybe: “Last updated X days ago”
|
||||
* Maybe: “Open questions” section highlighted
|
||||
* Evergreen posts: Prominent placement, “Related posts” section
|
||||
* Maybe: Toggle to show **edit history**
|
||||
* Maybe: “Promoted to evergreen on [date]”
|
||||
|
||||
### Filtering & Discovery
|
||||
|
||||
Readers might want:
|
||||
|
||||
```
|
||||
/blog/all → All stages mixed
|
||||
/blog/seeds → Only plants (emerging ideas)
|
||||
/blog/cultivating → Active thinking
|
||||
/blog/evergreen → Reference material only
|
||||
/blog/timeless → Evergreen + question posts (always relevant)
|
||||
```
|
||||
|
||||
* * *
|
||||
|
||||
## Tensions & Trade-offs
|
||||
|
||||
### “Won’t this make me look less authoritative?”
|
||||
|
||||
**Short answer: No.** The opposite:
|
||||
|
||||
* Transparency builds trust
|
||||
* Showing uncertainty is **more credible** than false certainty
|
||||
* Readers respect “I’m thinking through this” more than “Here’s the truth”
|
||||
* Having **evergreen material** shows maturity and reliability
|
||||
|
||||
**Long answer**: Authority doesn’t come from “I never change my mind”. It comes from “I think carefully and adjust when I learn something. And some of my thinking stands the test of time.”
|
||||
|
||||
### “What if someone quotes my half-formed idea out of context?”
|
||||
|
||||
**Risk**: Yes. **Mitigation**:
|
||||
|
||||
* Clear garden stage badges
|
||||
* License/note: “This is work-in-progress thinking”
|
||||
* If it matters, you update the post and readers see the change
|
||||
* **Evergreen posts have explicit “stable” indicator** – these are safe to quote
|
||||
|
||||
**Real mitigation**: The garden stage IS the context.
|
||||
|
||||
### “Doesn’t this create noise?”
|
||||
|
||||
Fair question. If you publish **everything**, yes.
|
||||
|
||||
But you filter by stage. A reader interested in “reference material” sees only evergreens. A reader interested in “emerging ideas” sees only plants.
|
||||
|
||||
**It’s signal, not noise – because it’s labeled.**
|
||||
|
||||
### “When should I promote to evergreen?”
|
||||
|
||||
Don’t rush. A thought becomes evergreen through:
|
||||
|
||||
* **Time passing** (stability test)
|
||||
* **Repeated usefulness** (does it serve you and others?)
|
||||
* **Standing up to challenge** (did criticism refine it or break it?)
|
||||
* **Foundational role** (does it anchor other ideas?)
|
||||
|
||||
Some thoughts never become evergreen. That’s okay. Not all thinking needs to be permanent.
|
||||
|
||||
* * *
|
||||
|
||||
## Historical Context
|
||||
|
||||
* **My Blog** (2000s): “Publish when finished”
|
||||
* **Twitter** (2010s): “Publish everything instantly”
|
||||
* **Thinking in Public** (2020s): “Publish with context about development stage”
|
||||
* **Thinking in Public + Evergreen** (2025+): “…and let the best thinking crystallize”
|
||||
|
||||
It’s a **synthesis**:
|
||||
|
||||
* Blogger rigor (think before publish)
|
||||
* Twitter immediacy (don’t wait for perfect)
|
||||
* Garden transparency (show the state)
|
||||
* **Librarian wisdom** (some things deserve to last)
|
||||
|
||||
* * *
|
||||
|
||||
## Examples in the Wild
|
||||
|
||||
* [For the Love of Obsidian and IndieWeb](https://blog.giersig.eu/articles/for-the-love-of-obsidian/) was published as `#garden/cultivate` at first, then updated to `#garden/evergreen`
|
||||
* Some posts on IndieKit might be `#garden/evergreen` – foundational documentation
|
||||
* Explorations of **Digital Garden** metaphor are themselves thinking-in-public
|
||||
* IndieKit debugging posts are likely `#garden/question` – “Here’s what I’m stuck on”
|
||||
|
||||
* * *
|
||||
|
||||
## Connection to Other Concepts
|
||||
|
||||
### MYOG
|
||||
|
||||
Thinking in Public requires **infrastructure you control**. Can’t do this on Medium or Twitter (no garden stages, no update control). Need your own site. Yes, you could use elaborate tagging system on Mastodon like some do, but thats too confusing imho.
|
||||
|
||||
### Resonance-Driven Publishing
|
||||
|
||||
Thinking in Public **creates resonance**. Public thinking invites response. Response informs next iteration. Best thinking crystallizes into evergreen material. Loop.
|
||||
|
||||
### [For the Love of Obsidian and IndieWeb](https://blog.giersig.eu/articles/for-the-love-of-obsidian/)
|
||||
|
||||
The plugin removes friction that would prevent thinking-in-public. If publishing took 10 steps, you’d only publish “finished” work. Frictionless → more plants, more gardens, more evergreens over time.
|
||||
|
||||
* * *
|
||||
|
||||
## Open Questions
|
||||
|
||||
* How does the garden metaphor scale? (100 posts? 1000?)
|
||||
* Should there be **automatic archiving** (old plants → delete or revitalize)?
|
||||
* Can readers filter by garden stage in RSS?
|
||||
* Does thinking-in-public work for **all topics**? (Personal, technical, political?)
|
||||
* How do you handle **“I was wrong” posts**? Demote evergreen?
|
||||
* What’s the incentive structure for **keeping old plants alive**?
|
||||
* **NEW**: How do you celebrate promotion to evergreen? Special notification?
|
||||
* **NEW**: Should evergreen posts have a section that shows the journey (plant → cultivate → evergreen)? Would it be a “related” section?
|
||||
|
||||
* * *
|
||||
|
||||
## Status
|
||||
|
||||
**#garden/cultivate** – Actively exploring the evergreen concept. The stage ladder is becoming clearer through practice.
|
||||
|
||||
* * *
|
||||
|
||||
## Next Steps
|
||||
|
||||
* [x] Implement garden stage filtering in 11ty templates ✅ 2026-03-15
|
||||
* [x] Add evergreen filtering and discovery ✅ 2026-03-15
|
||||
* [ ] Add garden view to RSS feed (with stage indicators)
|
||||
* [ ] Document which posts are actively cultivated vs. dormant vs. evergreen
|
||||
* [ ] Public “Thinking in Progress” dashboard (with evergreen section)
|
||||
* [ ] Consider “promotion ceremony” for posts moving to evergreen
|
||||
* [ ] Revisit: Does the plant/cultivate/question/repot/revitalize/evergreen vocabulary fit?
|
||||
## Core Concept
|
||||
|
||||
**Thinking in Public** is the practice of making your thinking process – not just finished conclusions – visible. It means:
|
||||
|
||||
* Publish **seedling ideas**, not just polished essays
|
||||
* Show **uncertainty** and **open questions** explicitly
|
||||
* Make **iterations visible** (Garden Stages)
|
||||
* Allow **reader feedback** on incomplete thoughts
|
||||
* Treat your blog as an **extended mind**, not a portfolio
|
||||
|
||||
The opposite: perfectionism-driven publishing. “I only publish when it’s finished.” This is **risk-averse** and **isolating**.
|
||||
|
||||
* * *
|
||||
|
||||
## Why It Matters
|
||||
|
||||
### 1. Authenticity
|
||||
|
||||
Finished thoughts are often polished, sales-like, optimized. Unfinished thoughts are **real thoughts** – with questions, doubts, contradictions.
|
||||
|
||||
Readers can distinguish: “Okay, this is a well-considered opinion” vs. “This is an experiment, take a look.”
|
||||
|
||||
### 2. Faster Iteration Loop
|
||||
|
||||
If you have to wait until “finished”, the feedback latency is weeks or months. If you publish-while-thinking:
|
||||
|
||||
```
|
||||
Day 1: Publish #garden/plant (seedling)
|
||||
Day 3: Reader comment → new perspective
|
||||
Day 5: Update to #garden/cultivate
|
||||
Day 10: Publish #garden/revitalize (new insights)
|
||||
Day 30: Promote to #garden/evergreen (stable, reference-worthy)
|
||||
```
|
||||
|
||||
This is **resonance-driven**, not archive-driven.
|
||||
|
||||
### 3. Lower Barrier to Writing
|
||||
|
||||
> “A seedling thought shared is always better than a perfect thought kept private.”
|
||||
|
||||
Every additional requirement (“It must be finished”) is a **reason not to publish**. Thinking in Public removes this barrier.
|
||||
|
||||
### 4. Building in Public
|
||||
|
||||
Not just ideas, but **processes**: How I built the plugin, what problems I solved, which are still open.
|
||||
|
||||
Readers don’t just see “the result”, but also “how people actually develop.”
|
||||
|
||||
* * *
|
||||
|
||||
## The Garden Metaphor
|
||||
|
||||
Implemented with [Digital Garden](https://maggieappleton.com/garden-history) stages:
|
||||
|
||||
```
|
||||
🌱 #garden/plant → Brand new thought, just emerged
|
||||
🌿 #garden/cultivate → Active thinking, developing
|
||||
❓ #garden/question → Unresolved, asking for input
|
||||
⚙️ #garden/repot → Restructuring, reframing
|
||||
🔄 #garden/revitalize → Old idea, new life
|
||||
🌲 #garden/evergreen → Mature, stable, foundational (reference material)
|
||||
```
|
||||
|
||||
This makes **development stage visible** without saying “this is bad” or “this is good”.
|
||||
|
||||
An old idea can become relevant again. A seedling can lie dormant for years. A cultivated thought can mature into **evergreen reference material**. That’s **okay and transparent**.
|
||||
|
||||
* * *
|
||||
|
||||
## Understanding the Stages
|
||||
|
||||
### 🌱 Plant
|
||||
|
||||
A brand new thought, barely formed. Hypothesis-stage. “I’m wondering about…”
|
||||
|
||||
**Characteristics**:
|
||||
|
||||
* Low barrier to publish
|
||||
* Likely to change significantly
|
||||
* Invites early feedback and discussion
|
||||
* Short half-life
|
||||
|
||||
### 🌿 Cultivate
|
||||
|
||||
Active development. You’re thinking through it, refining, testing against reality.
|
||||
|
||||
**Characteristics**:
|
||||
|
||||
* Regular updates
|
||||
* Growing clarity but still evolving
|
||||
* Reader input shapes direction
|
||||
* “Works in progress” feeling
|
||||
|
||||
### ❓ Question
|
||||
|
||||
Deliberately unresolved. You’re asking for help, missing pieces, or exploring contradictions.
|
||||
|
||||
**Characteristics**:
|
||||
|
||||
* Explicitly unfinished
|
||||
* Invites expertise
|
||||
* May stay this way indefinitely (that’s okay)
|
||||
* High reader engagement potential
|
||||
|
||||
### ⚙️ Repot
|
||||
|
||||
Restructuring. The idea was good but needs new framing, different context, or fundamental reorganization.
|
||||
|
||||
**Characteristics**:
|
||||
|
||||
* Shows evolution of thinking
|
||||
* Breaks old patterns
|
||||
* Vulnerable moment (might fail)
|
||||
* Growth through friction
|
||||
|
||||
### 🔄 Revitalize
|
||||
|
||||
Returning to an old idea with fresh perspective. New relevance, new connections, new maturity.
|
||||
|
||||
**Characteristics**:
|
||||
|
||||
* Acknowledges time passing
|
||||
* Shows how thinking evolved
|
||||
* Often triggered by external event
|
||||
* Second (or third) life for an idea
|
||||
|
||||
### 🌲 Evergreen
|
||||
|
||||
Mature, stable, foundational. Reference material. This thought has been tested, refined, and stands on its own merit.
|
||||
|
||||
**Characteristics**:
|
||||
|
||||
* Unlikely to change fundamentally
|
||||
* Serves as reference/foundation for other ideas
|
||||
* High evergreen value (useful months or years later)
|
||||
* Can still be updated, but updates are minor refinements
|
||||
* Often becomes a “hub” for related posts
|
||||
* Attracts consistent traffic and citations
|
||||
|
||||
**When to promote to Evergreen**:
|
||||
|
||||
* Thought has been through plant → cultivate → revitalize cycle
|
||||
* Stability: hasn’t needed major updates in 3+ months
|
||||
* Utility: others reference it, it appears in multiple contexts
|
||||
* Maturity: feels foundational, not provisional
|
||||
* Clarity: explanations are clear enough for newcomers
|
||||
|
||||
* * *
|
||||
|
||||
## How It Changes Reader Relationship
|
||||
|
||||
**Traditional Blog**: “Author publishes finished thought. Reader reads. Maybe comments. Static.”
|
||||
|
||||
**Thinking in Public**: “Author works in public. Reader watches process. Reader contributes. Post evolves. Reader sees their input mattered. Some thoughts become trusted reference material.”
|
||||
|
||||
This isn’t just technically different. It’s **culturally** different:
|
||||
|
||||
* Less “author as authority”
|
||||
* More “author + reader as collaborative thinking”
|
||||
* Posts are **conversations**, not broadcasts
|
||||
* Some conversations crystallize into **reference material**
|
||||
|
||||
* * *
|
||||
|
||||
## Practical Mechanics
|
||||
|
||||
### In Obsidian + obsidian-micropub
|
||||
|
||||
```yaml
|
||||
---
|
||||
title: Some Half-Formed Idea
|
||||
tag: garden/cultivate
|
||||
excerpt: "I'm exploring..."
|
||||
---
|
||||
|
||||
## Initial Thoughts
|
||||
[...]
|
||||
|
||||
## Questions
|
||||
- What about X?
|
||||
- Does this connect to Y?
|
||||
- Still unclear: Z
|
||||
```
|
||||
|
||||
**Publish** → Blog shows with 🌱 badge. RSS reader sees `garden-stage: plant`.
|
||||
|
||||
Later:
|
||||
|
||||
```yaml
|
||||
tag: garden/cultivate
|
||||
```
|
||||
|
||||
**Update** → Post evolves. History visible.
|
||||
|
||||
Eventually:
|
||||
|
||||
```yaml
|
||||
tag: garden/evergreen
|
||||
excerpt: "A foundational exploration of..."
|
||||
```
|
||||
|
||||
**Promotion** → Visual indicator changes, post moves to reference section.
|
||||
|
||||
### In the Blog Template
|
||||
|
||||
* Post shows **clear stage indicator**
|
||||
* Maybe: “Last updated X days ago”
|
||||
* Maybe: “Open questions” section highlighted
|
||||
* Evergreen posts: Prominent placement, “Related posts” section
|
||||
* Maybe: Toggle to show **edit history**
|
||||
* Maybe: “Promoted to evergreen on [date]”
|
||||
|
||||
### Filtering & Discovery
|
||||
|
||||
Readers might want:
|
||||
|
||||
```
|
||||
/blog/all → All stages mixed
|
||||
/blog/seeds → Only plants (emerging ideas)
|
||||
/blog/cultivating → Active thinking
|
||||
/blog/evergreen → Reference material only
|
||||
/blog/timeless → Evergreen + question posts (always relevant)
|
||||
```
|
||||
|
||||
* * *
|
||||
|
||||
## Tensions & Trade-offs
|
||||
|
||||
### “Won’t this make me look less authoritative?”
|
||||
|
||||
**Short answer: No.** The opposite:
|
||||
|
||||
* Transparency builds trust
|
||||
* Showing uncertainty is **more credible** than false certainty
|
||||
* Readers respect “I’m thinking through this” more than “Here’s the truth”
|
||||
* Having **evergreen material** shows maturity and reliability
|
||||
|
||||
**Long answer**: Authority doesn’t come from “I never change my mind”. It comes from “I think carefully and adjust when I learn something. And some of my thinking stands the test of time.”
|
||||
|
||||
### “What if someone quotes my half-formed idea out of context?”
|
||||
|
||||
**Risk**: Yes. **Mitigation**:
|
||||
|
||||
* Clear garden stage badges
|
||||
* License/note: “This is work-in-progress thinking”
|
||||
* If it matters, you update the post and readers see the change
|
||||
* **Evergreen posts have explicit “stable” indicator** – these are safe to quote
|
||||
|
||||
**Real mitigation**: The garden stage IS the context.
|
||||
|
||||
### “Doesn’t this create noise?”
|
||||
|
||||
Fair question. If you publish **everything**, yes.
|
||||
|
||||
But you filter by stage. A reader interested in “reference material” sees only evergreens. A reader interested in “emerging ideas” sees only plants.
|
||||
|
||||
**It’s signal, not noise – because it’s labeled.**
|
||||
|
||||
### “When should I promote to evergreen?”
|
||||
|
||||
Don’t rush. A thought becomes evergreen through:
|
||||
|
||||
* **Time passing** (stability test)
|
||||
* **Repeated usefulness** (does it serve you and others?)
|
||||
* **Standing up to challenge** (did criticism refine it or break it?)
|
||||
* **Foundational role** (does it anchor other ideas?)
|
||||
|
||||
Some thoughts never become evergreen. That’s okay. Not all thinking needs to be permanent.
|
||||
|
||||
* * *
|
||||
|
||||
## Historical Context
|
||||
|
||||
* **My Blog** (2000s): “Publish when finished”
|
||||
* **Twitter** (2010s): “Publish everything instantly”
|
||||
* **Thinking in Public** (2020s): “Publish with context about development stage”
|
||||
* **Thinking in Public + Evergreen** (2025+): “…and let the best thinking crystallize”
|
||||
|
||||
It’s a **synthesis**:
|
||||
|
||||
* Blogger rigor (think before publish)
|
||||
* Twitter immediacy (don’t wait for perfect)
|
||||
* Garden transparency (show the state)
|
||||
* **Librarian wisdom** (some things deserve to last)
|
||||
|
||||
* * *
|
||||
|
||||
## Examples in the Wild
|
||||
|
||||
* [For the Love of Obsidian and IndieWeb](https://blog.giersig.eu/articles/for-the-love-of-obsidian/) was published as `#garden/cultivate` at first, then updated to `#garden/evergreen`
|
||||
* Some posts on IndieKit might be `#garden/evergreen` – foundational documentation
|
||||
* Explorations of **Digital Garden** metaphor are themselves thinking-in-public
|
||||
* IndieKit debugging posts are likely `#garden/question` – “Here’s what I’m stuck on”
|
||||
|
||||
* * *
|
||||
|
||||
## Connection to Other Concepts
|
||||
|
||||
### MYOG
|
||||
|
||||
Thinking in Public requires **infrastructure you control**. Can’t do this on Medium or Twitter (no garden stages, no update control). Need your own site. Yes, you could use elaborate tagging system on Mastodon like some do, but thats too confusing imho.
|
||||
|
||||
### Resonance-Driven Publishing
|
||||
|
||||
Thinking in Public **creates resonance**. Public thinking invites response. Response informs next iteration. Best thinking crystallizes into evergreen material. Loop.
|
||||
|
||||
### [For the Love of Obsidian and IndieWeb](https://blog.giersig.eu/articles/for-the-love-of-obsidian/)
|
||||
|
||||
The plugin removes friction that would prevent thinking-in-public. If publishing took 10 steps, you’d only publish “finished” work. Frictionless → more plants, more gardens, more evergreens over time.
|
||||
|
||||
* * *
|
||||
|
||||
## Open Questions
|
||||
|
||||
* How does the garden metaphor scale? (100 posts? 1000?)
|
||||
* Should there be **automatic archiving** (old plants → delete or revitalize)?
|
||||
* Can readers filter by garden stage in RSS?
|
||||
* Does thinking-in-public work for **all topics**? (Personal, technical, political?)
|
||||
* How do you handle **“I was wrong” posts**? Demote evergreen?
|
||||
* What’s the incentive structure for **keeping old plants alive**?
|
||||
* **NEW**: How do you celebrate promotion to evergreen? Special notification?
|
||||
* **NEW**: Should evergreen posts have a section that shows the journey (plant → cultivate → evergreen)? Would it be a “related” section?
|
||||
|
||||
* * *
|
||||
|
||||
## Status
|
||||
|
||||
**#garden/cultivate** – Actively exploring the evergreen concept. The stage ladder is becoming clearer through practice.
|
||||
|
||||
* * *
|
||||
|
||||
## Next Steps
|
||||
|
||||
* [x] Implement garden stage filtering in 11ty templates ✅ 2026-03-15
|
||||
* [x] Add evergreen filtering and discovery ✅ 2026-03-15
|
||||
* [ ] Add garden view to RSS feed (with stage indicators)
|
||||
* [ ] Document which posts are actively cultivated vs. dormant vs. evergreen
|
||||
* [ ] Public “Thinking in Progress” dashboard (with evergreen section)
|
||||
* [ ] Consider “promotion ceremony” for posts moving to evergreen
|
||||
* [ ] Revisit: Does the plant/cultivate/question/repot/revitalize/evergreen vocabulary fit?
|
||||
* [ ] Track post lifecycle: when was it planted? When promoted to evergreen?
|
||||
|
||||
@@ -0,0 +1,10 @@
|
||||
---
|
||||
date: 2026-03-22T11:56:05.558Z
|
||||
likeOf: https://mastodon.social/@donnerbella/116268395139377355
|
||||
aiTextLevel: "0"
|
||||
syndication:
|
||||
- https://blog.giersig.eu/likes/d919b/
|
||||
updated: 2026-03-22T11:57:20.871Z
|
||||
mpUrl: https://blog.giersig.eu/likes/d919b/
|
||||
permalink: /likes/d919b/
|
||||
---
|
||||
@@ -0,0 +1,22 @@
|
||||
---
|
||||
date: 2026-03-22T13:40:15.777Z
|
||||
title: Diary Of A CEO Is Making You Less Successful - Barry's Economics - Barry's Economics
|
||||
likeOf: https://www.youtube.com/watch?v=CbDQs_TcyN4
|
||||
visibility: public
|
||||
youtubeVideoId: CbDQs_TcyN4
|
||||
youtubeChannel: Barry's Economics
|
||||
youtubeThumbnail: https://i.ytimg.com/vi/CbDQs_TcyN4/mqdefault.jpg
|
||||
category:
|
||||
- on/sociology
|
||||
- on/economy
|
||||
- on/propaganda
|
||||
aiTextLevel: "0"
|
||||
updated: 2026-03-22T13:43:14.500Z
|
||||
syndication:
|
||||
- https://bsky.app/profile/did:plc:g4utqyolpyb5zpwwodmm3hht/post/3mhnogsn2ms2o
|
||||
- https://blog.giersig.eu/likes/yt-like-cbdqs-tcyn4/
|
||||
mpUrl: https://blog.giersig.eu/likes/yt-like-cbdqs-tcyn4/
|
||||
permalink: /likes/yt-like-cbdqs-tcyn4/
|
||||
---
|
||||
|
||||
> The system is broken, but we are sold the story that we are broken
|
||||
@@ -0,0 +1,33 @@
|
||||
---
|
||||
date: 2026-03-22T08:18:36.735Z
|
||||
title: "A Web Revival: the Internet didn't die, you're just not on it - onionboots"
|
||||
likeOf: https://www.youtube.com/watch?v=tkUgOT22F5s
|
||||
visibility: public
|
||||
youtubeVideoId: tkUgOT22F5s
|
||||
youtubeChannel: onionboots
|
||||
youtubeThumbnail: https://i.ytimg.com/vi/tkUgOT22F5s/mqdefault.jpg
|
||||
category: smallweb
|
||||
aiTextLevel: "0"
|
||||
updated: 2026-03-22T08:29:19.404Z
|
||||
webmentionResults:
|
||||
sent: 1
|
||||
failed: 0
|
||||
skipped: 0
|
||||
details:
|
||||
sent:
|
||||
- target: https://brennan.day/trust-and-faith-in-our-web/
|
||||
endpoint: https://webmention.io/brennan.day/webmention
|
||||
type: webmention
|
||||
status: 201
|
||||
failed: []
|
||||
skipped: []
|
||||
timestamp: 2026-03-22T08:28:32.764Z
|
||||
webmentionSent: true
|
||||
syndication:
|
||||
- https://bsky.app/profile/did:plc:g4utqyolpyb5zpwwodmm3hht/post/3mhn4vi77en2y
|
||||
- https://blog.giersig.eu/likes/yt-like-tkugot22f5s/
|
||||
mpUrl: https://blog.giersig.eu/likes/yt-like-tkugot22f5s/
|
||||
permalink: /likes/yt-like-tkugot22f5s/
|
||||
---
|
||||
|
||||
A bit late to the game, but thanks to [brennan.day](https://brennan.day/trust-and-faith-in-our-web/) this nice piece resurfaced and I wanted to share it with you: **A Web Revival: the Internet didn't die, you're just not on it - onionboots**
|
||||
@@ -3,7 +3,7 @@ date: 2026-03-08T06:15:00.000Z
|
||||
title: about
|
||||
summary: About me page
|
||||
category: slashpage/about
|
||||
updated: 2026-03-21T19:32:58.123Z
|
||||
updated: 2026-03-22T09:13:31.401Z
|
||||
webmentionResults:
|
||||
sent: 1
|
||||
failed: 0
|
||||
@@ -56,7 +56,7 @@ mpUrl: https://blog.giersig.eu/about/
|
||||
permalink: /about/
|
||||
---
|
||||
|
||||
My path has been anything but straight. I started out as a Unix administrator, spent some time DJing minimal techno, studied Sociology in Constance, and somehow ended up managing a mountaineering gear shop. For nearly a decade I ran a communication agency - writing, editing, advising clients across industries. Then came years as a social worker, helping young people and refugees find their footing in Germany. These days I work in public relations for a district office, with a focus on social issues.
|
||||
My path (see [my CV](https://blog.giersig.eu/cv/)) has been anything but straight. I started out as a Unix administrator, spent some time DJing minimal techno, studied Sociology in Constance, and somehow ended up managing a mountaineering gear shop. For nearly a decade I ran a communication agency - writing, editing, advising clients across industries, implementing digital tools to facilitate strategies. Then came years as a social worker, helping young people and refugees find their footing in Germany. These days I work in public relations for a district office, with a focus on social issues.
|
||||
|
||||
I tell you all this not to impress, but because the zigzag matters. It shaped how I pay attention.
|
||||
|
||||
|
||||
@@ -3,7 +3,7 @@ date: 2026-03-08T01:32:42.024Z
|
||||
title: now
|
||||
summary: a page that tells you what I'm focused on at this point in my life
|
||||
category: slashpage/now
|
||||
updated: 2026-03-19T19:02:01.726Z
|
||||
updated: 2026-03-22T14:20:50.384Z
|
||||
webmentionResults:
|
||||
sent: 0
|
||||
failed: 0
|
||||
@@ -18,6 +18,8 @@ webmentionResults:
|
||||
reason: No webmention endpoint found
|
||||
timestamp: 2026-03-09T19:23:19.612Z
|
||||
webmentionSent: true
|
||||
aiTextLevel: "0"
|
||||
aiCodeLevel: "0"
|
||||
mpUrl: https://blog.giersig.eu/now/
|
||||
permalink: /now/
|
||||
---
|
||||
@@ -32,7 +34,7 @@ This page is a [now page](https://nownownow.com/about), you should consider addi
|
||||
- Integrating [Obsidian, Digital Garden](https://blog.giersig.eu/articles/thinking-in-public/) and IndieWeb
|
||||
- exploring the Indieweb
|
||||
- Ghost blogging
|
||||
- upgrading skills from FreeBSD 3 to FreeBSD 15
|
||||
- upgrading skills from [FreeBSD](https://www.freebsd.org) 3 to FreeBSD 15
|
||||
|
||||
... and I like ice in the sunhine!
|
||||
|
||||
|
||||
@@ -0,0 +1,23 @@
|
||||
---
|
||||
date: 2026-03-22T10:25:28.096Z
|
||||
inReplyTo: https://rmendes.net/replies/2026/03/22/can-llm-be-inclusive/
|
||||
category: dev
|
||||
aiTextLevel: "0"
|
||||
webmentionResults:
|
||||
sent: 0
|
||||
failed: 0
|
||||
skipped: 0
|
||||
details:
|
||||
sent: []
|
||||
failed: []
|
||||
skipped: []
|
||||
timestamp: 2026-03-22T10:26:10.106Z
|
||||
webmentionSent: true
|
||||
syndication:
|
||||
- https://blog.giersig.eu/replies/ca3d8/
|
||||
updated: 2026-03-22T10:26:57.554Z
|
||||
mpUrl: https://blog.giersig.eu/replies/ca3d8/
|
||||
permalink: /replies/ca3d8/
|
||||
---
|
||||
|
||||
empowering! Thank you for this perspective. I can't stand elitism. Let the people decide what they want.
|
||||
@@ -0,0 +1,30 @@
|
||||
---
|
||||
date: 2026-03-22T07:45:25.492Z
|
||||
repostOf: https://www.faz.net/aktuell/politik/inland/manfred-weber-und-die-afd-berlin-sollte-von-ihm-lernen-200653662.html
|
||||
category: on/politics/fascism
|
||||
aiTextLevel: "0"
|
||||
syndication:
|
||||
- https://bsky.app/profile/did:plc:g4utqyolpyb5zpwwodmm3hht/post/3mhn2jdwaez2y
|
||||
- https://blog.giersig.eu/reposts/25df5/
|
||||
updated: 2026-03-22T07:50:39.149Z
|
||||
webmentionResults:
|
||||
sent: 0
|
||||
failed: 0
|
||||
skipped: 1
|
||||
details:
|
||||
sent: []
|
||||
failed: []
|
||||
skipped:
|
||||
- target: https://open.ifz-muenchen.de/server/api/core/bitstreams/6b9eff90-d467-4fda-86ac-752746ab718d/content
|
||||
reason: No webmention endpoint found
|
||||
timestamp: 2026-03-22T07:48:28.443Z
|
||||
webmentionSent: true
|
||||
mpUrl: https://blog.giersig.eu/reposts/25df5/
|
||||
permalink: /reposts/25df5/
|
||||
---
|
||||
|
||||
Der Opfermythos ist integraler Bestandteil des faschistischen Denkens, zahlt er doch direkt auf den [palingenetischen Ultranationalismus](https://open.ifz-muenchen.de/server/api/core/bitstreams/6b9eff90-d467-4fda-86ac-752746ab718d/content) ein. Wenn man nicht Opfer wäre, müsste man sich sein "Heldentum" auch nicht zuück erkämpfen. Da es tatsächlich ja eher schwierig ist, sich selbst, im reichsten Viertel der Welt, glaubhaft als Opfer zu sehen, werden krude ideologische Hilfskonstrukte zur Selbstveropferung genutzt.
|
||||
|
||||
> Es ist doch eine ziemlich künstliche Trennung, die da aufrechterhalten wird: gemeinsame Abstimmung ja – aber nur wenn sich die Beteiligten zuvor nicht berühren?
|
||||
|
||||
**Künstliche Trennung** - ist wahrscheinlich ehrlicher als vom Autor gewollt. Die Konservativen und die Rechten unterscheidet eben wirklich nur eine "künstliche Trennung"
|
||||
@@ -0,0 +1,14 @@
|
||||
---
|
||||
date: 2026-03-22T11:37:51.919Z
|
||||
repostOf: https://cartoons.guido-kuehn.de/die-mittaeterin/
|
||||
category: on/politics/fascism
|
||||
aiTextLevel: "0"
|
||||
syndication:
|
||||
- https://bsky.app/profile/did:plc:g4utqyolpyb5zpwwodmm3hht/post/3mhnhj25o6b2o
|
||||
- https://blog.giersig.eu/reposts/baf6d/
|
||||
updated: 2026-03-22T11:39:13.610Z
|
||||
mpUrl: https://blog.giersig.eu/reposts/baf6d/
|
||||
permalink: /reposts/baf6d/
|
||||
---
|
||||
|
||||
Capitalism is a death cult.
|
||||
Reference in New Issue
Block a user