#[0] do you use lnurl-commando with your CLN? and if yes, is it remote from the node or local?

#[0] does your relay not support compression on the transport layer? can’t see anything in tcpdump

and then the people try their zaps on a guy named jack

with lightning it changed from simple off by one to off by 1000 :)

“We train young men to drop fire on people. But their commanders won’t allow them to write 'fuck' on their airplanes because it’s obscene!“ https://iwdrm.tumblr.com/post/3032397163

#[0] stats

stats

#[0] info

implemented now signature verify for the clnurl invoice dispatcher. damn you people who try to pay me with fake data :)

can someone take a look here, it’s really not my field of expertise https://github.com/jb55/nostr-js/compare/master...denis2342:nostr-js:patch-1

“Do you mind if I have a quick one?” https://iwdrm.tumblr.com/post/4369172203

it’s called the sat size war :)

#[0] why is damus requesting the lnurl callback 16 times after startup even if it got the correct answer for he first time? https://void.cat/7JcuyhDxG7d56GAyBFjGFq

clients should never ever cache the answer for the callback request

did you maybe cache the first request with the callback, because I don’t see you calling the callback (changed it yesterday)

just zapped me and it worked.

easy, just write good notes

Viva Zapata!

nip-57 describes the node sending the zap note as the zapper. but I always thought that the one who is sending the sats is the zapper. the mainstream will decide and so think they already did :)

hacked together my first nodejs tool called clnurl. it’s a big steal from lnurl-commando and cln-nostr-zapper. feels good that the zaps go through code I understand.

anyway, with this tool you can serve lnurls directly from you cln node for your zaps