HTTP doesn't change every day. Hardly any effort involved in staying compatible.

Reply to this note

Please Login to reply.

Discussion

No effort in staying compatible with NIP 1 Kind 0 either... That's my point.

And your point is wrong.

How long has it been since you couldn't listen for kind 0 events on web socket servers and retrieve messages?

There isn't a spot angle client fully compatible with nostr anyways. There likely never will be. Amethyst comes close.

Whoops, I am wrong. I meant to refer to messages. Kind 1. Now I look stupid. 👏🏻

Kind 1 is being moved out of NIP 01, and we're supposed to avoid using Kind 01 for anything other than tweets, going forward, so still wrong.

Lots of apps will have to be rewritten.

Then I'll take the L. But I'm now interested in looking closer at HTTP's history of development. Perhaps I can learn me sumthin .