RakNet VS libcurl

Halo was mostly all about single player and early multiplayer/local multiplayer but their online netcode has sucked since Blood Gulch. Lots of games do networking horribly, I have been in gamedev making networking and I hate most of what people do. The ones that have a clean natting, based on enet style reliable UDP channels, RakNet style punch are better (RakNet was good until Facebook bought it). It has come a long way but also fallen back. Valve source netcode (on github) is probably the best and you can check it out here. They started with the best in Quake networking, then to Source.

Raknet No longer worked on but from what I've read, it's complete and working. It has been used in many games between 2000 - 2010

Inconsistencies can be prevented by ensuring the server handles all operations and does so in a given order, then transmits the results to clients. I wrote a little about this for my game Avoyd a long while ago. Clients (including a client running the server) send an edit request via reliable ordered UDP (e.g. using Enet, Raknet, Steam Networking etc.) and the server places these in a single queue then performs the edits and sends the results back also using reliable ordered UDP.

RakNet. It's been forked but still not that active.

RakNet (UDP network library)

Then, in another terminal window, we use curl to hit the endpoint:

I'm not a fan of the "Reproducible tarballs" section, because it's explicitly about pre-processing the source code with autotools, instead of distributing a pure, unaltered git snapshot (which `git archive` can already generate in a deterministic way).

The section following then mentions signing the pre-processed source code, which I think is the wrong approach. It makes a difficult situation because of how strongly some people encourage signed source code, yet I think autotools is part of the build process and should run in the build server (and double checked by reproducible builds). If people pre-process the .orig.tar.xz they upload to Debian, this pre-processing won't be covered by reproducible builds because it happens undocumented.

The patch for "reproducible tarballs" is quite involved[0] and has rookie mistakes like "pin a specific container image using `@sha256:...` syntax, but then invoke `apt-get update` and `apt-get install` to install whatever Debian ships at that time".

[0]: https://github.com/curl/curl/pull/13250/files

Made a PR to curl in line with the above: https://github.com/curl/curl/pull/13338

Through the Fast Forward program, we give free services and support to open source projects and the nonprofits that support them. We support many of the world’s top programming languages (like Python, Rust, Ruby, and the wonderful Scratch), foundational technologies (cURL, the Linux kernel, Kubernetes, OpenStreetMap), and projects that make the internet better and more fun for everyone (Inkscape, Mastodon, Electronic Frontier Foundation, Terms of Service; Didn’t Read).

This looks to be a general issue with curl.

On Windows by default it will also be checking the OS certificate store.

https://github.com/curl/curl/discussions/11707

This Docker image is designed to support implementing Github Actions with Python. As of version 4.0.0., it starts with the official python docker image as the base which is a Debian OS. It specifically uses python:3-slim to keep the image size down for faster loading of Github Actions that use pyaction. On top of the base, we've installed curl gpg, git, and the GitHub CLI. We added curl and gpg because they are needed to install the GitHub CLI, and they may come in handy anyway (especially curl) when implementing a GitHub Action.

I believe they have a bit of a point, as it isn’t locally obvious that randlen will match the zero-terminated length of randstr, at https://github.com/curl/curl/blob/1d8e8c9ad1ff3351386422535f.... It depends on the exact behavior and interface