I guess I confused blips and bolts. But it has been around for 5 years now and is supported by all the major lightning implementations.

It's not the applications that are the issue. Most of them already support lightning addresses and keysend. The issue is that the majority (95%) of feeds still use keysend addresses and anyone using a lightning address-only wallet can't send payments to a keysend address.

Keysend was ratified as bLIP-003 and is part of the Lightning Network protocol: https://github.com/lightning/blips/blob/master/blip-0003.md . It's true that LNURL is preferred nowadays, but keysend is still perfectly valid.

For LND, you use the same SendPaymentV2 call that you use to pay invoices to pay keysend: https://github.com/Podcastindex-org/helipad/blob/main/src/lightning.rs#L74-L134 . The only difference is you provide it with the node address, hash, and preimage rather than the invoice (payment_request). I would be happy to implement it if your software was open source.

NWC is a protocol that connects apps to wallets and supports paying invoices and paying keysend. Wallets can choose to support one or the other or preferably both.
https://github.com/nostr-protocol/nips/blob/master/47.md#pay_invoice
https://github.com/nostr-protocol/nips/blob/master/47.md#pay_keysend

The reason we prefer keysend is because it doesn't require a bunch of extra LNURL/HTTP infrastructure to make it work. Your wallet pays another wallet directly on the Lightning Network and that's it.

CoinOs's implementation is NWC-only as far as I know. Here's the relevant (Core Lightning) code from their repo:
https://github.com/coinos/coinos-server/blob/master/lib/nwc.ts#L293-L330
https://github.com/coinos/coinos-server/blob/master/lib/payments.ts#L499-L534

Here's Alby Hub's LND implementation:
https://github.com/getAlby/hub/blob/master/nip47/controllers/pay_keysend_controller.go
https://github.com/getAlby/hub/blob/master/lnclient/lnd/lnd.go#L497-L589

The main ones that support NWC right now are v4vmusic.com, Castamatic, and StableKraft.app. Podverse is adding NWC to their 2.0 version. The other apps have historically used the Alby API directly, but we're working to get each of them to adopt NWC.

Would you consider implementing the ability to send a keysend payment from Rizful? A lot of the Podcasting 2.0 music and podcast feeds still use keysend and it would be great to use your NWC wallet with v4vmusic.com, Castamatic, or any of the other podcast/music apps.

I understand the issues with not wanting to implement receiving keysend payments, but sending keysend payments is pretty trivial. CoinOS is doing a similar thing where their NWC implementation supports send but not receive.

🧠 dumb relay, dumb client. Write the JSON yourself.

Wow this looks great!

I think Nostr is great for discovery. The only method we have for RSS right now is a centralized database called the Podcast Index. We could use Nostr relays to decentralize that index and provide a way to share music and podcasts with friends and others.

I don't think Nostr is suited for hosting content. RSS is a simple text file that you can host on any webserver along with your MP3s. Webservers are very good at serving small static files like RSS at scale and can do 10k requests/sec out of the box. Compare that to Nostr, which can take multiple seconds to find a single piece of content spread across multiple relays.

The problem with RSS is the user interface. Many people want a simple user interface for it and don't want to learn how it actually works. We do have https://musicsideproject.com and https://sovereignfeeds.com that let you fill out a form to generate an RSS file. You still need a place to put that file and some people don't want to learn how to upload files to webservers either.

I think there's a good opportunity to combine the strengths of each technology and build something great. You could build a Nostr app that uses Nostr relays for podcast/music discovery, uses RSS to build podcast/music feeds, and uses Blossom to host the RSS feed and MP3s on a webserver for you.

We had that one magical night and then went our separate ways. It sucks.

We did build some cool apps to hopefully bridge the gap:

@Derek Ross built Podstr and Zaptrax to host and play RSS feeds with Nostr.

@Sir Libre built a killer V4V music app https://v4vmusic.app that has all the features you'd want in a music app including Nostr logins, community ratings, spam filtering, playlists, live streams, publisher tags, podroll, and more.

@ChadF and 33 others built http://ITDV.podtards.com to highlight the excellent musical talents of The Doerfels and also built his own music app https://stablekraft.app/

@Gigi built https://castr.me that automatically publishes media in your npub as an RSS feed.

I would invite anyone who wants to help to check out some of the vibe coding tools that are now available, like Shakespeare, Cursor, Claude, Codex, and Gemini. Many of the apps I referenced were coded by people who have never coded before. It's never been easier to build something and be the change you want to see in the (Nostr/RSS) world.

<promo>
The RSS crowd is having another live concert on January 9th at 7pm to celebrate the release of So Big's new album: As If.

The concert is going to have a lot of surprises based on your zaps and boosts so tune in! It will be streaming on all of your favorite podcast/music 2.0 apps as well as on Nostr/Tunestr.
</promo>