Hacker News Reader

Comment by speps | Hacker News Reader

Similar to this, except this one has Reddit comments as well : https://embedd.io/

https://comments.network/ allows Reddit comments as well, but I just titled it accordingly to this page (:

And it works with url instead of story id by searching on HN or Reddit. Does it overwhelm browser by searching url like that?

- comments.network seems to use internal api[1]

- embedd.io directly request HN and Reddit

1: https://comments.network/api/

I see they are using Algolia to do the requests (at least for HN) on the front-end. Unfortunately it is limited, as you cannot get from there whether the current thread is opened for comments or whether the comments are opened for reply. That's why I'm parsing Algolia AND HN's website for each of the comments, to mix the data. Also it makes it easier doing the work on the back-end to add new services and not depending on a 3rd party. See the changelog on the bottom of https://comments.network/ to see those bugs fixed really recently.

I understand, but comments.network js snippet will stop working if you stop your server (comments.network/api), which is a 3rd-party service. Am I right?

Right now (alpha) yes, but I'm exploring other options for its future. Do you have any idea? I want to avoid fragmentation initially so open-source right now is not viable as I cannot support many different pre-releases from different users, but I've definitely considering open-sourcing it in the future ( see http://github.com/franciscop/ ).

For the sake of it I will point out that the alternative, is actually two different third-parties dependencies, http://embedd.io/ snippet and https://hn.algolia.com/ service (;

Since HackerNews itself use algolia, I think its safe to use it. And embedd can easily switch to official HN api.

I just saw that network.comments use internal api too for Reddit while it have a clean json API. I think it could be nicer for network.comments to be more transparent and to not depend on third party like network.comments internal api. In order to prevent servers maintenance and to give more privacy.

Imagine tomorrow, network.comments seduce every hackers on the world and have more than 100k blog are requesting network.comments/api server. You'll ask guys to install their own instance which is not your first goal to avoid installing stuff.

And there are a few self-hosted "external comment" systems out there, including my own simple one:

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

I will be checking it and the alternatives for the server-side if I decide to also include an in-page comment system, thanks.

But you probably shouldn't boast about the size "as simple as including a 5k Javascript file" when you have a dependency/require jQuery for your project to work on the client side (which is also not disclosed as it's only in an example, which could mean it's only for that example but checking the source it's an actual dependency)...

I'll rework the text to make it more explicit, and less boasty, but that really wasn't my intention.

I'm gonna be overhauling it over the next few weeks to support nested comments, and can almost certainly drop jQuery at that time too.

Reply on news.ycombinator.com