There's still time to send says for tomorrow's No Agenda

http://l.curry.com/fEh

Reply to this note

Please Login to reply.

Discussion

I just spent 30 mins trying to figure out why my http://v4v.app doesn't work with this LNURLp and I found it.

The LNURL spec DOESN'T specify response codes, IBEX returns 201 (created) which is fine but my code was looking specifically for 200 (which pretty much everyone else uses). Fault is in my code.

I’m just going through now and changing a whole lot of checks for == 200 to >=200 and < 300. I know you love hearing about this stuff… as usual, you broke something 🤣😆🤣😆

But the LNURL spec is also poorly written too. 🏃‍♂️✂️

#[2]

I can see arguments here for 200 or 201 both. It’s a grey area. I agree it should probably be in the docs.

Unfortunately they're giving 201 on the first call which just gives you parameters and the address to fetch the invoice from I guess that creates a unique internal code.

That second call could legitimately be 201 as it creates a unique invoice. But 201 on the first information only call is a bit weak.

In the absence of a tight spec you get this kind of interop problem.