Hacker News Reader

Comment by benfrain | Hacker News Reader

“It’s all about the comments”. All these static site generators are fine but they can’t deal with comments. Then you have to add a commenting system from a 3rd party, at which point you may well wish you’d just gone with a PHP/DB solution from the beginning

View on HN

I just ditched comments entirely and don't miss them. Comment volume didn't change, but people email me now instead.

> people email me now instead.

And then you manually add that to the article or just keep it to yourself?

A little of both. This is for a fairly low-volume personal tech blog so of course this wouldn't really scale. When I do add a comment to one of my pages it's not presented in the typical comment thread way but more like an edit that thanks the person and rephrases what they had to say.

You can use webhooks for this. As an example: https://staticman.net/docs/

Got rid of comments altogether as being generally Far Too Much Headache given the cohorts of spammers, bots, trolls, black-hat pen-testers, etc., etc. If anyone reads my website (Hi! to both of you...) and wants to comment, there are contact details right there with various ways to reach out. If it ever got to the point where there was a 'community' (dubious concept, that) developing, well,... just set up a subreddit, IRC or Riot channel or something.

Well I just launched fastcomments.com which you could use :p

https://fastcomments.com/

I appreciate the pricing~

It isn’t clear to me what the individual tier allows, except for the pageview restriction. There is no FAQ or Support link on the homepage. Is it one domain where all sub domains can have comments enabled? Or is it one subdomain in a domain? Or is it all (disparate) domains owned by an individual?

Yeah right now you have to have an account, then you have direct access to customer support via the UI.

A FAQ page I should put together, that's correct.

Your questions:

1. The tiers differ in pageview restrictions and developer support access. The highest tier provides migration support for the platforms that don't have automated migrations today (you can import from Disqus, Commento, and a couple others).

2. Right now domains are unlimited and validated at TLD. When you sign up just enter the sites you want to use like.com, this.org. For example, I dog-feed it on my blog at blog.winricklabs.com, but I only have winricklabs.com on my account.

Are there any plans to add a free tier without support or migration for say, less than 100k views a month? The pricing seems pretty neat if you're closer to the limit of the pricing ie one million page views but if you're at the other end of the spectrum then it's significantly better to go with a free solution

Don't want to support a bunch of free customers at the moment. Maybe later.

I think it's a good call.

For the sake of clarity, if I have 2 domains, is it $4.99 per domain, or can both domains come under a single $4.99 charge?

Both as a single charge.

Thanks. HN helped with it! :)

What happens if you shut down the service, are there any guarantees on availability? How can I export my data and could I import it somewhere else reasonably easy?

You have full access to your data via the UI (csv exports all db fields).

Do you have a react component for this ?

You mean as a wrapper? I'm not familiar with react as an Angular guy, but do you need one - could you plop the HTML into the page? All the client side script does is insert an iframe and control its size.

I'll look into making a React component.

react does not play well with non-react javascript

> react does not play well with non-react javascript

I'm work on a somewhat older project (circa 2015) that started without react, and have also found that to be the case.

End-all-be-all web frameworks seem to be the rage now, but I'd prefer to see a solid library of micro-frameworks that can be stitched together (like jquery plugins, but better).

Also, the idea of a web server transferring over a huge javascript library and app just to load a single page seems wrong. There has to be a better way, a better amalgamation between server and client.

to be fair, the problem seems to be in the jquery side. It was not built to play well with others.

Also React fundamentally assumes it is the only one modifying the DOM through its virtual dom. If something else changes the DOM (like jquery), then React falls through.

I won't be doing that! Offering a full react version.

I'll just write the client in React then. It's like 30 lines of code that pulls in and resizes the iframe.

Who did you quote? ("It’s all about the comments" )

I'm curious about what you think about Talkyard-blog-comments https://www.talkyard.io/blog-comments (I'm developing it), in comparison to a PHP+DB approach? (Pros & cons? if you have time)

check out FactorJS

Reply on news.ycombinator.com