Live now, taking song requests in the chat! 🤙⚡
nostr:naddr1qqjxydee8qckvcmy95unxvt9956xgetz94skxcf495ek2cmzv5urqdmrxq6rvq3qeaz6dwsnvwkha5sn5puwwyxjgy26uusundrm684lg3vw4ma5c2jsxpqqqpmxw5z04j5
We pushed a release yesterday that should start to solve a lot of payment reliability problems. We've been working on this problem for months, trying to figure out what the problems were and what fixes it.
We're excited to share our research into that: https://blog.mutinywallet.com/fixing-payment-reliability/
We built our own internal platform for measuring payment success rates through a bunch of trail and error, with many configuration tweaks along the way. We store the results of that so that we may revisit what increased reliability.
If you have an interest in payments on LN or are building on LDK, we'd highly recommend you take a read and learn from many of the problems we've faced and how we've solved them. If we can be of any help to others, please reach out if you're seeing similar issues.
Please let us know if things improve. It's not going to eliminate payment failures by any means, but it should be greatly improved from where we've been at. We'll monitor things as we go and continue to make improvements now that we can quantify reliability.
Nothing concrete but it does feel faster this morning
Just came up with a new plan for fixing replaceable events with nostr:npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj
The biggest issue with replaceable events (contact lists, profiles, lists,) is that there is no versioning scheme. This leads to many issues where your contact list is dropped, comments+likes+zaps appearing only on older versions of a post, etc.
We need a concept of versioned events in nostr and a way of querying those effectively. Looking forward to working with nostr:npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj on this and implementing it in Damus, nostrdb and hopefully strfry once we figure it all out.
Maybe timestamps could indicate versioning. Sounds like we need relays to treat them differently though.
Wouldn't know, I live here now. More than enough cool people to keep me informed and entertained
Godspeed. It's probably the last thing you want to be spending Friday night fixing.
I would zap this but your ln addr doesn't work
Zapping is pretty easy with Nostr Wallet Connect. You zap a bunch of notes in your nostr client and then approve those zaps inside your wallet. But what if it was just a little bit easier?
Today, we're shipping "auto approve" so you can set up Wallet Connections that auto-pay requests within a limit!
To set up a budget, check the "auto approve" checkbox, then pick the amount and the interval. You can also edit existing wallet connections. There is no need to reconnect Mutiny to your nostr client if you've already set it up.
Auto approve is a simple concept, but we wanted to ensure we could pair it with budgeting before unleashing it on the world. Expect a lot more to come in the future around wallet connections and auto payments!
https://blog.mutinywallet.com/auto-approve-zaps-with-the-power-of-budgeting/
It works! 🤙⚡
A nostr dev meetup in OC next week 👀
https://www.meetup.com/nostroc-live-coding-of-notes-and-other-stuff-over-relays-oc/events/296110750/
We're hangin at Steelcraft in OC tonight, come join us
Seems like it's kinda both a feature and a liability, at least with mutinywallet
We're all on a crazy journey here, I'm just glad to know I'm not alone. You did good work today. Thank you.
Thanks for mentioning this, I need to fix my strfry-policies to permit these kinds
Self hosted snort was pretty easy to set up. Although I haven't tried running Primal yet.
SDXL go brrrr
```
nvidia-smi incineroar: Thu Aug 31 14:31:45 2023
Thu Aug 31 14:31:45 2023
+---------------------------------------------------------------------------------------+
| NVIDIA-SMI 535.104.05 Driver Version: 535.104.05 CUDA Version: 12.2 |
|-----------------------------------------+----------------------+----------------------+
| GPU Name Persistence-M | Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. |
| | | MIG M. |
|=========================================+======================+======================|
| 0 NVIDIA GeForce RTX 2080 Ti Off | 00000000:01:00.0 Off | N/A |
| 99% 86C P2 150W / 260W | 10888MiB / 11264MiB | 100% Default |
| | | N/A |
+-----------------------------------------+----------------------+----------------------+
+---------------------------------------------------------------------------------------+
| Processes: |
| GPU GI CI PID Type Process name GPU Memory |
| ID ID Usage |
|=======================================================================================|
| 0 N/A N/A 949 G /usr/lib/Xorg 4MiB |
| 0 N/A N/A 10817 C /opt/ai/kohya_ss/venv/bin/python 10880MiB |
+---------------------------------------------------------------------------------------+
```
