Adding Mastodon Comments to Your Blog
beej.us
beej.us
F-Droid apps don't have comments or ratings on the default F-Droid app. They're generally less necessary because the apps don't have ads or severe privacy concerns like the ones from Play Store do, but it's still nice to hear others' experiences and comments on them.
G-Droid introduced a commenting system by simply redirecting you to a mastodon URL when you clicked "Add a comment". That URL will by default add "@gdroid@mastodon.technology" and a hashtag based on the app package name to your post. For eg., for the Markor app, it would add
@gdroid@mastodon.technology #net_gsantner_markor #fdroid_app_comments
at the end of your comment post. The @username will notify a bot to pickup this comment, the hashtag will help it attribute it to the right app, and so your comment will get collected and displayed below the app listing in G-Droid.Sadly, G-Droid itself doesn't seem to be actively maintained anymore, the last update being a few years old, but it's a really cool example of what is possible when you have open, flexible systems that can be plugged in together in many ways to create the features you need.
I ended up doing something similar, but statically, and searching for discussions dynamically rather than using a single hardcoded thread. Essentially it's a script that searches for recent posts linking to my domain name on Reddit, HN, etc, and then updates a file with the URL of that post and some information about when it was made and how many posts there are. Then there's a Hugo template that converts the data in this file to HTML.
The script runs every few hours using free GitHub runner time, and if it makes a change, it commits it and creates a pull request with the contents so that I can review it. (I could automatically commit straight to the main branch but I like having the manual review just in case.)
I couldn't get it to work for Mastodon because there's not really a public search for Mastodon (for all sorts of reasons), although at some point I want to get it working for Bluesky. I did try hooking it up with Twitter for a while, but that required all sorts of API keys and things that I didn't want to deal with so I gave up. You also need API keys for Reddit, but that was easier to get hold of and manage.
I wrote a post about how I implemented it here: https://jonathan-frere.com/posts/adding-discussions/
I’m quite happy with the result. It’s simple, minimal, and fast. It does exactly what I need and no more.
Plus, everything is held for my review before being published, so I don’t have to worry about spam, cross-site scripting, or off-topic comments. It’s been a satisfying solution.
There's a rather long list of other solutions over at https://darekkay.com/blog/static-site-comments/
And there's https://github.com/carlitoplatanito/disgus for adding Nostr based comments to your static blog.
I should perhaps also add a little disclaimer/warning: When i had a closer look at cactus comments a while ago, it seemed to be broken / "assembly required" in various parts and blogs that use it.
What works best for me is to add a link to the fediverse, linkedin and sometimes HN threads of comments when I publish a post. It's also a very low tech solution :)
At the same time, I am an opportunist — sometimes it is Reddit, sometimes it is ix Xm, and sometimes it is here, the Hacker News. Different posts resonate with different audiences; and I don't want to link to a ghost town.
One issue is that there is no such thing as "the default platform for discussions"—no matter which one you choose, only a small fraction of readers will be interested in participating.
Isn't this what the various linkback mechanisms tried to solve? It seems like the ideal solution: let anyone comment wherever they want, from a tweet to their own follow-up blog post, and connect them all via automated notifications.
Anyone else weighed up the two approaches, I'm still on the fence tbh.
However since I'm not a very good frontend dev, posting to this is currently done through a CLI application without great UX. :D If you're interested, I would *love* to collaborate with someone on it.
PS. a running instance where I post now and then is https://marius.federated.id
It's pretty easy to do. I recommend it, if you already use Fedi for anything.
https://micro.blog has a good implementation of this for both the Fediverse and Bluesky. A random example of mine that has an array of 'em if you want an example: https://zacwe.st/2025/02/12/amazon-is-removing-the-ability.h...
Mastodon is great, but the "pick a server" step is a pretty hard filter for most users, who just want to sign up for something.
You'd also get to benefit automatically from Bluesky's blocking/moderation tools.
How is this relevant to making your own server?
> You can set up your own PDS, right now
Any existing alternative servers compatible with the main network?
If I would want comments on my blog I would try to integrate BlueSky and Mastodon comments.
https://blog.nawaz.org/posts/2025/Jan/adding-fediverse-comme...
https://andreasthinks.me/posts/quarto_comments/open-social.h...
If it were going to get any bigger, I'd want my own Mastodon server.
Edit: this is also why I made it an explicit user action to load the comments.
(but just having users click a button is likely to be more than enough)
I have tried to get my static site generator (Lektor) to work with Mastodon and generate my Mastodon posts as a blog. I haven't had success yet because Lektor is obsolete and kind of garbage, but Mastodon's API is great.
I really like this solution, though. Just write a blog post and link to it from Mastodon. That solves the problem of Mastodon's text limit and of small hosted instances needing to regularly delete content to stay under their account limit.
As a technical feat and expression of FOSS integration this is cool but I don't know about the utility of it since any actual human being reading these comments will already be reading them on Mastodon. It is definitely better than the cancer that is Disqus though.
Github is a proprietary service owned by Microsoft. Storing comments there is a less privacy friendly solution than this one.
I'll literally take ads and tracking over it.
To your point, though, I don't expect anyone without an account already to post, but my target audience largely already has such accounts.
This is a ridiculous expectation. Virtually nobody uses Mastodon, especially since BlueSky now is the open platform of choice.
But even without this, Twitter-like websites for me and a lot of other people have absolutely no usecase, despite being in the audience who could read your blog. Expecting all your visitors to have an account in nonsensical.
But maybe for your blog, you could use the same basic technique and do BlueSky comments instead.
You may want to look around you...
This is massively down from 2 years ago where it was 1.7M: https://www.reddit.com/r/Mastodon/comments/10bimq2/comment/j...
You may want to look around you...
You can run your own server, on your own hardware, make your own account, own every step of the stack, and can comment on there.
It's not just 3rd-party login, it's YOUR-party login.
You still have to make an account on a totally unrelated website. It's the shittiest experience one can think of.
But your excuse is "Hey actually you can also setup the whole application yourself before making the account to post a blog comment on an unrelated website, so that's actually super awesome!".
Absolutely ridiculous, and if any company you didn't like were to do something similar you would screech.
Even back before 2010, almost all blogging platforms had an option that would let the owner require log in to comment.
And it was fairly common, because of spam.