ericpp
Eric P

@npub1ye5…knpr It seems like the new(er) version of Nostrudel requires that you set up outbox relays before you can post. Can it show an warning message or something if you don't have them set up or try to post without having them set up?
I don't use Nostr too much and it took me awhile to figure out why it was trying to post to 0 relays.

2025-12-20 18:05:44 UTC

- reply

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.

2025-12-19 22:32:39 UTC

- reply

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:
@nprofile…8m4j built Podstr and Zaptrax to host and play RSS feeds with Nostr.
@nprofile…5hgd 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.
@nprofile…zarj built http://ITDV.podtards.com to highlight the excellent musical talents of The Doerfels and also built his own music app https://stablekraft.app/
@nprofile…tf6v 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>

2025-11-23 03:11:57 UTC

- reply

They're just standard Lightning nodes that use Keysend rather than Lightning Address/LNURL/Invoices to receive payments. Most of them (other than Fountain) are self-hosted and self-custodied rather than being hosted by a custodial wallet.
Both Keysend and LNURL are ways to get around Lighting's requirement that a sender needs to ask the recipient to generate an invoice before they can pay them. There's no way to send a "spontaneous payment" in standard Lightning.
Keysend works by sending the payment with an empty invoice. The recipient's node just receives the sats and ignores the fact that there's no invoice attached. The sender uses the node's public key to send the recipient sats via the Lightning network.
LNURL works by putting a publicly-accessible webserver in front of the recipient's node who's only job is to generate invoices for people who ask for them. The sender uses the recipient's Lightning Address to look up the webserver, sends a request to the LNURL callback, and gets an invoice back. They then can pay that invoice on the Lightning network.
V4V nodes chose keysend because it's simpler and requires no additional lookups or servers in the middle of the payment process. You just send a payment from your node to the recipient's node through the Lightning network and that's it.
Wallet providers, including most of the ones the Nostr folks use, chose LNURL and ignored keysend entirely, which is why many here are unfamiliar with it.

2025-11-18 18:54:46 UTC

- reply

The Lightning network already uses other nodes to route payments. Doesn't BOLT12 just extend this concept to also route messages?

2025-11-18 18:31:07 UTC

- reply

https://github.com/getAlby/hub?tab=readme-ov-file#optional-configuration-parameters

2025-11-18 18:30:05 UTC

- reply

Well at least until the Alby Nostr relay goes down. You did switch that in the AH config, didn't you?

2025-11-18 18:02:57 UTC

- reply

That's the logical alternative to the LNURL payment flow:
Instead of: Payer -> HTTP/LNURLp -> Recipient
Do: Payer -> Nostr Relay (Hopefully not Cloudflared) -> Recipient
Of course if we adopted keysend or BOLT12, the payment flow would be Payer -> Recipient without any middlemen.

2025-11-18 17:58:01 UTC

- reply

It looks like you can fetch the offer code from NIP-01 or NIP-05 https://github.com/shocknet/CLINK/blob/main/specs/clink-offers.md#integration-with-nostr .

2025-11-18 17:40:36 UTC

- reply

It would be good for running some local LLMs

2025-11-18 17:39:24 UTC

- reply

That's the best thing about having a de-Googled phone. All of the notifications go away and you realize that none of them were ever important.

2025-11-18 17:37:00 UTC

- reply

Decentralize harder!

2025-11-18 17:32:47 UTC

- reply

Unfortunately, the most popular Lightning implementation (LND) still doesn't support BOLT12. Every major implementation except them supports it.
I would love to kick LNURL to the curb and go full BOLT12, but it can't happen until they get with the program.

2025-11-18 03:16:51 UTC

- reply

Looks like a great space!

2025-11-17 18:36:37 UTC

- reply

The only constant in life is change

2025-11-17 18:00:41 UTC

- reply

Ooo What's this? 👀

2025-11-10 18:21:06 UTC

