mleku on Nostr: forward compatibility is always easy, backwards not so easy anyway, it's just a ...
forward compatibility is always easy, backwards not so easy
anyway, it's just a matter of building out a few clients that use the new protocol, and there's lots of reasons to change the way it's done because light clients like ebook readers often can't do websockets, and this was a big part of why specify that unless an API requires subscriptions it doesn't need websockets
the client devs anyway need to leran how to architect and modularise their code anyway
so, i'm just gonna push forward to build out new stuff that uses the new protocol and i know i have people who will adopt it due to its greater simplicity
probably better i just the forward compatibility (old to new) problem altogether
anyway, it's just a matter of building out a few clients that use the new protocol, and there's lots of reasons to change the way it's done because light clients like ebook readers often can't do websockets, and this was a big part of why specify that unless an API requires subscriptions it doesn't need websockets
the client devs anyway need to leran how to architect and modularise their code anyway
so, i'm just gonna push forward to build out new stuff that uses the new protocol and i know i have people who will adopt it due to its greater simplicity
probably better i just the forward compatibility (old to new) problem altogether