|
|
|
|
|
|
by jimmydoreornot
1028 days ago
|
|
|
1. I concur. But it's no big deal.
2. Nothing prevents this, but it would be specified as a sister protocol. I haven't seen it specified, but I know that relays are doing it.
3. Websockets allows pub-sub. Clients stay connected to relays and instantly get the next message when it arrives. Polling means either lots of polling or having delays.
4. I can't even comment on this one.
5. Optional chaining is possible and has been proposed. I also started a nostr-like protocol back in November 2022 based on my gripes with it. Then I came to my senses... nobody is going to use my variant. Perfection is the enemy of the good. |
|
|
Then, how are you supposed to know how to do if it is not specified?
> 3. Websockets allows pub-sub. Clients stay connected to relays and instantly get the next message when it arrives. Polling means either lots of polling or having delays.
You can remain connected even with plain TCP (or with TLS) too. But, if you only want to send or receive a single message (rather than waiting as new messages arrive), then HTTP would also do.
> I also started a nostr-like protocol back in November 2022 based on my gripes with it.
Do you have the document?