Hacker News Reader

Comment by phunehehe0 | Hacker News Reader

One thing that struck me the other day was that HN disallows commenting on items older than 2 weeks. This pretty much rules out the use case for me. I have been on the receiving end of intriguing comments that arrived after 2 years.

I would ask for Diaspora support, but after seeing that the comments will go through comments.network's infrastructure, I guess I'd rather not add that dependency.

Nice idea though, if you are cool with limiting comments to 2 weeks. I know some people do like that.

View on HN

One of the main points developing this was making it flexible on the back-end so adding new networks is a breeze. I am considering options for https://comments.network/ future, since I would love for it to grow. Would you pay say 10-15$ for making it all open-source so you can install it on your own server?

Not in my case. I accept to sacrifice some features to keep my blog static. Maybe something on the client side that pulls comments from a public source will do. Maybe even just "email me if you have a comment and I'll include it here".

Wait so you'd rather not add https://comments.network/ dependency but also not host it yourself; how would you set it up then?

Also, would it be nice if Comments network integrated comments on their own when the thread is closed? So you can just comment on the site itself (once the network comments are closed it'd basically be an alternative to Disqus).

If I cared enough I would have used something with built-in comment support, or something like stevekemp posted in a sibling of the parent (aunt/uncle?). I'm not sure I want to do that, because it seems overly complicated for little value. Just having a way for somebody reach out if they really want to is enough for me.

I setup self-hosted commenting system for my static site:

https://github.com/skx/e-comments/

It could do with some more love, to add nested comments, but otherwise it might be of interest.

Reply on news.ycombinator.com