If you still use Telegram you're either clinically retarded or a malicious actor. It's always been an FSB honeypot but now there's some actual evidence: https://istories.media/en/stories/2025/06/10/telegram-fsb/

I added nostr zaps to go-host-lnaddr, everyone's welcome to review and comment:

GitHub

Add nostr zap support by rkfg · Pull Request #27 · hieblmi/go-host-lnaddr

Closes #17. Testing this is harder than I expected because lnd doesn't allow settling an invoice made by itself, Primal asks to connect a walle...

I couldn't find any other such solutions except the reference implementation which is in JS. go-host-lnaddr allows hosting your own Lightning address/LNURL pay/Nostr name, and now it also lets you receive zaps to your own LND node. I haven't tested it much, just followed the spec and used the mainstream libraries. It's effectively a small addition to the existing functionality that parses zap request and posts zap receipt + puts the request to the invoice description. Still, there could be quirks I missed. I currently run this patch myself.

The biggest problem in nostr is... following people apparently. I've seen too many clients where this basic feature is either missing or unavailable because of adblock hiding it for some reason or it's buried so deep I can't find it. On primal it's the former I think: Non-working zap button, a menu... Add user feed? Is that following? Nope, it's something else completely. Ah, there it is: Very convenient, just open any post and you can find the follow button if you're lucky. No wonder engagement is so bad on nostr if you can't even follow people in one click.

Great DoS potential! Since pushing an event doesn't mean you're able to sign, just pick whatever events of other people and push them to this relay, get a bunch of such messages that *those* people receive, not you, lmao!