Our great sponsors
-
awesome-nostr
nostr.net - awesome-nostr is a collection of projects and resources built on nostr to help developers and users find new things
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
It sounds interesting but I use https://hnrss.github.io/
Unless it had most of the features of hnrss.org I would not be able to use it.
Perhaps you could pivot your approach and submit a PR to hnrss for the feature?
Everything is a website these days.
Even code commits. https://github.com/torvalds/linux/commits.atom
Completely agree. Like the parent poster, I never subscribe to newsletters and the sites that don't offer good ways to be updated of new content (e.g. RSS feeds) lose me as a visitor.
There are, however, a few email to rss tools, a quick search brings this one as the top reasult: https://github.com/leafac/kill-the-newsletter
Might be a good workaround in case the content on the site is worth it.
https://github.com/nostr-protocol/nips/blob/master/65.md
The TLDR is that when a Nostr client supports NIP-65, it broadcasts to all known relays (which is continually updated/expanded) the list of relays that User A posts their stuff to.
This means that as long as User B is connected to at least one of those "all known relays", their client now knows what relays User A posts their stuff to, and will specifically fetch things from those relays when it needs to load User A's things.
It's essentially the Nostr take on the Gossip protocol: https://en.wikipedia.org/wiki/Gossip_protocol
There is JSON Feed¹ already. One of the spec writers is behind micro.blog, which is the first place I saw it(and also one of the few places I've seen it). I don't think it is a bad idea, and it doesn't take all that long to implement it.
I have long hoped it would pick up with the JSON-ify everything crowd, just so I'd never see a non-Atom feed again. We perhaps wouldn't need sooo much of the magic that is wrapped up in packages like feedparser² to deal with all the brokeness of RSS in the wild then.
¹ https://www.jsonfeed.org/
² https://github.com/kurtmckee/feedparser
Just a GitHub. [1]
It's very early days still, but I use it myself.
The marketplace [2] is much more advanced! You can already use it to buy and sell stuff over Nostr!
[1] https://github.com/servuscms/servus