HNRelevant VS notiflux

I made HNRelevant, a web extension for HN (https://github.com/imdj/HNRelevant).

The extension adds a section for related discussions for each submission page. Many times, I found myself intrigued by interesting discussions which left me hungry for more and I'd go down a rabbit hole, or maybe it was promising but didn't get enough attention and I'd need to check if there were any related discussions in the past about the same subject.

I found that even though HN is a news aggreagator, many discussions on HN are timeless (just like this here).

I'm proud of it and find the experience and flow to be very enjoyable. It also helps me find great stories that I might not have stumbled across.

You can use userscripts [1] which is a safari extension which allows you to add userscripts, and the author of this work have an userscript [2] that you can use with safari (or any other browser)

[1] https://github.com/quoid/userscripts

[2] https://github.com/imdj/HNRelevant/blob/main/HNRelevant.user...

This is an extension for hacker news that I made some time ago and shared here initially at the very beginning.

It's basically hn.algolia.com integrated into the HN.

I found that a lot of posts have more backstory to it, and maybe there were similar posts in the past with valuable discussions that the current post may fall short on or just didn't reach enough people.

It display relevant submissions in intergrated sidebar right in the page you're on, for smooth experience & native look (it rely on the same stylesheet).

The plugin is available on Chrome, Firefox and as a userscript.

Github: https://github.com/imdj/HNRelevant

It was actually couple of weeks ago, but a small project that took mostly just two days to put together and I'm pretty happy with how it turned out.

Notiflux (https://github.com/ikornaselur/notiflux): a small WebSocket broadcast server, the idea being that clients connect with WebSocket (such as a website) and then any source can send a POST request to the API to broadcast messages, allowing for real-time functionality from servers that don't support WebSockets, or you might have multiple sources that each might broadcast messages.

Auth is done by Notiflux having a public key and the sources have the corresponding private key, JWT tokens signed with the private key include topics and scope (subscribe or broadcast to the topics). Clients would auth with an API for example, get a JWT with maybe a 10 second expiry, use it to subscribe to the topics that the API would then broadcast to through Notiflux.

It was an excuse as well to play with WebSocket in Rust and learn a little bit about the Actor Pattern.

If I would continue I'd want to explore how well it scales, how much traffic it could handle and look into horizontal scaling, but I feel like it's complete enough as a toy project.