#m=image%2Fjpeg&dim=640x480&blurhash=%23DFYS%2C0e4m%25gXARQaKsl%25M9t%25MNLskoet7NGWAfi%24wxvI%5BROt7W%3ARikCWB%7EqIU9Fx%5D%25LRjV%40Rit8%25LM%7CNG%251s%3AogWCM%7BofRka%7EjYxZozoeRjWroJxuWBNGbFt6t7WBRjWX&x=0b54724700aef2cd24000709e4bea899eedbf20e8466d9f35471921bc8b46a6a
I have a friend who also completed the assignment last night after struggling mightily with a silly bug. You got this dawg!
Beware of IDEs promising to faithfully display the state of the file system. π
We've released Mutiny version v0.5.7 which includes two notable changes.
Payjoin v1 support has been added. Huge credit to nostr:npub1yevrvtp3xl42sq06usztudhleq8pdfsugw5frgaqg6lvfdewfx9q6zqrkl over the last few months, for the improvements to the PDK library and getting it included into Mutiny! Thanks to Ben Allen too for testing.
We're really excited about the privacy gains here and for future improvements such as Payjoin v2. This should allow asynchronous payjoins, making it possible for a mobile user to payjoin with another mobile user.
We've also made some underlying changes to how NWC works in Mutiny. We've switched over all new connections to use our new strfry based relay instead of using the Blastr. This should greatly improve performance and speed, in addition to being able to better support consumer apps.
You may continue using your existing NWC connections, but for better reliability, you can delete existing wallet connections to recreate them on the new relay.
In the coming months, we should have a load of new nostr related features as well. Stay tuned!
Payjoin is our best hope for on chain privacy. I'm so happy y'all are building this functionality. π§‘
Dunno why but today feels like a Rage Against the Machine day.
πππππππ
Swan is mining.
Lightning is not bad. It's, frankly, amazing technology. It's just ill-suited to small scale nodes. It was fine when fees were low b/c the problems were hidden. But now fees are permanently high so the devs that were pushing the state of the art of lightning self-custody are coming to terms with this reality.
The most private solution for fast settlement is looking like large LN nodes that offer privacy preserving custodial IOUs. When your stack of IOUs gets big enough, withdraw to cold storage. This is the 99% solution. It's WoS with good privacy. You might get rugged for your tipping wallet. Big deal; it's better than maintaining a lightning node and dealing with liquidity, force closes, mempool fee storms, server uptime, etc.
We need to soft fork again to bring on the next cohort of self-custodial bitcoin users. This is the real battle. It's playing out on github, the mailing list, delving, and other bitcoin developer forums, and even on twitter. But, as usual, the quality of discourse on twitter is low. WYGD? Β―\_(γ)_/Β―
I deleted my linkedin but recruiters still harass me. :(
It's only self custodial if you can also collude with the mint to rug whoever holds a particular ecash token after you traded it in. If not, it's just sparkling custody.
When your team has to hold you back from overengineering the solution to a nasty bug.
I think we can 10x it at least. But you're right it doesn't scale enough.
Sounds like you are conflating correlation with causation.
nostr:npub1emdtsxly9m68m00x206t574jttp65vk0c2m89ms038q047yz7ylqcac9aw
I love that nostr clients (at least Amethyst) plays audio on a loop. π
Exactly what I want to hear on a loop when I'm scrolling the feed on the can.
For the love of humanity we need to get these people baked!
omg rekt, why no lightning address nostr:npub1ryfdh0pyjyp4kx3hdv9v73algvw4pr49unkw5ez0lfunzxzflfws79rg5z?
omg you are the charlatan. Senpai noticed me!
I was being facetious. =P On behalf of all bitcoiners thank you for the work you do. π§‘
omg rekt, why no lightning address nostr:npub1ryfdh0pyjyp4kx3hdv9v73algvw4pr49unkw5ez0lfunzxzflfws79rg5z?
Someone should package all these consensus rules into a library. π€