I thought this is how standards are started and evolved? isn't that also how nostr does things?
Discussion
Its how all web "standards" were created in the past
You mean standards exist to be broken by the biggest player so the ecosystem centralizes more and more?
Why is it Alby's fault? If something like this provides value (i.e. is implemented by clients) isn't it worth considering adding it to the spec now?
By not following the spec Alby is causing all other clients to break. Because Alby is the biggest provider everybody will assume that whatever Alby does is the spec and others will have to either follow or die. You might as well call it the AlbyLN standard. If that is not centralization I don't know what is.
You can do it, no one is going to stop you. But you can't also keep saying it's an open standard.
With that said, I know these things are hard and it's easy to make mistakes. Maybe you didn't expect apps to start relying on the {created: true} response and it wasn't your intention to break other apps -- that's one of the reasons why I'm pointing out this: to warn people about these small slippery slopes.
But from nostr:nprofile1qqsrxra3gv0lnkxz2pcxh0xuq9k4f9dr7azwq3aypqtnay4w0mjzmtqprpmhxue69uhhyetvv9ujuumwdae8gtnnda3kjctvqyt8wumn8ghj7un9d3shjtnwdaehgu3wvfskueqpr4mhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet5qq7dwn 's answer above I get the feeling that he doesn't care and thinks this is even good.
What value does this provide other than break other WebLN clients?
It’s completely useless. It serves no real purpose whatsoever.