Bluesky

• Post to Bluesky via a Tab view or by highlighting text

Usage Guide

Initial Setup

• Open the Bluesky plugin in the Obsidian settings.
• Enter your Bluesky handle (e.g. evanharris.bsky.social).
• Enter a Bluesky App Password - Note: Please do not enter your Bluesky password here.
  • If you do not have an App Password, you can create one by going to the App Passwords page and creating a new App Password.

How to Post

A new megaphone icon will appear in the left sidebar after you install the plugin.

• To compose a post or a thread:
  • Click the megaphone icon to open a Bluesky tab.
  • Write your post or thread.
  • Click "Post" to post to Bluesky.
• If you prefer to use the command palette, you can run the Open Bluesky tab command.

Reply to a post

You can add your post (or a whole thread) as a reply that continues an existing Bluesky post.

• Open the Bluesky tab.
• Paste the post's URL (e.g. https://bsky.app/profile/handle/post/...) into the Reply to a Bluesky post field at the top.
• The plugin looks up the post and shows a preview so you can confirm the target.
• Write your post or thread and click "Post" — it will be attached as a reply.

Leave the field empty to post normally. Any public post can be replied to.

Network use & privacy

This plugin only contacts the network for the following, all initiated by you:

• Bluesky (bsky.social) - to authenticate with your App Password, to publish posts, threads, and uploaded images via the AT Protocol (@atproto/api), and to look up a post you choose to reply to. Your credentials are stored locally and sent only to Bluesky.
• Link preview generation - when your post includes a URL, the plugin fetches that URL (and its preview image) to build the embedded link card. This means it contacts whatever domain you linked to.

No telemetry or analytics are collected. The plugin makes no network requests unless you post or include a link.

Testing

npm run test:e2e

Runs provider-free UI smoke tests against a real, sandboxed Obsidian instance via wdio-obsidian-service — no Bluesky credentials, no network calls, no contact with your real vault. See test/README.md for details.

[!WARNING] When touching the test config, never point plugins: in wdio.conf.mts at the repo root ("."). wdio-obsidian-service copies data.json — which holds your real Bluesky app password — from the plugin directory into every test vault. Always go through the staged copy in test/plugin-dist/ (scripts/stage-plugin.mjs).

Say Hi

• Bluesky

Roadmap

• Media
• Embeds
• Posting threads from within a file
• Language specification

Attribution

This project builds upon the Bluesky AT Protocol, which is licensed under the MIT License.

The source code of this project includes parts of the Bluesky AT Protocol, following the MIT License requirements.