mariusor 2 days ago

> are UDP. some

:P

  • mafuy 2 days ago

    Misses, sure. But it should be quite rare that the order is wrong. It would only happen if the route changes.

    • jvanderbot 2 days ago

      Or, does "Alexa, add peanut butter to shopping list" fall under the UDP frame size? Joke reversed.

      • JdeBP 2 days ago

        Your wife is possibly wondering why you send everything cleartext in one single frame and don't do challenge-response or any sort of state machine resynchronization between client and server. (-:

    • mariusor 2 days ago

      Eh, comedic posts should probably be allowed some leeway in their attempt at being funny.

      • JdeBP 2 days ago

        Especially as it's impossible to tell whether jvanderbot's "people" datagram got dropped by some intermediate hop in the UDP version or was never sent. (-:

  • TOGoS 2 days ago

    That's why you put enough context in each packet that nobody gets confused if the order changes or some get missed.

TeMPOraL 2 days ago

And some people, like me, are... what do you call TCP but without initial handshake? Like:

----

Other person: Hi, what time was that thing?

Me: Hey, 14:00.

...

...

Me: Hey, 14:00!

...

...

Me: walks in their face Hey you, the thing you asked, it's at 14:00.

Other person: Yes yes, I heard you first time!

Me: boils internally, muttering to themselves so why the fsck didn't you say so?

----

Please don't hang on "Hello", but for $deity's sake, confirm reception of messages, especially in analog communication.

  • simonw 2 days ago

    Weirdly I really enjoyed MrBeast's line on this in his leaked internal production memo:

    "Since we are on the topic of communication, written communication also does not constitute communication unless they confirm they read it."

    https://simonwillison.net/2024/Sep/15/how-to-succeed-in-mrbe...

    • whoisyc a day ago

      This is why emoji responses on Slack are so useful. You can ask others to affirmatively confirm that they have read a message and they can make the confirmation without clogging up the channel with tons of text messages.

      And no “read receipt” as it is usually implemented would not cut it, because it only means “this message showed up on the recipient’s screen once” not that they have actually read it.