Steven Bell :pci: :pc2red:

Bug Reports Here:
https://t.me/+NCqewc8q0eU4NzYx

https://getalby.com/p/steven

Artisanal Coder.

You may know me from such apps as: LNBeats, The Split Kit, Sovereign Feeds, Music Side Project, CurioCaster, &
TranscriptSearchTool

Bug Reports: https://t.me/+NCqewc8q0eU4NzYx
GitHub: https://github.com/thebells1111/
LN Address: steven@getalby.com
Nostr: npub1yvgrrzf4dnmu30qfhw95x87ruu0g2kpv3a64h8hpvqsre8qeuspsgd6pv9

Public Key

npub18a6x0kawfw7vjy097psqwy7v7ly4z5ac3u2tpqr3u3v2uvk467esdepny4

NIP-05 Address

stevenb_at_podcastindex.social@momostr.pink

Profile Code

nprofile1qqsr7ar8mwhyh0xfz8jlqcq8z0x00j232wug799sspc7gk9wxt2a0vcpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsaudpyj

Publishing to

relay.damus.io

nos.lol

Author Public Key

npub18a6x0kawfw7vjy097psqwy7v7ly4z5ac3u2tpqr3u3v2uvk467esdepny4

Show more details

Last Notes

2026-05-14 02:42:07 UTC

I’ve been doing some vibe coding. It’s faster… I think. But it’s exhausting. I can’t quite place my finger on what it is. It almost feels like I’m in a constant argument “No, not that, this, and why did you change the styling. Go back to the old style.” When I’m done, I don’t feel relief like I did when I solved a problem. It’s almost a quiet resignation, like “Well, I’m glad that’s over.” I somehow feel more mentally drained and wonder what exactly I’m trading in for the speed.

2026-03-19 18:14:40 UTC

- reply

https://curiocaster.com/rss/feed.xml
https://podcastindex.org/podcast/4935828
The picture shows the test tag. I have a socket connection going 24/7 that broadcast a new liveValue every 30 seconds. Just connect to the socket and parse the JSON that's returned.
https://cdn.masto.host/podcastindexsocial/media_attachments/files/116/257/197/868/547/192/original/3e5376a2d1ebe726.png

2026-03-19 14:39:03 UTC

- reply

The JSON structure has a bunch of stuff that isn't needed for most apps, it's internal stuff I use with The Split Kit to talk to other programs (like mAirList), so don't get to hung up on that structure.
I suspect that structure will change as we brainstorm. What I'd like for us to agree on is how things like Title/Song, Author/Band, Podcast/Album should be labeled so everyone is on the same page.

2026-03-19 14:34:10 UTC

- reply

I'll try to put together a working livestream feed in a few days with dummy liveValue tag that changes every 30seconds so you can test and develop.
I also have this which is just an html file with some JS so you can see what's going on under the hood on the client side.
https://codepen.io/editor/S-B-the-typescripter/pen/019d0407-7f0c-750f-9c76-1ab1520f1c6d

2026-03-19 14:31:04 UTC

- reply

I agree on the RSS naming conventions, so would like to come up with a json file structure we all agree on.

2026-03-19 02:50:36 UTC

@npub1p7v…qql0 @npub1wd7…8l2x
Are either of you planning on implementing liveValue into your apps? It's an unofficial tag, but CurioCaster and @npub1qvx…hseu support it.
Think of it as a live chapters block and live value block that gets sent over a websocket during a live show.
I'd like to discuss a format that makes sense and modify the proposal so everyone can agree on a good format for the tag
https://github.com/Podcastindex-org/podcast-namespace/discussions/547#discussioncomment-16201182

2026-02-20 15:47:19 UTC

@npub1778…53yq
Here you go dude, an easy place to send your podpings.
https://podping.me/

2025-07-04 00:15:45 UTC

I have a friend looking for a job. She does mostly front end work. If any of your companies are hiring, I'll send her your way. https://www.linkedin.com/in/haliekoehler/

