i created my own protocol for my games...

Watching people who are great at using vim is like watching people training at the gym: you find them sexy, you want to be like them, but you don't want to go through the effort

"kinda FUN" (laughs in 9999 possible vulnerabilities)

These video formats are my favorite. Love the content

"[...]I think that's probably more than enough, than I need" You're just asking for trouble now.

Man, really wanna see more of these kinds of videos - your deep dive into this, showcasing also your knowledge of things like TCP protocol and websockets, is super interesting :)

Yes, I did. Unfortunately it was written in lua, so as you can imagine, the moment I stopped sending string identifiers was the moment it kind of lost its ground.

I created my protocol 10 years ago, consider a short in the packet for routing, do not use a int for len unless you want recieve 2 gb packets, handle all connections and packets in a own async thread pool. the CPU has a fast array copy instruction, keep that in mind.

Prime leveling his scope creep skills.

I've been using little-endian in my protocols for years, just because all the major architectures use it. It simplifies a lot of code and saves the small perf hit of having to convert back and forth constantly.

I've created my own protocol but with variable length integers in header, because it is more _fun._