Conversation

Notices

1. Embed this notice
   iced depresso (icedquinn@blob.cat)'s status on Wednesday, 14-Aug-2024 05:28:13 JST iced depresso
   i saw a game once that broadcast everything it did like >ten times in UDP because "that made it more reliable"
   
   RE: https://mastodon.gamedev.place/@PJB/112666295817888264
   • Pleroma-tan likes this.
   • Embed this notice
     iced depresso (icedquinn@blob.cat)'s status on Monday, 19-Aug-2024 08:12:31 JST iced depresso

     in reply to

     • LisPi
     @lispi314 TCP is hopeless.
   • Embed this notice
     LisPi (lispi314@udongein.xyz)'s status on Monday, 19-Aug-2024 08:12:32 JST LisPi

     in reply to
     @icedquinn Sounds like they didn't feel like digging into TCP tuning.
   • Embed this notice
     iced depresso (icedquinn@blob.cat)'s status on Monday, 19-Aug-2024 08:50:35 JST iced depresso

     in reply to

     • LisPi
     @lispi314 QUIC is not bad. I don't like the monotonically increasing counters† but otherwise I would probably use it.
     
     Wanted to implement it for nim before i burned out.
     
     †i dislike counters like this because they could theoretically run out. once they do, what then? just crash the program? everyone just tells me "don't worry about running out of int64s"
   • Embed this notice
     LisPi (lispi314@udongein.xyz)'s status on Monday, 19-Aug-2024 08:50:37 JST LisPi

     in reply to
     @icedquinn Probably why QUIC was made, yes.
   • Embed this notice
     iced depresso (icedquinn@blob.cat)'s status on Monday, 19-Aug-2024 10:28:22 JST iced depresso

     in reply to

     • LisPi
     • rheaplex
     • gentoobro
     @rheaplex @gentoobro @lispi314 variable length identifiers are what CRDTs use now. it does complicate some stuff. old formats were built in the age of everything-is-a-db-record.
     
     in the case of network protocols a "i ran out of handles—negociate restart" is fine. what happens now is basically undefined behavior (likely it will just wrap because thats what the machine code does, but you are supposed to track those so if it wraps back to 1 it would be interpreted as trying to send outdated packets)
   • Embed this notice
     rheaplex (rheaplex@social.xenofem.me)'s status on Monday, 19-Aug-2024 10:28:23 JST rheaplex

     in reply to

     • LisPi
     • gentoobro
     @lispi314 @icedquinn @gentoobro 1969 to 2038 was a loooooong way off.
   • Embed this notice
     LisPi (lispi314@udongein.xyz)'s status on Monday, 19-Aug-2024 10:28:24 JST LisPi

     in reply to

     • gentoobro
     @gentoobro @icedquinn For similar reasons it annoys me that unix timestamps aren't bignums.
   • Embed this notice
     gentoobro (gentoobro@shitpost.cloud)'s status on Monday, 19-Aug-2024 10:28:25 JST gentoobro

     in reply to

     • LisPi

     You'd have to go really fast for a long time to run out of int64's. You'll run out of unix timestamps in a similar order or time, so it's not much different from a timestamp.