Connected from Mutiny to nostr client, but it looks like I have to go back to Mutiny to approve zaps, and the requests timed out.🤷🏼♂️
New Mutiny Release v0.4.14 🚀
We've made some improvements to load times and fixed an issue causing missing lightning gossip data that could have caused a lot of "no routes found" errors.
We also have the android app caught up to feature parity with the web wallet. Log downloads, state downloads & uploads, plus back button navigation.
Our android app is here, but now that it has caught up to development, we'll get it up on fdroid sometime soon. https://github.com/MutinyWallet/mutiny-web/releases/tag/v0.4.14-1
Lastly, we're going to continue working on path finding improvements to make the wallet more reliable. We've worked behind the scenes on our prober to handle multi path payments better, and analyzing the results to provide to our Voltage LSP.
We'll also be working on a custom path finding algorithm to prioritize hubs, in addition to integrating additional LSPs like Zeus/Olympus and C=, which those teams have already started helping with.
Let us know if payments are any better at all, but we expect some popular destinations to still be problematic. We're sorry about this but we are actively working on it. A lot of what we are doing is still very experimental.
Discussion
Yes, you do have to go back to your wallet to approve zaps. Auto approval is coming soon but it is still going to require you going back to the app.
Now zaps aren't showing up in wallet to approve... i hit zap in Amethyst, select the amount, get a curly status circle, then nothing.
Go to Mutiny and there's no zap to approve, and in Amethyst no zap has been recorded🤷🏼♂️
Amethyst has a problem with persisting NWC strings for whatever reason. Sometimes they don't swap out at all, sometimes it reverts, it's very unpredictable and annoying. Double check that the NWC strings match in both amethyst and mutiny.