Spam isn't the only challenge of going self-hosted and it's cool to tie into an existing ecosystem for identity. Also it's pretty neat that people can engage outside of your website while you still get to pick what gets surfaced on your own website.
I have a static site. Self hosted would mean I’d need a database and I think right now I want to keep the static generation. Happy to try self hosted in future and write my own solution but right now I got plenty of side projects
Most Mastodon instances already have moderation. Can that be leveraged? Or does it tend to be too permissive?
If I only show comments from a well-moderated Mastodon instance that my main account is on, plus any instances that it federates with, does that not solve the problem?
Bluesky allows thread owners to hide posts from the thread.
Presumably the blog interface itself can choose to simply not surface hidden replies at all; if you view the thread via a different client (eg the Bluesky app) you would have the option of seeing the hidden posts.
And of course if you view the thread through your own Bluesky interface your personal blocklists and moderation would apply to the thread.
I'm not sure if this implements it, but Bluesky has an API to hide replies (called thread gating). It's a separate API call though, so you don't get it automatically when loading a thread via the API.
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.
