How long will you be able to sustain this? I have a fairly small site that has virtually no traffic, so I would love to use this but what happens if you end up with a large number of sites using this? And assume that the donations don't cover the expenses. Do you have a fallback plan?
Hi! Sorry if I'm missing something. I do not understand how to pay you? Clicked around the site for a bit and couldn't find some self evident thing I can do to send you any given amount of money; my employers might find the idea of this being a paid service a bit more easy if I try to push this to them for use on some of our microsites
... here's a weird thought. Could you have a free and paid tier split based on overall traffic, but pass the paid tier cost onto the user? ie, when the quota is reached (say an article trends on HN surprisingly), the comment box pops up a paywall, but any user can foot the bill, and then everyone else gains the benefit, including the site owner?
This idea of anyone can pay is actually really compelling for a service like this.
Not just giving a boost to small passion projects, but I’m thinking about stuff that’s abandoned by the creators for whatever reason. Community could simply keep things going in their absence and that is interesting.
I really like the idea and the implementation looks nice! But not having any type of spam protection is a deal breaker for me. Even if links are set to nofollow, it's still a big opportunity for bots and spammers to abuse this system and spread their links, similar to what is happening to misconfigured wordpress sites.
Thanks for the feedback. I'll add Akismet integration to the backlog for people with the same objection. Allowing people to pass an API key to their Namespace shouldn't be too difficult but I'll need to build out a UI for separating ham versus spam which might take more work.
In the Namespace settings you can force all comments into moderation before displaying to the page. This would be the best option for you in the mean time.
One quick win that might catch most of the bots is using CSS to hide an dummy form input.
No human will see it if their browser properly renders, but bots using CSS selectors might fill it in. If you see that field is filled in then you have a high probability of it being a bot and can drop it.
Regarding the hidden form input, make sure you aren't blocking screen reader users/the visually disabled accidently. Make sure you can't end up in that input with the tab key.
I've found that comments submitted in less than 7 seconds from page load are spam. On a few low traffic sites I just discard anything faster than that.
A few bots seem to load a page, wait a while, then come back to it. But by and large they seem to try to submit the comment immediately after page load.
Mind you, this was on low-traffic sites. High traffic sites I'm sure see more varied techniques.
I love the project but consider integrating oopspam (https://oopspam.com) instead of Akismet. Akismet is basically adding a tracking. People from the EU cannot use it with Akismet.
Unfortunately I remember Disqus as doing the exact same thing when they came out of the gate. “It’s awesome: you can now have effortless comments on static sites!”
It got installed everywhere, they trojan horsed ads, and I feel like they might be the grandparents of those 6-panel “one weird trick doctors don’t want you to know” boxes.
Does it auto-identify the page by URL, or can I specify an ID of some sort in the "code snippet" vaguely mentioned? I do have canonical URLs for all pages [1] but some pages have more than one URL.
Yeah, if you click setup and follow the prompts, the service will give you a snippet of HTML, drop that into your pages and it should work.
If you want to see the snippet, view the source code of any page which has Remarkbox embeded for an example.
It will use the URL to determine the thread by default, you can hack this code and provide an id instead, but please make sure you Namespace the thread_uri with your domain, otherwise you will not be able to moderate the comments.
Finally Remarkbox works without Javascript, and will enhance the experience when Javascript is enabled.
Supporting `<link rel='canonical'>` sounds like an interesting idea though, we should build that into the snippet or back end.
I've been using utterances (github issue tracker powered comments) on my website. Seems better than Disqus (lighter, less tracking) but it requires a github account.
