Stirling Forge

Feels like a nicely wrapped pretext for the internet getting 9/11'd.

The Israeli bots are out in force. No one wants this war in reality. No one wants to die for Jeffrey Epstein's employer. When they start going around with the draft vans pulling people in, that is the answer to the age old question: "When do we get to use the guns?"

PIC Related: what would happen to Bitcoin if Core laid off Peter Todd and returned the 82b relay limit. p📝 4b19868e…

I think the "temporary" nature of #BIP110 is actually it's what leads to the reasoning of @ODELL that it has potential for being used to "threaten a reorg" later. The rejoining of the chains later does actually just seems like more risk than reward and threatens history of the main chain in the case of the BIP failing. I'm running #BIP110 right now because it's directionally correct and majority support of the BIP would be better than it failing completely. But if someone makes a BIP-110 version that is not "temporary" I will run this, as I view it much safer for bitcoin, because it can either succeed or fail gracefully.

The best 📝 a0600bbb…

Easy to tell who is picking sides based solely off of who their friends are when it come to the "Mempool Policy and subsequent BIP debate". VS who is picking sides based of what has actually happened

If you are anti BIP -110, the best thing you can do is HOLD CORE ACCOUNTABLE BY HAVING THEM REVERT THE RELAY POLICY TO 82 BYTES. If the inscription bug was the gasoline, that action and the unwillingness to waver on it was the match that lit the fire. The fact that the pro-core side doesn't even consider this an option is why so many people are abandoning it as the reference implementation and running a fork. Do people not realize there is easy reversal of course that would show good faith? Honestly the pro core influencers are all acting like this is a rogue element of a few bad actors. No there are a LOT of people who are fed up with Core for directly supporting spam with the change of mempool policy. Core is dying in the bed they made. Even if the fork fails, they will be dead in that bed unless they change course and listen to users with valid concerns.

Got openclaw to a usable state where I can drive Uber and Lyft all day and it has Claude and Codex create and refine plans for bug fixes and feature emhancements. Sends updates to me that I can review between every ride. I no longer need to be home to continue 24/7 Ridestr development. We are cooking

Trying openclaw is almost making me a Claude code maxi. Openclaw is wild; has to be severly tamed. Claude code just kinda gets shit right. Going to work on finding the balance of the two.

I've normiefied the onboarding flow and UI for Ridestr and Drivestr now. Nothing says nostr/create keys/etc anymore in the frontend. Much more user friendly for people who aren't total decentralization nerds. If you want to test it, check out version 0.2.5! All feedback welcome! 📝 ab07015b…

So they're gonna use the Epstein files to push internet identity, rather than arrest the pedophiles. "Protect the kids" by enslaving them.

Okay real talk how fast can we fix this if it's deployed and get a second internet going?

This will be big 🙏 📝 4fd1f739…

Wow we are so lucky that every facet of our government cares about our lost dogs!

Because of the bitcoin price, I've gone back to doing Uber and Lyft fulltime, and will probably only spend an hour to two a day on RoadFlare dev work. Compared to the 12-16 hour days I was putting in the last month to get it out there, this will feel like a snails pace. I've also removed the video sharing the winning vision of Roadflare with Nostr, for OPSEC reasons. I appreciate all the support and love of yall. I just have to build my bitcoin runway up a bit more before I can fully execute the vision. This will probably delay an IOS version until the bull market ramps back up. 🙏 I may set up an openclaw agent that I can call in between rides and manage the project remotely for, but I feel like that in itself might be a month long project I don't have time for, so for now a 1-2 manual and focuses dev time will work for me

Roadflare is out, now built into Ridestr and Drivestr version 0.2.0! So many bug fixes this last week before I felt like it was in a safe place to push out. If you use it, let me know how it works out for you, and any issues you have. Download now from zapstore.dev (android only, for now) Github Repo here: https://github.com/variablefate/ridestr

Yeah if the bitcoin price could return to 100k for at least the period I'm not working to code Ridestr, that'd be GREATT

Can we make a modified NIP-09 delete request to allow deleting NIP-44 dm events that were sent TO you? More of a relay feature than anything, but if the info is public anyways it'd be nice to be able to clear out your inbox every once in a while.

What's the over under on them blaming the state sanctioned Cyber attacks on openclaw/moltbot

New workflow has been plan with Claude, review plan with codex, review plan with Claude, review plan with codex again, implement with Claude, and then have codex scan codebase for bugs. Maybe it's all just hallucination and I'm wasting time, but it feels very refined. The worlds' two best engineers battling it out for the best code snippets to put in