Last I saw Alby wallet seemed reluctant about it. I wonder if they have any updates since nip 57 has been officially merged? #[2] #[3]
Discussion
I just dropped a question to Alby in Telegram. No answer yet.
@bumi replied in telegram "we for sure want to support developments like that"
Reading the PR he had some questions: https://github.com/nostr-protocol/nips/pull/224
In my opinion the spec has problems that I shared in my comments in the GitHub issue.
It adds Nostr specific complexity to the universal LNURL protocol which will make it harder for LNURL providers to implement.
I would have hoped we build on existing interoperable protocols (like LNURL) and not need to invent a new Nostr specific one (which also only works in Nostr). This now means all tools and service providers need to support Nostr to make this possible - this will take time (it took LNURL years to get to the current adoption)
To me interoperable, reusable protocols are key.
And don't forget payments on Nostr are possible. You can tip/zap any lightning address. Only the payment proof (the zap) will not be published on Nostr.
But ultimately adoption and demand will matter. We need to make Nostr big to convince everybody. :)
Alby is for sure committed to support this as much as possible.
Is it difficult to implement? At what point/level of Nostr adoption do you consider it important enough to implement in its current form if it doesn’t change the way you’d want it to? And is waiting the right decision? Maybe it is for Alby. I’d say it’s not the right decision for Nostr users. So wallet providers that implement it now will have an advantage on Nostr. How important do you consider Nostr to be moving forward? Those are the relevant questions.
I am not saying Alby is waiting. As mentioned Alby is committed to push this forward as much as possible.
I personally just believe that some other proposals would have seen faster adoption. It is not ideal that all lightning address providers are required to now make Nostr specific changes. this slows down adoption and is not really the idea of interoperability.
It's not all about adoption. Fiat has the highest adoption. UBI is certainly very poppular with the people.
Sometimes the right thing to do is not the popular thing.
I hope Alby will still suppot normal LNURL tho :)
hehe :) that's the main thing of course. the one thing that we currently have as such a higher-level standard.
Ah my bad for misunderstanding. No doubt Alby has shown its commitment to supporting Nostr. And I think it’s good to have people like yourself raising these questions early on. 💜🤙
Thanks! He responded here too just a few minutes ago. I’ll tag the note below. Good to see them supportive and raising questions now makes sense.
#[7]
this is the mentioned pull requests: https://github.com/nostr-protocol/nips/pull/224 it's worth reading to understand the discussion.
The reason is that NIP-57 is badly designed, with no interoperability with existing LNURL or LN Addresses. In fact, you cannot support both zaps and normal LN Addresses or your profile.
Read the NIP.
People celebrate that it was merged as a sort of accomplishment.
No, it was merged because it turned out feedback was being ignored and multiple parallel implementations were being pushed, regardless of the issues raised or improvements suggested.