bradbarrish29 downloadsPublish notes to micro.blog using the Micropub API. Supports drafts, categories, image uploads, and editing existing posts.
Publish the active Obsidian note to Micro.blog with Micropub. The plugin supports published posts, Micro.blog drafts, image uploads, categories, Mastodon cross-posting when explicitly requested, and updating a previously published post.
Use a development vault, not your main vault.
Place this folder at .obsidian/plugins/microblog-publisher in that vault.
Install dependencies:
npm install
Start the development build:
npm run dev
In Obsidian, enable community plugins and turn on Micro.blog Publisher.
https://micro.blog/account/apps. The token is stored with Obsidian secret storage, not in the plugin settings JSON.https://micro.blog/micropub.https://micro.blog/micropub/media.mastodon: true in a note's frontmatter when you want that post cross-posted.By default, publishes send a blank mp-syndicate-to value so Micro.blog does not cross-post to every configured service. Cross-posting happens only when a note opts in with frontmatter and a matching syndication UID is configured.
---
title: Optional title
categories:
- notes
mastodon: true
---
After a successful publish, the plugin writes:
microblog_url: https://example.com/post-url
microblog_published: 2026-05-01T12:00:00.000Z
microblog_media:
image.png: https://micro.blog/photos/...
Use Update published post on micro.blog to update a note that already has microblog_url.
Run the production build before release:
npm run build
Run a release package build:
npm run package
The package script writes safe distributable files to dist/microblog-publisher/: main.js, manifest.json, and versions.json. Do not publish data.json, node_modules, or local .obsidian state.
README.md describes the plugin and how to use it.LICENSE is included.manifest.json has a unique id and semantic version.versions.json maps plugin versions to minimum Obsidian versions.main.js, manifest.json, and versions.json.