Fresh TWiB! And maybe the last one for a couple of weeks. I think an important one too, especially if you’ve been wondering why bitcoin didn’t pump after the rate cut. And I cover that new PR to core that walks back some configuration deprecation. Don’t miss this one! https://fountain.fm/episode/dEVrFEYiwHe7CjjkJ2zM

Check out this cool guy I came across on the farm today.

GM! Eating breakfast with some guests.

Fresh TWiB: Why I think a rate cut was a lock and it’s not because of the jobs revision. That’s a smoke screen. Also, why this cut Isn’t a ripper for the price, yet. https://fountain.fm/episode/H5lo1HQmAk34SY3FDwe7

Even if Alby had kept easy hosted wallets around, no major lightning wallet supports keysend. And when you consider what’s easiest for podcasts to give out on air Lnadress offers a familiar email address format. To be clear, I think it’s a real shame Keysend has not seen more love. and… it’s a shame lnadress is not Bolt12 ready which also solves some of this. But there is a hard reality we are up against. We are down to just Fountain and Alby compatible apps that can boost. Ironically fountain could just sit back and do nothing and they pretty much consolidate and lock up the entire boost market because they probably already have about 80% of it. They’re pretty much the last easy lightning wallet for boosting in town. And for the listener, it’s a lot less of an ask if they can use any lightning app that supports LNaddress to support the show. They could use strike or other apps directly even.

I think some key context when reading this is: 1. There is already a active Podcasting 2.0 Boost community, that existed before Nostr and Zap. This is not something being invented today. This is about modernizing something that has been around since the early days of Lightning. 2. Keysend has not been widely adopted outside of Podcasting 2.0 (it's NOT a P2.0 tech, it's a lightning thing) and if we want to grow the base of users who can Boost/Zap a podcast, we have to move beyond Keysend. 3. lnaddress, and the email format for payments is an obvious UX improvement over node addresses, and opens podcast Boosts up to the entire Lightning ecosystem.

Just to be clear, Oscar's spec here still uses the Podcasting 2.0 valueblock in the RSS feed. The big change, is instead of the metadata coming via Keysend (at the lightning level) it would be delivered via Nostr, as the lnaddress spec does not support including all the metadata needed for a boost/Zap.

Actually, this is the problem. You can do it, but there’s several huge disadvantages right now and I don’t think most people realize it. Important Metadata podcasters need to credit supports is missing, just not even captured. And importantly to me if you’re self hosting a node, it gets even worse and anyone in the split doesn’t get any metadata. When you receive the boost, you have no idea the total amount, and the most situations you won’t even know who sent it. It depends on all of the systems between. It currently only works in very limited situations. I’ve been testing this the hard way with some of my shows, and it was a mini disaster. Even though I’m a big proponent of using lnadress I had to roll back to using my node address/keysend for now because of all of the shortcomings with the current implementation. Being able to properly credit people who support the show is a vital and important part of the value for value cycle - that is fundamentally broken right now with the current lnadress implementation. If the current implementation sees wider adoption, it will destroy boost for podcast. I don’t say that lightly, you probably know how critical this is for my shows. I think some key insights that I have here that maybe others are missing is that I run multiple shows at scale that are funded by boost. Multiple episodes of my shows are often in the fountain top charts each week. I’m not bragging. I’m just pointing out, it’s significant us. We self-host our entire infrastructure. And we build tooling around boost, so that way we can properly credit those who supports us. And I’m a big supporter of other v4v podcast and as a listener, I boost a lot . So I really been looking at this for all angles since about December. If I could go on the podcasting 2.0 show every week and yell that we have a problem here I would! I think a lot of people are missing this because they’re not quite as deep into the technicals . Technically lnadress is supported. But it’s a disaster in its current implementation and limitations. It also reinforces centralization because just look at the practical implementation so far. Fountain is the easiest and most complete implementation. Even using Alby Hub the experience is sub-par. You will get the stats. And your SOL if you just want to run your own node and lnadress.

Some of the biggest economic stories of our lives dropped this week, I humbly try to break it all down in this weeks TWiB. This is one you won’t want to miss! 🍻 https://fountain.fm/episode/IwvVdS7vgLUWLRVBxT9Y

If you want a wild read to get more background on today’s episode this 17 page essay by the Treasury Secretary is screaming the quiet part out loud. I can’t believe a sitting Treasury Secretary wrote this. https://www.international-economy.com/TIE_Sp25_Bessent.pdf

GM. Working on today’s TWiB, assuming I can find the 🎙️in all the fog.

New episode 🍻 Mostly my take on the state of the Core vs Knots debate, and why it’s getting so heated right now. https://fountain.fm/episode/vNS3UnEX1NMhmngvCl9m

When you imagine living on a farm, you probably picture chickens , milking cows, goats eating things… But I’m learning the reality is more like dealing with waste, fighting pond Duckweed, and finding weirdos on the property with the drone …

Boosting this for Nostr visibility. Especially relevant for Bitcoiners and GrapheneOS users. https://fountain.fm/episode/O1CkPZO6eJ61q2Xu0jaJ