As another option Remark42
this post was submitted on 24 Mar 2024
129 points (99.2% liked)
Selfhosted
39253 readers
189 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 1 year ago
MODERATORS
You might like Commento which is FOSS. You can self-host it (or fire it onto a free or low cost cloud host), and fun. It's more like a Lemmy/reddit format (comment up/down votes can be enabled) than masto but maybe you'll enjoy it.
Users can comment anonymously or you can enable basic verification steps. Decent moderation for if spam bots find you. Etc.
ETA I used to host my instance on Heroku's free tier and it was more than enough for what little traffic was coming to my site.
What about blog spam though? Surely this would relinquish controls like moderation for your site?
OP here: I haven't tested how exactly this would work but I think with some tweak to the scraping script I think I could have it hide muted comments pretty easily. From there moderation would also fall back to how things work on Mastodon- if someone is posting abusive comments I can report the post and have the instance admins take whatever action necessary against the infringer.
I've been using one of the Javascript variants of this for a while. While that is a little heavier weight for the client than this completely static solution, it's ultimately just a few kilobytes and minimal processing that's fast even on old devices.
I've been using https://utteranc.es/, same concept but using Github issues as comment. This is interesting, especially if there's a way to handle each user's instances.
Just looking at the Utterances site, this sticks out:
No lock-in. All data stored in GitHub issues.
...so you can just migrate those comments somewhere else if you don't want to use Github anymore? If not, I'd call that textbook lock-in.
For what it's worth: I self-host gitea, and it gives me the possibility to import not only repos but also issues, projects, etc from GitHub, gitlab, bit bucket, and a handful of others.
I don't know if Utterances can work with gitea's API. If it does, then in theory you should be able to migrate to gitea from GitHub for this use case.
I was genuinely wondering if it was that portable. Thanks for the info!
I hope this becomes more common
That's really cool! It reminds me a bit of Cactus comments building on Matrix rooms — but different protocol, obviously 🙂