@npub1der…xzpc I have more Castr PRs for your consideration:
https://github.com/dergigi/castr.me/pull/18
https://github.com/dergigi/castr.me/pull/19
I think the NIP-53 works now too:
https://github.com/dergigi/castr.me/pull/9

2025-10-09 16:48:32 UTC

- reply

I'm not cool enough

2025-10-09 05:05:53 UTC

- reply

I thought her emoji was 🤡

2025-09-30 18:46:08 UTC

- reply

Yessir? I didn't know there were multiple of me. That could be pretty useful in the future.

2025-09-30 18:19:43 UTC

- reply

We originally chose keysend because you can send metadata (sender name, total amount before splits, message, podcast, episode, app name, etc) along with payments through the Lightning network. You didn't need any web server or service sitting in the middle.
Keysend also just lets you send a payment without requiring the other side to generate an invoice first. Most of our feeds have payment splits in them for the podcast hosts, crew, and anyone responsible for putting together a podcast and it's a bit cumbersome to have to generate multiple invoices for every single split.
We've since updated the spec to allow for a Lightning Address to be used in the feed which allows the app to use either keysend or LNURLp depending on what the sending and receiving wallets support.
But we haven't completely figured out how to send the metadata to the recipient since LNURLp doesn't allow the same amount of metadata that keysend does. @npub1v5u…n0v5 solved the issue by posting the metadata as Nostr notes, but some in the community are reluctant to rely on Nostr or don't want their metadata to be publicly available on Nostr.

2025-09-30 16:50:59 UTC

- reply

I'm happy to help. There's a bunch of us here that understand the RSS spec. @npub177f…aaq7
@npub1yvg…6pv9 @npub19ha…q0fa @npub1yvs…wzdu to name a few.

2025-09-04 17:49:18 UTC

- reply

Yeah lnaddress/lnurlp is what we want to move towards, but the boost metadata issue has been tricky.
Keysend lets you attach arbitrary metadata (TLVs) along with your payment, which is how boosts work right now. The payments and boost metadata arrive directly to your wallet/node without any third-party involvement.
Lnurlp doesn't have the same flexibility and only gives you a 200 character comment field to use, which is too small for our purposes. We basically need a service or api or something to store the metadata for each payment and there's no agreement on how that should work.
Nostr solved this problem by having the lnurlp server post the metadata back to Nostr as a zap receipt whenever receiving a payment. There's still some ambivalence about using Nostr or any third-party service in the podcast world.

2025-09-04 17:25:55 UTC

- reply

Unfortunately you have to pick one or the other. Alby and Fountain are basically the only two that support keysend, but they're the two that most podcasters use right now. Other wallets like Strike or Primal only support lnaddress and don't support keysend.
You can look up the keysend info for a person through the well-known url. For example, my well-known (ericpp@getalby.com) is at https://getalby.com/.well-known/keysend/ericpp . That gives you my lightning node pubkey and a custom key/value for my wallet (basically a wallet id).
You can then use the pubkey, custom key, and custom value to create a valueRecipient tag:
<podcast:valueRecipient name="ericpp@getalby.com" type="node" address="02c7bb6f29f09d92d40d62d64443b688891259dea324406b4678df6235794f24bf" customKey="696969" customValue="34" split="1"/>

2025-09-04 14:31:09 UTC

- reply

@npub18am…p424 There is a small issue with your feed. The value recipient types should be lnaddress rather than lightning-address: https://sessions.soapbox.pub/rss.xml .
Also, the podcasting world hasn't fully figured out the switch from keysend to lnaddress. So if you want to see boost information (sender name, total unsplit amount, message, etc), you have to use keysend rather than lnaddress. I think Fountain might work regardless since it also posts this info to Nostr?

2025-08-31 21:59:15 UTC

- reply

I like the way Nostrudel does it. You shouldn't need to be prompted for a signature until you're actually do something that requires a signature.

