Will give it a shot. Never tried boosting with my zeus wallet. Is there a way (technically speaking) to make some sort of unified service that resolves as keysend first and if not, attempts lnaddress? Maybe im talking out my ass but the point is, we either move forward with one or the other... or create a solution that unifies the two. Whatever happens we probably shouldn't stay fractured as we are, with creators using one and users using the other.

KFC error... need more chicken

🤘🏽🤘🏽🤘🏽 have a great time and a safe trip!

If you're close enough to swing by Cleveland, I'd love to take you guys out for lunch or dinner! (Though, I don't think Im along you're route)

Ive used serverpartdeals.com in the past. They sometimes have good deals esp on refurbished drives. Haven't had any issues with any of their refurbs.

Sent u a dm!

Surprised it took you this long!

Good tip, thanks!

Sort of... technically, yes anyone can drop an lnaddress in and it will work***. But right now 90-some% of the existing library has keysend node addresses in the feed. So if youre trying to boost a track, but if your wallet doesn't support keysend, chances are it won't go through. Since most commonly used wallets don't support keysend, the friction of finding a new wallet already loses the majority of potential paying users. If you list an lnaddress in your feed, the opposite may be the case. Since most of the library is coded to recieve via keysend, most of the people actually boosting are doing so with keysend wallets. While not guaranteed, a good chance your lnaddress is missing a lot of payments. We use lnaddress and have noticed a lot of missed splits due to failed payments, especially on shows with a lot of splits involved. We're in a situation where you can't put the genie back in the bottle. The existing content creators and a small pool of existing paying users are using keysend while the larger pool of potential paying users and adopters are not keysend compatible. If more wallets (like zeus) supported keysend, it would immediately open them up as a solution to problem that unlocks a pretty significant use-case. And would immediately put them in the forefront as the recommended go-to wallet for 4v4 music. I say all this as a non-dev and admittedly not understanding what it takes to implement keysend. Im viewing it from 21k from up.

yesterday or a few days ago you mentioned something about how the future of all this stuff on nostr and wallets etc. Maybe? Or perhaps its just an excuse to tag the CEO for help pushing this agenda... anyways... I think the most compelling and fastest growing part of nostr "other stuff" is the music scene. Most all existing library is using keysend. And it's a perfect working solution that just works permissionlessly with no fuss. Some wallets say it's too hard to implement for shared wallets as its a node side implementation... but fountain has already built a solution that works. We need more options than just fountain or we will centralize, yet again. I would appreciate a wider push for custodial wallets to support keysend. As someone in the trenches, i can guarantee it will make a significant impact on onboarding artists.

Hey google how dare you say im not a blacktinoeese gay tranny?! That's racist.

Ohh - This is new to me. Thanks!

Can't get enough of 's incredible voice.

Ohhh a nice change of pace! More yard work today, this is the vibe is think