Avatar
Dave Jones
0b1aef6f7eb29eb2b6654279f3ce86e768461c7b434aee7ce70028d348eff84c
Running systems at podcastindex.org

Ah, I guess I lost it through testing on this beta software. Added back. 🙏

But, this post *should* go to Nostr.

#testing #podcasting20 #9S9ezTJek5heK

I just joined the live stream chat at: https://chat.podcastindex.org/?cid=9S9ezTJek5heK

#testing #podcasting20 #9S9ezTJek5heK #podcasting20 #9S9ezTJek5heK

I just joined the live stream chat at: https://chat.podcastindex.org/?cid=d778e25f92c084e65ab18f0470f498a802745c0df7 #podcasting20 #d778e25f92c084e65ab18f0470f498a802745c0df7

This should be producing a hash tag of the chat room ID. #d778e25f92c084e65ab18f0470f498a802745c0df7 #mkutesting

Checking from mobile. A little more styling needed on the login modal when the page is this small. It’s not pleasant. #mkutesting

Thanks to #[0]​ for all the helpful Nostr discussion tonight at the Birmingham Bitcoin meetup. Helped me iron out some thoughts. 🙏

It will be soon. Trying to figure out the best way to pull back in. I’m thinking probably a per episode hash tag that can be used. And then obviously replies. It’s all out-in at the per user level for sure.

Hello world. #mkutesting

Nostr keypairs are the best part of Nostr. Lots of opportunity for interop across other protocols.

#mkutesting

I just spent 30 mins trying to figure out why my http://v4v.app doesn't work with this LNURLp and I found it.

The LNURL spec DOESN'T specify response codes, IBEX returns 201 (created) which is fine but my code was looking specifically for 200 (which pretty much everyone else uses). Fault is in my code.

I’m just going through now and changing a whole lot of checks for == 200 to >=200 and < 300. I know you love hearing about this stuff… as usual, you broke something 🤣😆🤣😆

But the LNURL spec is also poorly written too. 🏃‍♂️✂️

#[2]

I can see arguments here for 200 or 201 both. It’s a grey area. I agree it should probably be in the docs.

I think the way it’ll have to be done is to have a core list that seem to be the most popular (this is unfortunate but predictable) and then read kind 10002 and append those to the current list before using.

The relays a user is connected to don’t seem to show up in their metadata (kind 0). Is there another way to get this info or is it not propagated?

There’s no way that’s accurate. Podcasting 2.0 has had boosts and per minute streaming sats for 2 years and the ecosystem total isn’t even in the same universe as that.

Time for the board meeting! We're running with scissors live with episode 126! And I wonder...!🎙🏃‍♂️✂️💥🎉🍻

podverse.fm/podcast/peLVTH…

curiocaster.com/podcast/pi9206…