2025-08-22 13:39:23 UTC

- reply

LOL. I don't understand what you did, but good work!

2025-08-21 23:52:04 UTC

- reply

Hopefully something. They've been gouging everybody for too long.

2025-08-21 17:05:26 UTC

- reply

It should be fixed up now.

2025-08-21 14:39:43 UTC

@nprofile…s2s2 I added NIP-53 support (e.g. zap.stream/tunestr.io stream) to your Castr.me project: https://github.com/dergigi/castr.me/pull/9

2025-08-20 14:26:08 UTC

- reply

I also run a node and keysend support is literally just one setting you have to turn on. I don't understand what's so difficult about supporting it.

2025-08-20 14:22:04 UTC

- reply

I do, but it would be nice to have other options besides Alby and Fountain.

2025-08-20 01:58:31 UTC

- reply

At least send but preferably both.

2025-08-19 21:30:36 UTC

- reply

What are Alby and Fountain doing to make keysend work that you're not able to do?

2025-08-13 19:12:48 UTC

- reply

Are you saying that @npub1a6c…lfrr is the new Carson Daly 😄

2025-07-25 20:28:19 UTC

- reply

Stream fight!

2025-06-30 13:17:28 UTC

- reply

Ask AI to build a GUI for Whisper for you 😀

2025-06-12 19:05:53 UTC

- reply

Yep. We're getting Gmail API errors at the day job.

2025-06-12 17:09:26 UTC

- reply

You should be able to install it from the Aurora Store

2025-05-27 21:18:21 UTC

- reply

Do they even support Bitcoin? What are they doing there?

2025-05-27 20:28:56 UTC

- reply

Mine only does the NIP-53 Live Chats (kind 1311) attached to Live Events (kind 30311) on Zap/Tunestr/wherever whereas @npub1ye5…knpr 's uses NIP-EC Ephemeral Chats (kind 23333) for standalone IRC-like ephemeral chat rooms on coolr.chat
There's also the NIP-28 Public Chats that NostrChat.io uses for chat rooms that's separate from both.
Maybe we need a new NIP to unify these chatty NIPs?

2025-05-27 16:25:51 UTC

- reply

Nice setup! What's the arcade machine in the corner?

2025-05-27 14:20:12 UTC

- reply

The podcast namespace has publisher feeds if you want to build a feed that contains all the podcasts/music that you publish: https://github.com/Podcastindex-org/podcast-namespace/blob/main/publishers/publishers.md
There's also list feeds if you want to build a playlists of podcasts or music that you like: https://github.com/Podcastindex-org/podcast-namespace/blob/main/docs/tags/medium.md#list-mediums

2025-05-27 01:33:55 UTC

- reply

Oh nice! Here's my Matterbridge one that I hacked together for the Satellite Spotlight: https://github.com/ericpp/matterbridge
@hzrd149 's is almost certainly more robust since he's an expert that all things Nostr.

2025-05-21 15:18:49 UTC

- reply

Which Nostr kinds does the Wavlake app use to find music on Nostr?

2025-05-21 01:21:46 UTC

- reply

It runs on Raspberry Pi which is ARM.

2025-05-20 22:06:35 UTC

- reply

Check out how Brrreadfan does it. He hosts everything on Github: https://github.com/Brrreadfan/brrreadfan.github.io
I would still recommend a separate server like blossom or satellite in case GitHub gets annoyed with hosting mp3s instead of code.

2025-05-17 04:32:53 UTC

- reply

Proof of Veganism (PoV)

2025-05-17 04:24:10 UTC

- reply

How much for a signed copy?

2025-05-13 22:52:26 UTC

- reply

