k00b lol this repo is 4 years old. I think I actually played with it a little when I was trying to implement lnurl-auth (I stopped because I wanted to be able to implement it without a domain name lol)
Well idk, I mean an lnurl-auth gem would be nice in general, but I don't necessarily think it should be shoved into this gem you know? It should probably be its own gem just because if you implement lnurl-auth into this gem then people will become surprised that you don't have every lnurl protocol in the gem so.
👀 @nerd2ninja
k00b lol this repo is 4 years old. I think I actually played with it a little when I was trying to implement lnurl-auth (I stopped because I wanted to be able to implement it without a domain name lol)
anything we should add to the gem?
Well idk, I mean an lnurl-auth gem would be nice in general, but I don't necessarily think it should be shoved into this gem you know? It should probably be its own gem just because if you implement lnurl-auth into this gem then people will become surprised that you don't have every lnurl protocol in the gem so.
(also oh hey wow you're on SN huh? lol)
He did upgrade today https://github.com/bumi/lnurl-ruby/commit/d10be525c36a0a9917069d6485266be10ad43e9c 🤔
Yeah I checked that. A PR to follow redirects and limit how many it follows.
yeah, should always have followed redirects. Even though those are not common in LNURL I think it's just a HTTP best practice here.
Make sense