This might be a bit more technical: https://fountain.fm/episode/209pa9hUnimYGWMS9okb
Yes and yes.
Nope, the node runs in the web page / app.
Even though we have just started releasing on iOS, a great reminder that even if something were to happen with the app on the app stores, our application is still available as a web app @ https://app.mutinywallet.com and self hostable as well.
nostr:npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg's distribution method looking pretttttttty good right now.
We just announced our TestFlight version yesterday 😭
But PWA version still going strong 👌
Happy Thanksgiving!
Until Monday, we're giving a 50% discount to all Mutiny+ subscriptions this month and we made our Gifting feature free until then. A great time to orange pill at the dinner table.
Read more about it here: https://blog.mutinywallet.com/mutiny-gifts/
Hopefully you onboarded your family to a wallet that is still available.
Can nostr:npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg be self hosted?
If so, is there a .deb package that makes it easy to install, configure and update?
My concern with web-based projects is that if the centralized ptovider goes away, users would be in a rough place. Even if the code is open source, it doesn't mean all the configuration files, .service files, nginx settings, are available
Heck, I've seen open source projects that wouldn't compile unless you had this one directory in a hard-coded path, which contained some library that nobody csn seem to track down.
I see they have a dev setup in their readme, so that's encouraging, but I've yet to see anyone else hosting a production site.
Yes, there are people that self host theirs, and we make it easy: https://blog.mutinywallet.com/self-hosting-mutiny/
We also use nix for most of our code repositories, making it highly self compilable.
Happy Thanksgiving!
Until Monday, we're giving a 50% discount to all Mutiny+ subscriptions this month and we made our Gifting feature free until then. A great time to orange pill at the dinner table.
Read more about it here: https://blog.mutinywallet.com/mutiny-gifts/
If you end up orange pilling a family member over Thanksgiving, don't forget about nostr:npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg and their gifting feature. You can gift a family member their first sats and set them up with a non-custodial Lightning wallet all in one swift action.
A little birdie named nostr:npub1u8lnhlw5usp3t9vmpz60ejpyt649z33hu82wc2hpv6m5xdqmuxhs46turz told me he slipped in some code that gives the gifting feature for free over Thanksgiving 👀👀
It's the same code base. But with minor flags for iOS vs PWA.
And you still have the freedom of choice.
Something something PWA something something...
We have started rolling out our iOS Testflight version of Mutiny Wallet to our Mutiny+ subscribers. If you're on the PWA version, you should see a link at the top of the home page.
We've written a guide on transferring the data from one device to another.
https://blog.mutinywallet.com/migrate-mutiny-wallet-to-the-native-apps/
nostr:npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg what do I do when the app force closes my channel?
- opened pwa
- some js error with big Reload button
- clicked reload button
- “Channel closed because user manually force-closed the channel”
4/5 experience so far, first hiccup. big fan! 💜
Logs would help. But this one is typically due to a pending payment that did not complete before the time lock.
The test fight version is being privately tested. Should be public soon.
as much as I respect nostr:npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg stance on nostr:npub1xnf02f60r9v0e5kty33a404dm79zr7z2eepyrk5gsq3m7pwvsz2sazlpr5 hodl invoices, zapping via a non-custodial mobile wallet is a pain in the ass as well. even if you use NWC you have to go into the app and wait for each zap, or hack it with a split screen like this 😂
I see it counter productive to aim for each payment to be perfectly self sovereign forever. it's OK if your zaps could be batched by your service provider and settled every few days, preferably with as little hops as possible. let the providers handle most of the plumbing risks
You're not wrong, though the batch approach still works decent here. Zaps don't need to go out right away and you can just open the wallet once a day to send them all out.
Though agree with it. Eventually we'll be able to push a notification for these and possible pay them in the phone's background.