Goolag Protocol

What does Any Forums think of this protocol? Is TCP deprecated now?

Attached: Screenshot_20220714_164607.png (875x578, 62.89K)

I'm using it right now

Attached: file.png (281x220, 8.11K)

Does it bring any improvements ?

Supposedly. Like multiplexing and stuff. Also, encryption is mandatory, that's why HTTP/3 only supports https

How? Is it because of cloudflare?

Yeah, CDNs mainly uses HTTP/3 therefore QUIC. You can see it under your network tab

Attached: 4cdn.png (430x366, 50.05K)

Yes, tcp is deprecated like ipv4 is.
Yeah some good (possible) performance and security. The stream stuff is great as well.

maybe, it should mean your single websocket server can handle >65,000 users at once if you convert it to webtransport/quic.
right now the best practice is to keep active websockets to

What do you mean by scaling horizontally and vertically mean. I think I once read that horizontally is running more instances per machine and vertically is running more machines but I'm not sure.

Nevermind.
>Horizontal scaling means scaling by adding more machines to your pool of resources (also described as "scaling out"), whereas vertical scaling refers to scaling by adding more power (e.g. CPU, RAM) to an existing machine (also described as "scaling up").

vertically is more cores/ram/storage
horizontally is another instance or node
lichess scaled vertically so they have a single beefy server that runs all the games (you can call this a lack of planning)
liwords (scrabble with friends) can scale horizontally, they anticipated the need to have more servers instead of painting themselves into a corner (premature scaling?)

What about the networking side? I read that network admins hated QUIC because it's harder to manage

>Also, encryption is mandatory, that's why HTTP/3 only supports https
Is that going to make https certificates obsolete ?

>Is that going to make https certificates obsolete ?
No, its the opposite, certificate is required to run a quic or http/3 server

But from what I read , this encrytion will be already implemented at the transport layer. Doesnt that negate the need to have a third party certificate ?

Yeah webtransport is cool. But right now its a pain in the ass to develop because there is no message framing like websocket. It's basically just a TCP stream replacement.

The encryption does happen inside QUIC, but you still need to provide the certs yourself if you deploy your own server. The difference between TCP+TLS is that QUIC embeds the TLS stuff inside the protocol, making them required

Oh crap, I hate provisioning certs

QUIC is just HTTP over UDP

>we reinvented the wheel
quelle surprise

Attached: well-thats-actually-kinda-cool-photos-4-2.jpg (550x1130, 71.17K)

the certificate requirements for some software are the reason i always have TLS certificate with cname * (that is, all domains), with start date of 1970-01-01 and end of 2070--01-01

more like we invented a new wheel that performs well both on and off the road