About this newsletter
(Notes: This is version 2 of this post; more details and version control in the footer.)
As I write this I'm preparing to fly to Vancouver for AtmosphereConf 2026. It just doesn't seem right that I run a workshop at the atproto.science event, whilst only publishing longform content using sites (my experimental wiki, my hub, Medium, LinkedIn, Mailchimp) which are not on the Atmosphere, particularly as I played a reasonable role in putting the entire ATProtocol Science agenda on leaflet.
Of course, if I was a developer that would not be the case, because solutions exist:
- while my experimental wiki is published from my Obsidian vault using Massive Wiki, I know of at least three solutions to publishing my markdown content using the standard.site lexicon. I just need a developer;
- and I own myhub.ai... but again I need budget to pay my developer to upgrade it, which may require some lexicon innovation.
I'd also be very happy to stop using Medium, LinkedIn or Mailchimp, but the fact remains that the vast majority of my audience currently receive my content via those platforms. At least I don't use Substack.
So I'm tweaking my online architecture just a little:
- Thinking in Obsidian, as before, and publishing to my experimental wiki. This will host the canonical version (often versioned), and will hopefully one day be published directly onto the Atmosphere via standard.site
- As it is not currently, I'll repost it to my leaflet, which is where people will be able to interact with it. I'll curate this version on my hub
- I'll also repost the content to the other platforms, pointing to the leaflet version and asking followers & subscribers to get a DID to use it to subscribe and discuss. If and when I start seeing Leaflet subscribers, I'll start transitioning those followers and subscribers to leaflet, using the same techniques I originally developed for migrating away from X.
So if you'd like to accelerate that transition, please subscribe and share!
Revision Notes
This is one of this wiki's pages managed with the permanent versions pattern described in Two wiki authors and a blogger walk into a bar…
- changes in this version: (2026-02-22)
- developed and described online architecture, having created my leaflet newsletter in the meantime
- version control