Nostr Web Client

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.

fiatjaf 2y ago

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.

Reply to this note

Please Login to reply.

Discussion

bumi 2y ago

I _very_ much care about independent standards and consitency. And I guess you also know that. Everybody involved in Alby and related projects does that and spends o lot of time on it.

We wrongly return a value in a function that should not return anything. (it's {enabled:true} btw. and might even be from the time when I worked on joule)

It was reported, a PR was made and we investigated if any apps rely on it. ONE single application was found afaik that discovered and used that value. The next version will have this changed.

done.

This is also how the process should be. Mistakes are made and they are fixed.

You are right in calling this mistake out and I appreciate that!

Making it sound we intentionally break standards or break all apps or make things so that it does not work in other extensions is wrong.