My experience with academia is that most of this hard work is done by undergrads, and conception and management by professors; developers aren't hired to do this. So besides "going back to school", there's no way in for an outsider.
Bunching together happens because of irregular speed. You have traffic clusters because the front is slower than whatever the "natural" speed is, but not so slow that people elect to pass.
If traffic is all moving in a narrow range of speed the clusters are smaller and less dense.
People will manage to circumvent the firewall if they want to attack your site. But you will still pay, and get both the DoS vulnerabilities created by the firewall and the new attack vectors in the firewall itself.
environmental "awareness" doesn't mean dog poo; environment-friendly will only be prioritized when it's cheaper to do so. That's why government subsidies and taxing are REQUIRED.
The western world should have subsidized it too, now you can't dismiss it because it wasn't organic--because it NEVER would be organic.
That's why environmental "awareness" doesn't mean dog poo; environment-friendly will only be prioritized when it's cheaper to do so. That's why government subsidies and taxing are REQUIRED for the switch to more environmentally friendly alternatives--this applies to everything, from fossil fuels to packaging.
I agree. That documentation really needs some love. But if you see the discussions on github issues about quadlet features a common theme is maintainers dismissing requests because "that shouldn't be done in production" or "that won't scale". It seems they can't wrap their head around people wanting to do simple things or someone doing things by themselves at home and not for work at a big company or corporation, and that reflects on that documentation.
Working for one myself, which does have a support contract wit Red Hat, I kinda get where they're coming from--if they make it easy to shoot yourself in the foot, dumb people shoot themselves in the foot in production and they have to fix the mess later. But for that they could have a sanctioned build for clients and a community build for everybody else, just like they have Fedora and RHEL.
Running a very similar setup here, also have issues with networking. Pasta worked, but has bugs and replied UDP packets on the wrong ports. The pasta version from debian packages is too old. Also, I tried making the networking work but now I just slap --network=host on everything and call it a day--works perfectly.
reply