Skip to content

feat: add Bluesky comments component#2286

Open
eamag wants to merge 2 commits intojackyzha0:v4from
eamag:v4
Open

feat: add Bluesky comments component#2286
eamag wants to merge 2 commits intojackyzha0:v4from
eamag:v4

Conversation

@eamag
Copy link
Copy Markdown

@eamag eamag commented Jan 25, 2026

Inspired by https://micahcantor.com/blog/bluesky-comment-section.html I wanted to try to add bsky comments to quartz.
Written with some help from AI (gemini in antigravity) because I'm not an expert in this area, happy to fix things!

This is how it looks like:
image
for a (randomly selected) bsky post https://bsky.app/profile/isakole.bsky.social/post/3md6xtso6yc2s

@eamag eamag marked this pull request as draft January 25, 2026 16:17
@github-actions
Copy link
Copy Markdown

github-actions bot commented Jan 25, 2026

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name Status Preview Last Commit
quartz ✅ Ready (View Log) Visit Preview 93f6bc2

],
```

### Bluesky
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

stepping back, i think it would be cool to have this automatically posted on bsky (via ATProtocol) per publishing notes. i.e for each of the note that we want to send to bsky, all users need to do is:

---
bsky: true
---

Then we can handle publishing and commenting automatically during build time. This is a bit more complicated that what you have here, but I think this implementation works as well, as first step

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I will do a full review afterwards, maybe sometime tonight. thank you for the transparency and work!

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

automatically posted on bsky (via ATProtocol) per publishing notes

I thought about it, but decided that managing login/passwords is too much for the first iteration

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do they happen to have an oauth workflow?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

They do, they also have App passwords which may be more relevant. I would rather do it in a separate PR though, it sounds a bit tricky to figure out when to post and how to prevent double posting (considering we're building it locally and in some ci/cd pipelines)

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I Thinks using standard site lexicon would be the best instead of bluesky feed posts that have a limit of 300 charachters ! see https://standard.site/
But yeah the atproto integration would be soo good! Definitly take a look at the https://standard.site/ wich is already used by leaflet, pckt, offprint blogging platforms.
Your notes will then be visible on each platform supporting standard.site !

@eamag eamag marked this pull request as ready for review January 30, 2026 16:15
@eamag eamag requested a review from aarnphm February 12, 2026 12:58
@eamag
Copy link
Copy Markdown
Author

eamag commented Feb 12, 2026

@jackyzha0 @saberzero1 any thoughts on this?

@saberzero1
Copy link
Copy Markdown
Collaborator

@jackyzha0 @saberzero1 any thoughts on this?

Turn it into a plugin once V5 is released.

@saberzero1 saberzero1 added the plugins Possible plugins ideas label Feb 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

plugins Possible plugins ideas

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants