Avatar
b0b
6042d70377f8ae95c160a64cbe0f632578f0b53b2c76095449e7053be3e62213
Co-host keypair.fm 🎙️

Interesting discussion on yolo mode. Why not yolo vibe code and then control what goes into production with good ol' git?

Writing up my first experiences with Vibe coding and I revisited the agilemanifesto. I feel like some of the good ol' developer habits make even more sense when using AI assistants. Like git for taking snapshots of your codebase and automated tests to quickly check it still works.

npub1g0eujuzgy06srs3sdanaytzq8adsd78d4g4p5xqtlue3d3q3v2mq6pl966 Just read your tam piece with great interest. Curious about the thesis of investing in infrastructure because of bitcoin TAM. Is the infrastructure not likely to get commoditized? Looking at the internet infrastructure boom cited in the article: Many early internet infrastructure companies (routers, servers, fiber optics) faced brutal competition despite the internet's massive growth.

nostr:nprofile1qqsqkaay6mxplgv3f9z0ep0rq4w8jrte3rvcm43xd2cgehsjevglmdcppemhxue69uhkummn9ekx7mp0h87030

love the idea!

does it have to be local or how would international shipping work?

Replying to Avatar Soak Quest

Bitcoiners are the new capital allocators.

We’re living in a brand new world—nothing will ever be the same again. What made sense before was just habit: the consistent, daily reinforcement that Keynesian dollars could get you things. More fiat meant more stuff.

But those assumptions were built on sand.

Now, with perfect money, capital allocation among Bitcoiners follows a different logic. It’s grounded in real economics—Austrian economics—with a focus on hurdle rates, opportunity cost, and long-term value.

Just like Bitcoiners found each other by following reason to its conclusion, their investment choices often arrive at similar endpoints. But there’s a twist: perfect money creates a paradox. When your money appreciates exponentially for doing nothing, it becomes harder to justify spending or investing it at all.

That’s the challenge: if Bitcoiners don’t actively defend the medium of exchange property, they risk losing the very status that made them the capital allocators in the first place.

Before Bitcoin can become the default medium of exchange, it has to reach critical mass. But its strength—unparalleled appreciation—makes spending it feel irrational in the short term. The opportunity cost is too high. That disincentivizes everyday usage, which stalls progress toward mass adoption.

Bitcoiners face a choice: delay spending and preserve gains—or spend with purpose to build the future. That’s why Bitcoin capital allocation has to expand beyond ROI. The hurdle rates vary: some investments are about returns, others about aesthetics, ecosystem growth, or purpose.

Using Bitcoin as a medium of exchange doesn’t make short-term ROI sense. But it’s a long-term, purpose-driven decision. The real return? Staying in control of capital allocation. Cementing Bitcoin’s role as not just a store of value, but a currency in motion. Until that happens, fiat still wins by default—easy to earn, easy to spend.

So let’s show the world what Bitcoiners can do. Back the people, brands, and companies willing to build on Bitcoin. Prove that Bitcoiners don’t just spend—they allocate with conviction. We can mint new brands overnight simply by choosing where we spend.

That’s how we stay the capital allocators.

And right now, there is no higher ROI than securing Bitcoin’s place as the medium of exchange through a thriving circular economy.

This MCP thing is really blowing up.

Just discovered this "anti new car ad", which also serves as a great vehicle (no pun intended) for financial and life wisdom.

https://youtu.be/V5tYK1mruHg?si=dnIHhVKt7AgjIVI5

Replying to Avatar Rizful.com

nostr:npub1marcan0laywmjprf4m8d34dr8m724a6jxxa56a5wwygcgj23q7nskfwmfg and nostr:npub1vppdwqmhlzhftstq5exturmry4u0pdfm93mqj4zfuuznhclxygfsdatk8w You discussed in your "rails" episode the basic challenge of using rails with Nostr -- rails is just not really made "out of the box" for highly async use cases like Nostr. I have recently had two biggish projects where I has to integrate Rails with nostr -- https://rizful.com/docs/connecting-apps#nostr-wallet-connect-send-and-receive and https://docs.megalithic.me/lightning-services/nsfw-image-detection-for-nostr .... both required a lot of SERVER SIDE communication between Rails and Nostr relays.

I used quite a lot of this https://github.com/wilsonsilva/nostr -- but you'll notice there are a few serious issues -- for one thing, there's no explicit way to actually close a connection with a relay! ( https://github.com/wilsonsilva/nostr/issues/19 ) ....

So after trying a couple different architectures I have currently hit on these rules for server-side development with rails and nostr.

1) Never try to communicate with Nostr relays directly from rails

2) Instead, use a purpose-build "intermediary" application written in Node.js/Typescript... this could be built many different ways but in my case, I have this Node.js application listening to a queue, where it consumes requests from rails....

3) This intermediary application allows your rails application (using multiple threads with something like Puma or many concurrent background jobs) to be "conservative" in its usage of Websocket connections.... you can design this intermediary application so it "re-uses" existing connection to relays, to avoid overwhelming relays, and also, in some cases, to keep connections alive so you can have very low latency with relays -- i.e. not need to constantly connect and disconnect from them.

4) This is just what I have come up with, but I've noticed better latency and better reliability after switching to this strategy.

So Rails can still construct the events, and handle the business logic (Because, as you point out, NOTHING beats Rails + Ruby + Active Record for business logic!), but then it always hands off communication with relays to the intermediary app. (Also, rails will have to listen on a queue to read from the intermediary app, I am using Redis in some cases, RabbitMQ in other cases, and SQS in still other cases, I have found each of these has certain strengths and weaknesses....)

Appreciate you laying out the architecture. I want to build a bookmarking app and couldn't decide whether to just use JS or hook into a Rails backend. Using Rails as an intermediate step is interesting. What tasks does Rails handle in that kind of set up?

I dream of having an ActiveRecord adapter that writes to Nostr like a SQL database and handles all the complexities of Websocket management for me #lazynostr

Replying to Avatar Rizful.com

nostr:npub1vppdwqmhlzhftstq5exturmry4u0pdfm93mqj4zfuuznhclxygfsdatk8w and nostr:npub1marcan0laywmjprf4m8d34dr8m724a6jxxa56a5wwygcgj23q7nskfwmfg thanks for your great podcast which I recommend highly - https://www.keypair.fm/ -- I listened to most of the back episodes today while snowshoeing in the San Gabriels

Thank you for tuning in!