#[0] Some weird badge behavior where I can award two people the same award? and award the same badge twice 
I had to manually deliver the badge. you got it now 📛
It’s my campaign, but you get a Nostr badge if you support the campaign directly https://geyser.fund/project/payjoin
GitHub Copilot has just inserted a cryptic Chinese comment on my code without any reason whatsoever.

this is just a legitimate code comment saying it’s a blocking call 😂😂😂
Awesome Support for the Payjoin project so far 🧡 Payjoin dev kit is coming fast. Thank you supporters! 
Quick and dirty:
Create an image that's 1080x1080 pixels.
Create a smaller version that 256x256.
Upload imges somewhere.
Visit https://badges.page
Sign in.
Tap create.
Enter the badge description.
Provide links to the badge and thumbnail image files from above.
Award badges to Npubs.
Every Payjoin supporter of on https://geyser.fund/project/payjoin is now eligible for the Payjoin Supporter Badge

I want a guide how to make one. People have asked for them and just sent a site that required login
I have found it difficult to source the data to feed into the UI. If you have a blockchair dump or they open up their own plugin that would be dangerous
nostr.band notcpuld make it easier to copy copy npubs easily on mobile
indeed, I have lots to learn thank you master ⚡️
This makes no sense to me in current form. When I show normies nostr the first thing they ask is “how do I find people?” because there are no suggestions and then they don’t return
Verifying my Nostr Nests identity: OwdLaJ6mDoHvZInNXeAO2NAQNcLX_46oI6RCQZzC5i4
if they’re meant to oay someone other than that relay then they should really be MAC’d so you can make sure they pay who you think they do
didn’t realize this was still open. Applied 🤠
CISA is popular
Looks like LUD 12 allows a comment where one could put a MAC associated with an invoice & nsec-derived key. nostr client could verify with the mac that the invoice came from a particular npub
couldn’t that be prevented with a MAC from the destination on the invoice?
I was imagining the authentication to part prevents a zaptunnel relay from stealing, not for privacy
wow yet another spot where an authenticated async relay protocol would fix the problem
