I built RSSext because I didn’t want to pay only to get notifications from the blogs I follow, and suffer the noise and the suggestions of those platforms, nor to be trapped in a silo with infinite unread counters and scrolling, nor to consume stolen content scraped for AI. I didn’t want a reader, I wanted a Sentinel. A simple tool that notifies me softly and helps me sort the incoming.
On the technical side, I went to full standards compliance for lightness, efficiency and accessibility. The package of ~80KB includes Vanilla HTML/CSS/JS code, icons and 17 languages. Users can set their own polling frequency and retention delay according to its own use. After that delay, the left-behind is cleared, because this extension handles signals, not content.
Everything is local, no backend, no accounts, no ads and no tracking. This utility sends you straight to the publisher’s web site, in full respect of their analytics and advertisement policy. It’s the result of ~30h coding, so it sure ain’t perfect. I’m curious to hear your thoughts on this "local-first" approach and the evaporation logic. The code is public, and I’m ready for the "Show HN" roast.
I built RSSext because I didn’t want to pay only to get notifications from the blogs I follow, and suffer the noise and the suggestions of those platforms, nor to be trapped in a silo with infinite unread counters and scrolling, nor to consume stolen content scraped for AI. I didn’t want a reader, I wanted a Sentinel. A simple tool that notifies me softly and helps me sort the incoming.
On the technical side, I went to full standards compliance for lightness, efficiency and accessibility. The package of ~80KB includes Vanilla HTML/CSS/JS code, icons and 17 languages. Users can set their own polling frequency and retention delay according to its own use. After that delay, the left-behind is cleared, because this extension handles signals, not content.
Everything is local, no backend, no accounts, no ads and no tracking. This utility sends you straight to the publisher’s web site, in full respect of their analytics and advertisement policy. It’s the result of ~30h coding, so it sure ain’t perfect. I’m curious to hear your thoughts on this "local-first" approach and the evaporation logic. The code is public, and I’m ready for the "Show HN" roast.
Try it directly from the Chrome Web Store: https://chromewebstore.google.com/detail/rssext-feed-sentine...