I think nostr:nprofile1qqsxx7uu034dee4aj8djcm4qcnymyfsvrvns333vfj2c8lq0g6fdxlgpr3mhxue69uhkummnw3ez6vp39eukz6mfdphkumn99e3k7mgpr3mhxue69uhkummnw3ez6vpj9eukz6mfdphkumn99e3k7mgpremhxue69uhkummnw3ez6vpj9ejx7unpveskxar0wfujummjvugy9k5a is hurting the lottery and discouraging players from participating by flooding the contest with 500+ sat entries. It's his prerogative how he wants too play, but what's the point if he's discouraging participation?
Looks amazing! I think the only thing I may have different is the double-starch. I may have subbed out the rice for some steamed Bartlett peas, or fresh steamed broccoli. Probably the peas because they're so sweet and delicious! But I'm salivating over the beef. 🤤
I love my crock pot. I've a nice, 8qt Rival cooker that I use to make meat sauce, beef stew, and other warm, winter soups. Just turn it on and forget it!
You're on a roll with all this beef! Just make sure you're eating enough fiber, or there could be trouble later on.
It's a giant rabbit that seeks vengeance for the mistreatment of rabbits. Have you ever seen how ripped those things are?? They can do some serious damage. And they're vindictive, too! 
I don't know if this matters, but my relay info via Amethyst is still showing v0.9.6
Thanks for the heads up! You rock!
I don't have Damus so I'm not sure about that one, but I've scoured Primal and am unable to find any setting, toggle, option, or process to switch from NIP-04 to NIP-17 (NIP-44). It's a problem because me along with others, use NIP-17 by default but if I send to a user whose client doesn't support gift-wrapped messages, I'm never alerted and they just don't receive the message. It's frustrating and disappointing that this essential feature has apparently been put on the back-burner. I'm irritated. Can you tell? 😂
Oh that was quick. It's nice when an upgrade is smooth sailing!
Thanks! Good luck with upgrade!
It's cool. Mine is rocky, but I certainly understand these things take time, and you can't plan for all eventualities. Looking forward to the new version!
What's "a while"? Hours, days?
That or use NWC unless user sets lnurl in profile. Then use lnurl.
I agree it adds an extra complication. Would there be a way to use the NWC as the default for both sending and receiving via the lud16, but allow users to override that by using an LN url in their profile if they want to have a split configuration? At least that way it would be straightforward flow and wouldn't create these conflicts based on how a client decides to handle it?
Or get rid of the LN address in the profile and use the NWC to universally integrate sending and receiving into the client. Using both only seems to cause problems and conflicts.
Yes, that's what led us to this problem. My friend was having trouble with Cashu not working properly in Damus, so I had him set his LN address as his Cashu Wallet, and his NWC from Coinos so he could receive to one and send from the other. But we couldn't figure out why he was both sending and receiving through Coinos since his LN address was from Cashu. Will brought the lud16 in the connect string to my attention and I discovered that in fact the Coinos NWC string inciuded the lud16 so it was overriding the LN address he had set in his profile. Given that NWC is used for sending, I don't really understand why it's a part of the NWC string at all. Because this seems to he a totally unnecessary problem. People should just set their LN address in their profile for receiving, and use the NWC string to integrate sending into the client.
In Amethyst, the &lud16= is ignored and the address set in the profile is what's used for zaps. I thought that's how all the clients worked but I'm now learning this is not so.
Why not just use the LN address a user has set in their profile, instead of parsing from the connect string? Since NWC is just used for zap sends, isn't the lud16 in the connect string mire trouble than it's worth as it caused problems like this?
This is the connect string copied from Coinos just now (with the secret cloaked 😉)
nostr+walletconnect://ba80990666ef0b6f4ba5059347beb13242921e54669e680064ca755256a1e3a6?relay=wss%3A%2F%2Frelay.coinos.io&secret=