Does anybody have a master list of all of the projects that implemented this (or something very similar) over the years? It's got to be a pretty long list by now.
The weird part is, there seems to be enough demand for this that these keep popping up, but not so much that any of them ever hang around.
There have been quite a few of them over the years in varying degrees of complexity. I think the most well-known one is probably HN Replies. A simple Github search returns the following results.
I (and probably a lot of other HN users) built my own bespoke HN suite that notifies me on replies, stories that I might be interested in, etc. It just sits quietly on a VPS and sends messages to me over Signal. Never open-sourced it because the code is a dire abomination.
Yours is probably the first Chrome side-panel variation that I've seen though.
There have definitely been a few over the years, especially if you include scenarios beyond just "get notified for replies". Some have been webapps, some have been browser plugins, etc.
> Should I update the instructions so something is more clear?
I believe they are referring to the "threads" link in the header of HN pages for an authenticated request. Can't say what the 20% is, of course. As for the 80%, it's a pull instead of a push but that page shows logged-in users their recent comments and the reply threads for them.
I spent at least 10 hours testing it yesterday. I got a lot of relief when the number badge incremented telling me that some commented on this post. Thank you.
To me the most interesting thing is the different red team adversary agents I'm using. There is a Jony Ive design critic agent which is surprisingly very good, a red team agent that does normal code review and bug hunting by injecting logging into the code running it in isolation in the /tmp/ folder, a red team agent that code reviews and find bugs in the test harnesses, and an agent that does mutation testing by breaking the code creating regressions to make sure that the test harness catch them -- I wanted to call it the trickster agent but did didn't want to drift from training and density in the LLM model.
I did a huge amount of experimentation last week discovering that if a model misses a bug or gets something wrong, running an adversary agent using the same model or family of models will not surface it. Everyone has the intuition about that but I can describe why using data. So Claude writes code that is orders of magnitude better than any project I inherited in the past 15 years and I'd have ChatGPT run all the adversaries.
In order to surface replies to posts and comments it requires huge amounts requests so I needed to figure out what the optimal request rate is based on frequency of replies over time. First posts get replies after a week so there isn't any reason to surface them. After analysis, I can conclude a request every 5 minutes in the background is enough. What is that 288 (pollComments) + 144 (author-sync) = 432 requests/day per user? I spent a couple hours on that. Actually, I started with the Hacker News API and then realized that I should check the https://hn.algolia.com/api but wanted to know which is optimal including using both. After experimentation and research I discovered that ~432 requests a day at Algolia is enough.
If one other person uses it, it is good enough for me.
If you use it and want more features, post in the issue queue or respond to one of my comments -- I'll get it.
The engine that makes the requests and does the logic is agnostic and probably is portable copy and paste into your project. The one thing I have are all the tests and red team adversary agents that do very well to surface bugs.
Can we get one which scans for downvotes on comments which are either positive or in anyway against any dominant narrative in HN?
*If you feel attacked by this comment, you know exactly what to do. Do it. Fulfill your destiny.
I just want to say please no. Comment chains where two people are arguing are the worst. Negative value. I’m always confused how they happen here, are people just refreshing their comments page waiting for a reply?
You understand the irony here? Is the issue that other people are in flame wars or that you open with negative sentiment comments and people respond in kind?
I appreciate your comment because it is an opportunity for me to test the extension works correctly surfacing your comment with little notification. Thank you. :)
The weird part is, there seems to be enough demand for this that these keep popping up, but not so much that any of them ever hang around.
Here is the proof. [0]
> yes please! i need a "comment to follow" functionality on HN
So I built it. I built this for one user named swyx. I'm going to email him now letting him know I built it.
[0] https://news.ycombinator.com/item?id=47402785
HN Notifier
https://github.com/meanands/hn-notifier
Hacker New Telegram Bot
https://github.com/lawxls/HackerNews-Alerts-Bot
HN Reply Notifier
https://github.com/lotsofnoise/hn-reply-notifier
And there have been Show HNs on them as well.
Show HN: I built an open-source notification inbox widget for Hacker News
https://news.ycombinator.com/item?id=36373123
Show HN: HN Reader – Track your conversations across Hacker News
https://news.ycombinator.com/item?id=46240221
I (and probably a lot of other HN users) built my own bespoke HN suite that notifies me on replies, stories that I might be interested in, etc. It just sits quietly on a VPS and sends messages to me over Signal. Never open-sourced it because the code is a dire abomination.
Yours is probably the first Chrome side-panel variation that I've seen though.
It is one of these services that just work.
Thank you, Dan Grossman!
Here's some discussion of one recent one:
https://news.ycombinator.com/item?id=21172406
And some more:
https://news.ycombinator.com/item?id=42814917
And HNChat, which went a little further:
https://news.ycombinator.com/item?id=12431724
That said, don't take this as criticism. It's clearly something that some HN users want. If you can make it stick, more power to you!
https://hnrss.github.io/
https://hnreplies.com
That's plenty enough to capture the 80/20 of my use case
Should I update the instructions so something is more clear?
Also what is the other 20%?
I believe they are referring to the "threads" link in the header of HN pages for an authenticated request. Can't say what the 20% is, of course. As for the 80%, it's a pull instead of a push but that page shows logged-in users their recent comments and the reply threads for them.
> A self-contained security audit prompt is available at docs/security-audit.md.
lmfao
To me the most interesting thing is the different red team adversary agents I'm using. There is a Jony Ive design critic agent which is surprisingly very good, a red team agent that does normal code review and bug hunting by injecting logging into the code running it in isolation in the /tmp/ folder, a red team agent that code reviews and find bugs in the test harnesses, and an agent that does mutation testing by breaking the code creating regressions to make sure that the test harness catch them -- I wanted to call it the trickster agent but did didn't want to drift from training and density in the LLM model.
I did a huge amount of experimentation last week discovering that if a model misses a bug or gets something wrong, running an adversary agent using the same model or family of models will not surface it. Everyone has the intuition about that but I can describe why using data. So Claude writes code that is orders of magnitude better than any project I inherited in the past 15 years and I'd have ChatGPT run all the adversaries.
In order to surface replies to posts and comments it requires huge amounts requests so I needed to figure out what the optimal request rate is based on frequency of replies over time. First posts get replies after a week so there isn't any reason to surface them. After analysis, I can conclude a request every 5 minutes in the background is enough. What is that 288 (pollComments) + 144 (author-sync) = 432 requests/day per user? I spent a couple hours on that. Actually, I started with the Hacker News API and then realized that I should check the https://hn.algolia.com/api but wanted to know which is optimal including using both. After experimentation and research I discovered that ~432 requests a day at Algolia is enough.
You should just submit a PR to OJ.
https://github.com/OrangeJuiceExtension/OrangeJuice/issues/3
If one other person uses it, it is good enough for me.
If you use it and want more features, post in the issue queue or respond to one of my comments -- I'll get it.
The engine that makes the requests and does the logic is agnostic and probably is portable copy and paste into your project. The one thing I have are all the tests and red team adversary agents that do very well to surface bugs.
I was thinking allowing people to follow users so they get a stream of posts and comments from users they are interested in the side bar
You understand the irony here? Is the issue that other people are in flame wars or that you open with negative sentiment comments and people respond in kind?
I appreciate your comment because it is an opportunity for me to test the extension works correctly surfacing your comment with little notification. Thank you. :)