lmao View quoted note →

Or probable future president, ladies and gentleman. A shitcoin shill.

Thinking more about it, this would probably require support from the client too. Like NWC would need to emit a failure event and the client would need to handle it and notify the user to try the zap again? Maybe with a link to the note with the failed zap for the sake of ease of recall? 🤷‍♂️ View quoted note →

Anybody know of some good metal on @Wavlake? #tunestr #metal #wavlake #music

Check this out: If you wear socks at home instead of shoes or going barefoot, you’ll clean your floors just by walking around and chilling. Follow me for more mind blowing tips!

My main beef with @Alby #NWC is what I perceive to be fragility. Every time I connect my node, I end up having to reconnect it a day or two later because I think the connection is broken. But I’m realizing that this might only be partially true. Say I zap someone via NWC. The zap shows up as pending. Sometimes the zap goes through, but sometimes it doesn’t. I only find out about this by refreshing several times. I don’t see a payment from my node, the zap didn’t work… what gives? NWC must be broken. But as I’ve been using good old fashioned manual zaps I’ve realized it might not be a problem with NWC! Sometimes when I go to zap someone, my nostr client is unable to get an invoice. This could point to an issue with the node that I’m trying to zap. The zap via NWC might just be failing silently because of that. I just wish there was a way to get that feedback from NWC. Like, “hey your zap failed because we couldn’t get an invoice, go try that again.” #wishlist

Always gets a chuckle out of me when I see people flying a trump flag next to a nazi flag. You know, the flag of the guys that tried to kill us in recent history. Makes about as much sense as people in the northern US flying confederate flags… which I have also seen. This is dumb.