To be fair, I do think Fountain Premium could be really useful for podcasters to have a source of sustainable monthly income. The amount of donations can vary from episode to episode and it's nice to know you have monthly income that you can rely on.
The only issue I had with your post was calling it V4V. V4V is putting the content out there (value) and asking people to contribute their value back to you in time, talent, or treasure. Putting content behind a paywall and demanding value upfront (even temporarily) is not V4V. Check out value4value.info for more detail.
I think a lot of people on Nostr equate V4V and Zaps/Lighting payments as they same thing, when one is a methodology and the other is just a payment method. People have been doing V4V long before Bitcoin and Lighting even existed.

2025-05-13 03:02:36 UTC

- reply

What did it break? Doesn't your applesauce library replace this?

2025-05-12 18:19:11 UTC

- reply

This isn't value-for-value. Value-for-value is putting your content out there and asking listeners to contribute back whatever value they got out of it in time, talent, or treasure. It's up to the listener to decide how much value they get out of the value you send out. That could be 1 satoshi or 1 million satoshis, that could be artwork or research for the show, or basically anything that is value added back to the show: https://value4value.info/ .
This is the Patreon paywall model, which does work for some podcasters. It's not v4v because you're asking for value upfront and setting both the floor and ceiling (i.e. $5) of the value your listeners to send back. Listeners who don't want to pay $5 will either not listen or find a copy somewhere else. Listeners who would be willing to pay more than $5 will still pay $5 because that is what you asked them to pay.

2025-05-11 00:06:24 UTC

- reply

Watch the revolution right now! The Satellite Spotlight is on RIGHT NOW with @npub1wzv…3tv2 @npub1w66…mgzn @redarrowhighway and @citybeach currently performing.
http://thesplitkit.com/spotlight25
https://tunestr.io/naddr1qq9rzde5xcerqd348y6qz9thwden5te0wfjkccte9ejxzmt4wvhxjme0qgsr5qnsn6medetj3vexljqqvy99gfdrgsp7hs9f52kdvrryz6gwkrsrqsqqqan8kvwknh

2025-04-17 05:56:36 UTC

- reply

Bitcoin is for everyone

2025-04-04 01:52:18 UTC

- reply

Looks like you all are celebrating tomorrow: https://first-avenue.com/event/2025-04-the-suburbs/

2025-04-03 16:56:43 UTC

- reply

Working a day job wishing I was there instead?

2025-03-14 17:33:26 UTC

- reply

I like that their deadline is April 1st.

2025-03-13 00:46:46 UTC

- reply

https://image.nostr.build/e078b977c73cb314ebf35823609212385cb2cfa3b1beb4ab846b11aaa7ad06e3.png It looks like you're trying to install Ditto

2025-03-09 22:29:12 UTC

- reply

https://image.nostr.build/a55fb507d7e2049b4c36a062d5d2ae05085ead0045403055ccd18e70649989a3.png

2025-03-09 17:31:24 UTC

- reply

I pushed out 4 PRs for your consideration: https://github.com/v0l/zap.stream/pulls
I wonder if it would make sense to combine the recorded stream and regular video content on the site and add an upload button to the recorded stream section.

2025-03-08 19:15:10 UTC

- reply

The ultimate goal of the Podcast Index is to decentralize and to not host anything. They don't want to be the single point of failure that they are right now. The index should instead be hosted by anyone that wants to host it.
They're looking at the Iroh library right now to do this, but maybe there's a Nostr way of doing this as well.

2025-03-08 18:28:54 UTC

- reply

Thanks Therapy bot. I needed that.

2025-03-08 18:27:39 UTC

- reply

I think it makes sense to have it on a distributed ledger like Hive. Anyone can host a copy of it and all of the copies are kept in sync with each other.
Having it on Nostr means you need to figure out which relays are hosting it and hoping they're up-to-date. You could do something like WebSub (which was used before Podping) and have the RSS feed indicate which relays it uses for events.

2025-03-08 18:02:22 UTC

- reply

You can use OP3 for analytics for self-hosted podcasts: https://op3.dev/

2025-03-08 05:51:39 UTC

- reply

But I don't want to!

2025-03-07 18:03:39 UTC

