fiatjaf on Nostr: Alby has started to return a {created: true} object from webln.enable() calls, which ...

Alby has started to return a {created: true} object from webln.enable() calls, which is not in the spec (the spec says to return an empty Promise).

Now some websites are relying on that {created: true} object being present and assuming webln doesn't exist otherwise, which makes it so they won't work on any other extension or environment that correctly implements the webln standard but not the "Alby standard".

In this case it might be a silly example, but this is how protocols die.