2025-06-18 00:17:03 UTC

- reply

I know it's not part of the spec, but something that would also be nice is an imageUrl. That way an app can display the image and the title without doing a bunch of calls to the feed and parsing it, only when the person actually clicks the item.

2025-06-17 13:40:47 UTC

- reply

Totally agree. Very confusing example.
I think at a minimum, all examples should include a bare minimum example, and a kitchen sink example. (Says the guy that won't be updating the repo)

2025-05-31 12:57:52 UTC

- reply

4 is the big one. Fountain happens to run their own relay, so it would end up becoming the de facto one most people used. Any one can run a relay, it’s just a server, but if we’re going to require people to run a server or use their host’s server, I’d prefer we’re doing it on REST server instead of a nostr server.
Storing and displaying TLV records has always required a server, the wallet providers just handled that for us.

2025-05-28 12:56:14 UTC

- reply

I totally agree, and the valueBlock is extremely open. The competing goals of interoperability and being open to other protocols is a a two edged sword for sure.

2025-05-27 17:42:15 UTC

- reply

v4v isn't metadata. v4v was PayPal and checks and gold coins and any other way you want to support a show, well before we started lightning payments.
But this does break the metadata, I agree. And I've tried to suggest solutions to address that. However, lnaddress is the direction everyone but PC2.0 is going. As much as I hate it, I can't deny it. I prefer keysend, I've just conceded that we've lost that battle.

2025-05-27 16:19:25 UTC

- reply

It's been in the spec for almost a year now. I think any of the apps wanting to do it have had ample time.
I actually think this is a good move, and you guys should move forward with it with your transition, that way you don't have to go back and update your feeds later.

2025-05-16 15:20:14 UTC

- reply

You can add it manually in the Manual edit in SF.
I can add it. But it adds to bloat.
I'm a podcaster. I see a field for title and another one for itunes:title.
Here's what I'm thinking:
WTF is this?
Which one am I suppose to use?
Why not just have one thing called title?
This is so confusing. This host sucks.
As a hosting provider, I want to avoid that, so I simplify. Maybe they don't get the full functionality. They don't care. They want ease.

2025-05-11 04:25:24 UTC

- reply

My hats off the Podcasting 2.0 community. They really understand what v4v is all about. This event was a hallmark of the time, talent, treasure model, and I couldn't be more proud of what was accomplished tonight.

2025-05-11 04:22:35 UTC

We just stress tested The Split Box. It was able to support the Satellite Spotlight, an event that sent 2.2 million sats worth of boosts, 1.2 million of them being through TSB.
The means the listener was able to scan a QR code from the wallet of their choice, and over 20 splits were handled on the backend.
This means you can paste your QR code on fliers, merch, the drumkit, and your fans can boost from the wallet of their choosing and each band member gets their split.
https://cdn.masto.host/podcastindexsocial/media_attachments/files/114/487/271/805/313/365/original/18cf4b792babf55c.png

2025-05-10 23:03:39 UTC

It has begun!
https://www.thesplitkit.com/spotlight25

2025-05-06 12:29:32 UTC

- reply

Imagine this, it has a time stamp or audio url on it as well, so you can walk to an area, geofence recognizes where you are, and it jumps to that spot in the audio and starts playing. It would be like a choose your own adventure podcast.

2025-05-02 20:38:35 UTC

- reply

Okay, and then the app displays the og:title and og:image.
It's not exactly intuitive, but could totally work without modifying the tag.

2025-05-02 20:36:31 UTC

- reply

Oh yeah!!! I hadn't considered OG images.
I'm not following what you need by node values though.

2025-05-02 19:26:24 UTC

The Funding Tag is your own sovereign linktr.ee
I'm pretty sure it can very easily be extended so it can be a direct clone, available in all apps.
Looking at these linktr.ees, if we add an img attribute, and something so you can tell the app what 'group' the item goes in, we pretty much have linktr.ee in the feed.
https://linktr.ee/hbo
https://linktr.ee/selenagomez
https://linktr.ee/hoe_math
https://linktr.ee/comedycentral
https://cdn.masto.host/podcastindexsocial/media_attachments/files/114/439/858/561/400/549/original/e2010aff208a0028.png

2025-05-01 12:00:53 UTC

- reply

You free to jump on a call later tonight? I can walk you through things and answer any questions.

2025-04-30 13:05:01 UTC

- reply

I wonder if your time 'might' be better spent figuring out how to implement Hive in the value block. I don't know if it's a better solution, but perhaps it addresses some of the pain points we're having with lightning.
IMO, a perfect solution would need at at least:
SPLITS!!!!!!
Micropayments.
Easily convertible to fiat.
A dead simple wallet that a mid-wit can figure out and fund
Programmable.
An easy API for an app dev to figure out.
Anything else???

2025-04-30 11:18:24 UTC

- reply

I’m not sure any of the apps support it, and until we move away from node addresses in the feed, I don’t know that they will. With NWC there’s several wallet options you can choose to connect your wallet to the app, but most wallets don’t support keysend, so won’t be able to send payments to most Podcasts

2025-04-29 20:50:51 UTC

- reply

Might be a bad address in the feed. @npub1ma9…vt3t is updating it.

2025-04-29 20:39:59 UTC

- reply

And look at all those splits going out back out!!!
https://cdn.masto.host/podcastindexsocial/media_attachments/files/114/423/181/871/190/636/original/8d6cb7af510c2219.png

2025-04-29 19:57:11 UTC

It's coming.... 5/10/25
One QR to rule them all,
one QR to find them,
One QR to bring them all
and in the darkness bind them.
One QR code, multiple splits, splits can change on your command, in real time.
Verify the splits were made.
https://thesplitbox.com/metadata/d5def5f7-63da-4292-9ff8-18fb7fdc18fe
https://cdn.masto.host/podcastindexsocial/media_attachments/files/114/423/002/595/551/910/original/25c6abe7538747ca.png

2025-04-21 13:57:20 UTC

- reply

Only 12-24 months to go... according to AI.
https://cdn.masto.host/podcastindexsocial/media_attachments/files/114/376/299/666/375/539/original/e1e398bbbc685e9e.png

2025-04-18 13:51:41 UTC

- reply

If it's their data, then they can pay for the servers and code base maintenance required to access their data. Why should they get it for free?
If an app decides to send it because it's no extra work for the app, or they just want to be good guys, that's cool, but if the app has to pay a team to develop the code to send the data, what incentive do they have to do so?

2025-04-01 13:53:44 UTC

- reply

I also have this https://github.com/thebells1111/live-updates
which a bare bones server/client than anyone should be able to use to build their own broadcasting system. As long as we all agree on the same json format, TSK doesn't need to be the only app sending out liveEvents.

2025-04-01 13:23:43 UTC

- reply

Nah, it's all open sourced, and @npub1z6g…amwj knows what's going on with it.
It's not a single point of failure by design, I'm just the only one doing anything with it right now.
It is literally a json file over a websocket. I don't know how to make it anymore open than that.
https://github.com/thebells1111/curiohoster
https://github.com/thebells1111/thesplitkit

2025-04-01 13:20:48 UTC

- reply

Then when we did live music and VTS, I though I could mod it to change albums instead of speakers. I just kind of tacked it on, then Boo-bury got involved, and it's turned into the Rube Goldberg machine you find today.
2/2

2025-04-01 13:20:12 UTC

- reply

It actually started as an idea I had when Adam and Dave where talking about doing a Bitcoin conference, I wanted a way to change the picture on a screen of who was talking and update the QR code with their lightning address so the current speaker could be boosted in real time.
1/2

2025-04-01 13:02:55 UTC

- reply

TSK is quite a bit more than a broadcaster for liveEvents. If someone one just interested in sending liveEvents, they totally can without using TSK. It's just a json file sent of a websocket.
I suppose someone could use my socket server rather than setting up their own, and their app sends the correct message to TSK, and then TSK rebroadcasts to all the clients, but I'd have to quite a bit of work to change how my authorization for who's allowed to send updates works.

2025-04-01 12:55:47 UTC

- reply

Now I have an endpoint looking for eventGuid, feedGuid, and itemGuid. It parses those from the query, looks up the feed and item from the Index, connects to your event over socket.io, and sends the stuff to build a block automatically.

2025-04-01 12:55:11 UTC

- reply

If the artist is using TSK, then they create an event in TSK, which gives them an eventGuid. As they add new block to each event, a new blockGuid is created. Those are used internally. Those don't really need to be in the mp3, that's left over from an old method.

2025-04-01 12:40:29 UTC

- reply

https://sfyl.b-cdn.net/BTC%20Minstrel%20-%20A%20Collection%20Of%20B-T-Sea%20Shanties%20-%20The%20Ballad%20Of%20Bitcoin.mp3

2025-04-01 12:38:14 UTC

- reply

Then you just need to broadcast the liveEvent over socket.io and put the server url in the feed so the apps know which socket to connect to.
Right now, Podcast Guru and CurioCaster are the only two apps listening for liveEvents.
Here's the discussion, and what data the apps are getting looks like.
https://github.com/Podcastindex-org/podcast-namespace/discussions/547

2025-04-01 12:34:07 UTC

- reply

So, there's no need to have metadata in mp3 for liveEvents to work, but your app may need it if you're deciding to use TSK to broadcast your events, and you want your player to be able to talk to TSK to automate the process.

2025-04-01 12:32:25 UTC

- reply

The radio station could send out the data the apps are looking for over socket.io. Right now, TSK is the only liveEvent broadcasting app, so someone either has to build their events manually, or send a feedGuid and itemGuid to my endpoint so I can build the events automatically. I put that info in the mp3 files they download from TSK so they don't have to look it up, their software can just send what's already in the metadata.

2025-04-01 00:10:28 UTC

- reply

Once the show goes to recorded podcast, all of those live events can be converted to VTS and chapters in the feed.

2025-04-01 00:09:09 UTC

- reply

It’s a tool I developed to send live info to any of the apps listening to the socket.io event found in the feed. By listening the app can get live data from the podcaster, think live value blocks and live chapters that update in real time on any listening app.

2025-03-31 20:52:55 UTC

- reply

If you drop an mp3 download from TSK into a metadata reader like this https://www.metadata2go.com/result#j=74918a66-cbea-4ab1-925b-38381a8c770c You'll see I'm adding the stuff that needs to be read and sent to TSK. Again, it's built for mAirList, but if Azurecast is able to send data, I can build something around it. I really just need the feedGuid and itemGuid if you're trying to play a song and it builds your TSK event in real time.
https://cdn.masto.host/podcastindexsocial/media_attachments/files/114/259/014/896/513/152/original/d43226516e0d1e56.png

2025-03-31 20:47:45 UTC

- reply

But any software that can send the eventGuid, feedGuid, and itemGuid whenever the song changes would work.

2025-03-31 20:47:01 UTC

- reply

When you download the mp3 from TSK, I add some extra metadata into the mp3, stuff like the eventGuid, blockGuid, feedGuid, and itemGuid. Software like mAirList is able to read that metadata, then send it to an endpoint I have. Depending on the endpoint, it either adds and activates a new block to your TSK event, or it activates an existing block.
@npub1fmx…wp74 and @npub16rt…fjkv use mAirList for building/broadcasting their shows, so that's what it's built around.

2025-03-31 20:41:12 UTC

- reply

I'm not sure how Azuracast works, but if it has a way to read the metadata from an mp3 downloaded from TSK, then send that metadata to an API endpoint when the mp3 plays, then yes.

2025-03-31 18:02:42 UTC

- reply

But 20 years of precedence without needing backup servers is a pretty solid track record.

2025-03-31 18:02:06 UTC

- reply

I'm not sure either. I was just thinking about the two major reasons nostr bros say nostr is superior to RSS, which is the redundancy (you know, censorship resistance is there big thing), and then the centralization of the Index.
I'm not convinced nostr will replace RSS, as much as the nostr-bros think. They think it will replace everything. I think it's going to remain a realm of a few zealots, but I'm willing to consider their criticism and see what we may improve in RSS.

2025-03-30 22:16:49 UTC

My idea with the signature in the feed isn't so much that we need to figure out how we can integrate with nostr, I'm not convinced we need to. It's more that some of their criticisms about why nostr is better than RSS may have some merit worth considering, and if so, how we can use their ideas for our own purposes.
I'm open to criticism so we can improve things we may not notice because we're insiders and can sometimes be myopic when viewing something we love.

2025-02-27 21:59:49 UTC

- reply

So an image could have multiple purposes, and each purpose is separated by a space?

2025-02-25 22:11:45 UTC

- reply

As a designer and having episodes.fm so you too have to contend with feeds, how would you handle displaying something that is has a purpose of "hero", but one feed has it as a 3/4, another has a 4/3, a third has a 1/1, and a fourth has a 16/9?

2025-02-25 15:36:50 UTC

- reply

I lean towards having only purposes with very defined aspect ratios, and the apps know if the purpose is 'artwork' then they can safely put that in a 1:1 square and not have to also figure out if the aspect ratio of the 'artwork' works with their apps design.

2025-02-24 21:19:19 UTC

- reply

Dang, looking through this proposal, it looks like modifying the image tag has already been discussed, and most of us agreed that modifying podcast:images made the most sense.

2025-02-24 20:46:16 UTC

- reply

As it stands, the tag is pretty useless for anything other than lowering bandwidth. It's a drop in replacement for itunes:image or the image tag (which at least has a height attribute). It's limited to only a single count, and the precedence in podcasting is that image is a square image. It could be expanded to be actually useful for something many people have been asking for for, which is video thumbnails or banner images by changing the count to multiple and adding a ratio.

2025-02-24 20:40:07 UTC

- reply

Both of these images are 400W.
As an app dev, how can I use this info from the feed to create this layout if I don't know the height or ratio of each image?
It's not about maintaining the ratio, it's about know what the ratio is so it can be used for design.
If this is in the feed, I have know idea if it's a banner image or a square image.
<podcast:images srcset="https://example.com/image1.jpg 400w />
<podcast:images srcset="https://example.com/image2.jpg 400w />
https://cdn.masto.host/podcastindexsocial/media_attachments/files/114/060/746/213/201/751/original/a70f01f64ee3c44b.png
https://cdn.masto.host/podcastindexsocial/media_attachments/files/114/060/756/965/623/926/original/c0c61754c2527ee7.png
https://cdn.masto.host/podcastindexsocial/media_attachments/files/114/060/768/561/607/625/original/216d37547dbee392.png

2025-02-22 20:27:30 UTC

@npub1rcn…dw4h I don't think season and episode are being parsed by the Index correctly. Here's some feeds with podcast:episode that are returning the value as null from the Index.
https://podcastindex.org/podcast/4630863
https://podcastindex.org/podcast/6604977

2025-02-21 15:46:19 UTC

- reply

Do you have a link to the announcement so I can understand the context?

2025-02-15 16:06:51 UTC

- reply

I do too, which means I have to make a call to the feedUrl so I can get info the Index isn't currently parsing for, but also make a call to the Index, just to make sure the podcaster might have a value block.
Prior to needing to get info from the feed that wasn't in the Index, I only made one call, to the Index, since it had all of the info I needed.
If I did it to save code and bandwidth, I suspect other apps are doing it as well.

2025-02-15 13:14:02 UTC

- reply

Because of the wallet shim, some apps only use the value blocks from the Podcast Index. Since Fountain relies very heavily on the wallet shim, this may be the case. Concerning wallets, the feed isn't the source of truth, the Index is.

2025-02-07 16:39:35 UTC

- reply

Awesome! That's good news.

2025-02-07 12:26:29 UTC

- reply

Of course someone has.
https://cdn.masto.host/podcastindexsocial/media_attachments/files/113/962/594/084/086/001/original/5eda981e0e1f9e53.png

2025-02-06 18:18:04 UTC

- reply

I don't think it's a bad idea either, but getting wallets on board with it seemed to be problematic. Alby was willing to play along, but I think apps like Strike or CashApp, not so much.
I actually do a .well-known/keysend lookup with the address first to see if it supports keysend, then fall back to .well-known/lnurlp if the first request fails, so I'm not sure the options lookup is strictly necessary since I'm doing the same number of calls this way anyway.

2025-02-06 18:14:11 UTC

- reply

Were you guys able to get a Strike business account? The Strike API integration would be very beneficial for any app wanting to create a simple wallet/app connection.
And what you're saying is mostly the problem I'm talking about. All of the keysend address aren't going to be able to be paid using anything but a Breez, Alby, or Zebedee wallet. Right now, this isn't a big deal, but as more people start wanting to use easier wallets like CashApp or Strike, it will become an issue.

2025-02-06 17:10:59 UTC

It seems like we're putting our collective heads in the sand and ignoring that keysend as the method to send payments is not the direction things are going, and they won't go. The wallet makers have spoken, and unless you want to force your listeners into an in app wallet that supports keysend, or tell them to use AlbyHub, keysend will not be widely supported.

2025-01-28 12:50:28 UTC

- reply

If it’s something you’re passionate about, you’ll have to be the one to build it, demonstrate it, then help others figure out how to implement it into their app, if they even show any interest in it.

2025-01-25 19:09:30 UTC

@npub19gq…wdvy
There’s a discussion on nostr about using Castapod. Any answers I can relay?
https://cdn.masto.host/podcastindexsocial/media_attachments/files/113/890/568/544/870/246/original/4707292859734413.png

2025-01-25 14:37:24 UTC

- reply

So if I was fetching an event by feedGuid and itemGuid, what would the filter look like?

2025-01-25 05:59:25 UTC

- reply

I wonder how that should work if it’s an episode and has the feedGuid and the itemGuid. Should it have two “i” tags?
I find the nostr nip and tag system to be very convoluted and very unintuitive. I’m not convinced this protocol is ever going to amount to much, and had it never caught the attention of Dorsey or the bitcoin bros, would’ve remained in obscurity. I’m still not sure what all the hype is. But hey, it has TikTok strippers now.

2025-01-24 21:06:11 UTC

- reply

For anyone that knows how nostr notes works, here's what I'm putting in the metadata of the note to make splits from the feed work with The Split Box.
https://cdn.masto.host/podcastindexsocial/media_attachments/files/113/885/364/264/885/798/original/8c41a4e54e7b1d45.png

2025-01-24 21:04:57 UTC

PC2.0 is zappable on any of the nostr apps. Splits are being sent based on the feed.
https://iris.to/note1q72l2mpzgnrekhu94ml7nywhpzjd09j84n62x9we826nhqcryzgqp0w24k

2025-01-24 13:51:35 UTC

- reply

Surprisingly, lnaddress is more serverless than keysend, but it's a terrible experience. With the shift to lnaddress, the payment system becomes clunky in client only, and someone running a server could make a better experience by sending an array of addresses and having the clunkiness of the payment system handled server side.
As I'm thinking of solutions to handling the messiness of lnaddress, I keep falling back to a server just handling it behind the scenes.
2/2

2025-01-24 13:49:02 UTC

- reply

Is your adversion to a server component simply that? I ask because I keep you in mind when thinking about how payments could/should work in an app, but it seems like servers are necessary, especially for keysend, and either you're running it or someone else is. For payments, we simply sent an array to Alby, and Alby's servers handled it.
1/2

2025-01-23 02:19:44 UTC

- reply

Take for example this. It's how they're handling splits. Each of those is an identifier for a user, and the server you can find their profile on. So you have to query that server to get the profile, then from the profile get the lnaddress, then from that get the callback, then from that get the invoice, then from that make the payment. Then do it all again for the next split, and the next split, and the next split.
lnaddress is shit.
https://cdn.masto.host/podcastindexsocial/media_attachments/files/113/875/254/666/313/402/original/2a34dbe8408b6941.png

2025-01-23 02:13:35 UTC

The more I play around with nostr, the more I appreciate the elegance of RSS. Things on RSS seem much more efficient and simple, and you're not having to do lookup upon lookup upon lookup across multiple servers to get all the information you need. By and large, everything you need is right there in the feed.

2025-01-21 21:27:12 UTC

- reply

@npub1cwm…wcs6 has relay.fountain.fm, but I'm not sure all of it's capabilities.

2025-01-20 03:30:03 UTC

- reply

Cool! Thanks!

2025-01-20 02:56:46 UTC

@npub1thg…zq23 @npub1fmx…wp74 @npub1rcn…dw4h @npub1g2v…achf @npub1z6g…amwj
Have you guys been getting some payments for PC2.0 Episode 207 with a note talking about testing splittable zaps?

2025-01-19 20:47:02 UTC

- reply

Yes.
sjb@strike.me
gets turned into
https://strike.me/.well-known/lnurlp/sjb
When you do a call to that endpoint, you get this back. That tells you the char limit for the comment. Strike is 200, Alby is 250, some wallets don't have it.
Then you send this to the callback from the well-known.
https://strike.me/api/lnurlp/sjb/?amount=1000&comment=This%20is%20how%20you%20send%20comments
And then you'll get the invoice back and the listener pays that.
https://cdn.masto.host/podcastindexsocial/media_attachments/files/113/856/965/330/731/103/original/b21ae58d0b3b1bcc.png

2025-01-19 17:30:31 UTC

- reply

It is all kludgy. I don’t like it. Keysend is the proper tool for the job. I don’t mind sending sats to lnurlp wallets, but I’m at a point that if you really want metadata, get a better wallet that supports the right solution for the job.

2025-01-17 20:27:31 UTC

@npub1fmx…wp74 @npub1rcn…dw4h
Can you guys look through your Helipad logs for the last few days to see if any boosts came in for Episodes 68, 69, and 70 of PC2.0? I'm testing out splitable zaps from notes posted to nostr that look up the value block from the feed. I used those three episodes as a test case.

2025-01-17 15:28:53 UTC

- reply

Index has some cached data that's not in sync with the feed.
Did you podping it?
https://cdn.masto.host/podcastindexsocial/media_attachments/files/113/844/397/497/004/308/original/280aa6b1e38fe2df.png
https://cdn.masto.host/podcastindexsocial/media_attachments/files/113/844/401/038/653/938/original/29c5721aec3b45f2.png

2025-01-17 14:06:50 UTC

- reply

Oh cool. I'm glad I built that so I didn't have to build it.

2025-01-17 05:26:57 UTC

- reply

Have the last one you want in the list with the oldest pub date, first one has the newest date.

2025-01-09 15:45:12 UTC

- reply

Ok, but if I have a nodes address and ip, then I can initiate the connection, and if they accept, then we can open channels?

2025-01-06 05:06:02 UTC

- reply

Have you seen the Value Block Updater in SF? They idea is you can update an address once, and it will update it across all your feeds, It's still a slow, tedious process.

2025-01-06 03:02:53 UTC

LN Beats is now hosting music playlists. Available in all apps that support musicL.
https://podcastindex.org/podcast/7157117
https://lnbeats.com/album/eeeb0e31-f3da-54f2-909f-4fd640c684cc

2024-12-18 18:24:13 UTC

- reply

Store a copy of things across multiple servers. That's all nostr is doing. I send a message to Damus, Damus stores it. If you're not on Damus, you don't see the message. I have to send it to multiple relays and hope you're also on one of the relays I sent it to.
Nostr would store the rss on multiple relays. http server, only your one server. The redundancy is the thing I find most interesting.
And can we really ignore that relays have DNS?

2024-12-16 14:47:44 UTC

Bad news for Strike oAUTH API integration. It requires an EIN to setup.
https://cdn.masto.host/podcastindexsocial/media_attachments/files/113/663/044/036/607/914/original/a19c51bb3f525d0c.png

2024-12-14 05:27:20 UTC

- reply

What’s cool is that’s because of the work Alby did with their desktop plug in. Every boost from the Index is possible because of Alby.

2024-12-12 19:13:42 UTC

- reply

You would also host this file
https://getalby.com/.well-known/lnurlp/satsandsounds
at
satsandsounds.com/.well-known/lnurlp/satsandsounds/
Now, in your value block, your lnaddress would be satsandsounds@satsandsounds.com
It's not exactly difficult, but it can be confusing.

2024-12-12 19:08:49 UTC

- reply

What's your domain?

2024-12-11 16:56:27 UTC

- reply

No official way. It's being discussed here.
https://github.com/Podcastindex-org/podcast-namespace/discussions/676
I really like Alecks' solution of having a single url the app forward the metadata to. Others disagree. I've said my piece.
Until something official is adopted, if I build something out, I will be building to Alecks' spec as it's my preferred way of solving this problem.

2024-12-07 20:01:17 UTC

- reply

I'll try the Alby Hub with the internal node since it's the easier option and that way I can let people know there's an easy option if they want to run their own wallet.
What are the advantages of running a block chain node vs tapping into a remote block chain?

2024-12-01 00:04:10 UTC

- reply

Yep, I'd actually like something in the spec for the podcaster to be able to decide where the metadata goes, not just limited to a nostr relay. If the podcaster wants to send it to their own url for storing on their own database, and also to be able to rebroadcast it to several services including nostr, they could if they had their own server that received the data. I think this also future proofs metadata because nostr may not always be around.

2024-11-30 17:08:34 UTC

- reply

Not really your fault. I can certainly see how it comes across as targeting you, so I apologize for not being more careful with my thoughts.

2024-11-30 16:58:50 UTC

- reply

I was just getting ready to commend you on your concerns because I had a feeling you might think I was targeting you. I wasn't, so I apologize. I agree with most of your concerns, and a year ago when you were stating them they were even more valid. We're in a situation in which my preferred solution (keysend) isn't being widely supported, and probably won't be, and we have to shift to a solution I don't like, but I don't know a better alternative.

2024-11-30 14:09:20 UTC

@npub1cwm…wcs6 you built. My mantra moving forward is builders over bitchers. You demonstrated a solution. Is it perfect? No, it definitely has down sides. But it works, and it’s relatively easy to implement, and you open sourced it to your own detriment. Fountain could’ve had a huge advantage with being one of the few apps to still allow easy listener payments. I’ll be implementing your solution and thank you for your work. Thank you for being a builder.

2024-11-23 19:02:27 UTC

- reply

I think the idea is I can host the options endpoint on my own server, so I never have to update my feed. I put my options endpoint in the feed as the lnaddress, and if I decide to switch from Fountain hosting my wallet to Alby Cloud hosting my wallet, I only have to update the new address in one spot, which is on my server. Right now, if I change from one wallet provider to another I have to update every single feed my address appears in, including feeds I don't own.

2024-11-23 17:00:46 UTC

- reply

Since I'll be involved in this, I just need to know how we want to handle it.
I'm thinking we something documented in the github that shows what the new valueblock format that supports lnaddress and lnurlp. And maybe an explain it to me like I'm 5 sort of introduction, because I haven't kept up with a lot of this stuff, so don't really know the difference between the two and how to implement them.