- reply

Does it have to be HLS or is that just what the code allows right now? I think it's easier for people to host a single mp4 than it is to host a set of HLS files. I could submit a PR to add mp4 files if it makes sense to do so.

2025-03-06 19:12:26 UTC

@npub1v0l…qj49 Do the recording urls for past live streams on zap.stream have to be HLS streams or can they be MP4 or other static video files?

2025-03-02 16:58:32 UTC

- reply

He mentioned BTC and ETH later as an afterthought https://truthsocial.com/@realDonaldTrump/posts/114093819842100196

2025-02-25 22:26:58 UTC

- reply

https://assets.podhome.fm/df3c7f87-bdab-41fe-1438-08dbf068e250/638760518309627432rundown.jpg

2025-02-21 16:24:33 UTC

- reply

How does a random hacker have access to a supposedly cold wallet?

2025-02-21 15:03:00 UTC

- reply

Aw man. Sorry to hear that

2025-02-21 07:08:37 UTC

- reply

@npub1v0l…qj49 Were dvr.zap.stream and data.zap.stream affected? I get 503 errors from dvr and 404 not founds from data.

2025-02-19 00:22:28 UTC

- reply

I like deepseek-coder-v2 for coding tasks. The self-hosted deepseek probably won't be as good as ChatGPT unless you have to resources to run the full 671b model.

2025-02-18 20:38:54 UTC

- reply

In 22 minutes!

2025-02-17 05:05:40 UTC

- reply

Yeah it was dumb. Nothing happened in the game and they just decided to fight for no reason.
It was good game once they decided to actually play it.

2025-02-17 04:45:06 UTC

- reply

It has a simple API as well to develop against: https://github.com/ollama/ollama/blob/main/docs/api.md

2025-02-14 16:18:05 UTC

- reply

Open the feed, right-click on the page, and click 'View Page Source' to view the raw feed.

2025-02-14 01:38:50 UTC

- reply

Aww man. That sucks!

2025-02-14 01:28:58 UTC

@npub12q9…70wm Did The Velvicks get into the plumbing business: http://thevelvicks.com/ ?

2025-02-13 23:48:16 UTC

- reply

Bootstrap?

2025-02-13 17:38:13 UTC

- reply

Does this include the lnaddress wallet update as well?

2025-02-03 05:53:14 UTC

- reply

Why do we need banks? Be your own bank!

2025-01-11 19:24:24 UTC

- reply

NWC all the things! I want wallet interoperability.

2025-01-11 19:21:58 UTC

- reply

I would use them if they had a less intrusive KYC process. I don't want to take a 3d scan of my face to use their wallet. Other wallets just require an ID to use them.

2025-01-07 19:29:07 UTC

- reply

Fun fact: El Salvador is Spanish for The Salvador

2025-01-06 20:06:26 UTC

- reply

Another strategy is to have both platforms defined in the same Dockerfile and then use the BUILDARCH and TARGETARCH arguments to select the correct one. That's what I'm doing for the Helipad Dockerfile: https://github.com/Podcastindex-org/helipad/blob/main/Dockerfile

2025-01-06 19:50:23 UTC

- reply

You could probably use the TARGETARCH arg to conditionally install it.
Something like this might work:
RUN [ "$TARGETARCH" != "arm64" ] || apt-get install -y gcc-aarch64-linux-gnu binutils-aarch64-linux-gnu

2025-01-02 15:25:13 UTC

- reply

https://isobot.dev/isos/greenroom/20240528-035625-rdqdBPhL-see-egg.mp3

2024-12-30 18:15:59 UTC

- reply

I'm scared to look at my number

2024-12-30 18:15:20 UTC

- reply

We wouldn't need Lightning if Bitcoin was quick, easy, and cheap to send/receive.

2024-12-28 19:18:45 UTC

- reply

They don't care how any of this stuff works. Mastodon is basically their private Twitter.