The Bluesky ecosystem is so cool. I read this approach presented here some times ago. The only thing that could be problematic: you need to make a posting on Bluesky for all your Web pages to use the commenting system. And a webcomponent for this would be nice
You can only hide them. Bluesky also can’t block users, only hide them from your timelines (if you’re using an app that respects that). It’s quite limited compared to Mastodon in that regard.
It’s odd to eliminate using GitHub issues as comments because the user would need a GitHub account then decide on bluesky. Bluesky would also require users to have a Bluesky account? How many readers already have a GitHub account vs already have a Bluesky account?
I mean it’s fine, use whatever your comfortable with and Bluesky is the next frontier for development ideas.
Id love a term for this sort of thing. It's like tech hijacking or something. Google sheets as a backend, github discussions for a comment system, etc.
Interesting article! I always enjoy reading how people build and maintain their independent personal websites. This post starts with the "Comment System Problem" and mentions four possible solutions, but I think there's a fifth that has worked well for me.
After spending too much time fiddling with third-party comment systems, I ended up building my own [1]. It's pretty barebones, just does what I need, and nothing more.
Each comment is written to a text file for manual review, so I don't have to worry about spam, cross-site scripting, or irrelevant comments. I usually check them on weekends and add them to my blog.
Comments are stored as plain HTML files, and my static site generator [2] builds the site along with the comment pages [3]. So in a way, it's also a static comment pages generator.
This setup doesn't meet the five attributes (no infra, rich content, real identity, etc.) in the second section of the article, so it wouldn't suit the author's needs, but it has worked quite well for me. I've been using it for at least four years (perhaps much longer, since my old PHP website did something similar), and I've been quite happy with it.
Bluesky is very useful to store information on users' existing accounts.
I'm currently building a review system for my open source Web map https://cartes.app, based on Bluesky. Not trivial though, you have to create a lexicon and maintain a DB based on the Bluesky stream.
This is interesting to me for the reason of having a way to interact with social media that isn't loading a social media feed. It would be great to put this on my blog and then have people able to comment on it, and basically the only way I interact with Blue Sky or any social media feed is through this kind of interface and through creating content.
Over the years I've found that any interaction with social media that involves me loading the feed inevitably ends up with me doomscrolling or spending way too much time scrolling stuff that doesn't add anything to my life. This could be a way to avoid that cycle, finally, but still interact with the wider social media world a little bit.
38 comments
[ 252 ms ] story [ 2410 ms ] threadI mean it’s fine, use whatever your comfortable with and Bluesky is the next frontier for development ideas.
So personally I'd be wary of adopting it. I think it's likely the API gets locked down and the comments break in a couple of years.
If BlueSky banned you tomorrow what is the plan? If BlueSky went bankrupt tomorrow?
I figure there are other AT compliant products that you can switch to but a lot of data would go missing?
I only see 2 posts on the entire blog, both from 2025 (and one is this post).
https://cassidyjames.com/blog/fediverse-blog-comments-mastod...
After spending too much time fiddling with third-party comment systems, I ended up building my own [1]. It's pretty barebones, just does what I need, and nothing more.
Each comment is written to a text file for manual review, so I don't have to worry about spam, cross-site scripting, or irrelevant comments. I usually check them on weekends and add them to my blog.
Comments are stored as plain HTML files, and my static site generator [2] builds the site along with the comment pages [3]. So in a way, it's also a static comment pages generator.
This setup doesn't meet the five attributes (no infra, rich content, real identity, etc.) in the second section of the article, so it wouldn't suit the author's needs, but it has worked quite well for me. I've been using it for at least four years (perhaps much longer, since my old PHP website did something similar), and I've been quite happy with it.
[1] https://github.com/susam/susam.net/blob/main/form.lisp
[2] https://github.com/susam/susam.net/blob/main/site.lisp
[3] https://susam.net/comments/
I'm currently building a review system for my open source Web map https://cartes.app, based on Bluesky. Not trivial though, you have to create a lexicon and maintain a DB based on the Bluesky stream.
Bluesky _will_ enshittify sooner or later
Over the years I've found that any interaction with social media that involves me loading the feed inevitably ends up with me doomscrolling or spending way too much time scrolling stuff that doesn't add anything to my life. This could be a way to avoid that cycle, finally, but still interact with the wider social media world a little bit.