all of it, yes! though I worry about events getting too large. perhaps another kind, that relays could charge more for storing.
imagine a podcast app that publishes an event for each episode you listen to, across feeds. if I like your taste in podcasts, I'd like to follow a feed of your listens (and stream you and the content creators some sats)
there's a lot of reasons. for one, I like the idea of nostr as a distribution/notification channel, and rss has a ready supply of content. there's also the chance to disaggregate / aggregate feeds. I think value for value applies here. eventually nostr can supplant rss, by publishing notifications directly. podcasts belong here natively too. I love leaning into the decentralized nature of the platform.
nostr.io already has nostr -> rss on the profile pages. so if you go to https://nostr.io/p/[your pubkey hex] you'll see the link on the left
I haven't made it public yet, will do so soon. I'll happily tag you when I do
Also I made a browser bookmarklet that automatically generates a bridged nostr profile of the twitter account you have open in your browser. Create a bookmark and insert this as the url:
javascript:window.location.href="https://rsslay.nostr.net/create?url=https://nitter.moomoo.me/"+location.href.split('twitter.com/').pop() + "/rss"
I love hacks like this, again, thank you. I'm working on another RSS bridge, bidirectional. if you have any thoughts about how they work generally, rsslay in particular, or anything that seems relevant, please share
I'm using the existing one #[2] built that's running here: https://rsslay.nostr.net/
The source code is here: https://github.com/fiatjaf/relayer/tree/master/rss-bridge
word, the og rss bridge. thanks!
this is exactly what I was looking for, thank you both #[0] and #[1]
looking at nostrplebs.com #[0] as a solid example of offering a service for payment. have you written about your payment infrastructure? I know it's lightning, but which upstream bitcoin node, which lightning client, etc kind of details, would be nice to hear about. looking to experiment in that space as well. (not NIP05, but payment for service rendered)
geez, you are right. I upgraded my relay watchers to speak grpc to the backend yesterday, I've missed something. will fix and get the counts updated
also curious on this front. I'll put in 1000 sats per good link
this has happened with alby before. lmk if you care about debugging further, happy tohelp. otherwise I will drop it.
*receiver
the error message is noncomital, "payment failed: does the received have enough inbound capacity?"