I learned this in highschool when I discovered sending ping floods from a 1gbit VPS to a slow residential Internet connection can take down your Internet even if the router doesn’t respond to pings. The bandwidth still all needs to make it to the router in your house to be dropped.
Unless you’re rebasing or something, you should never need --force
. It’s a good way to accidentally delete or overwrite a remote branch.
I usually use the +syntax for force-pushing a specific branch:
git push origin +my_branch
This graph actually shows a little more about what’s happening with the randomness or “temperature” of the LLM.
It’s actually predicting the probability of every word (token) it knows of coming next, all at once.
The temperature then says how random it should be when picking from that list of probable next words. A temperature of 0 means it always picks the most likely next word, which in this case ends up being 42.
As the temperature increases, it gets more random (but you can see it still isn’t a perfect random distribution with a higher temperature value)
Clickbait from before it was called clickbait.
Pretty sure Ubuntu LTS is completely unaffected by this.
I hear that WireGuard is even more complicated to set up than OpenVPN.
I don’t know where you heard that. The exact opposite is true in my experience. OpenVPN is a shitshow compared to Wireguard.
I used to play so many of their games. The Escape Velocity series was great. And I remember one called Slithereens. Oh the nostalgia!
This article seems poorly written and says the same thing over and over again with slightly different wording. I would have liked some more specifics.
The Cyber Resilience Act (CRA) could have several implications for the open source software sector:
- Increased legal and financial responsibility
- Deterrent effect on the development of open source software
- Lack of consideration for the specificities of open source software
- Lack of consultation of the open source software community
Only 2 of those are implications of the law. 3 and 4 are redundant and are not caused by the law’s wording. They wouldn’t even be a problem if not for 1. 2 is also caused by 1 in a fairly obvious way.
Hows does the limitation of liability section in basically every open source license factor into this? It seems like you’d be fine as long as you aren’t personally using the code commercially? Or would this new law somehow override the open source license?
Personally I use dnsrobocert with my own domains. I’ve got a few subdomains that point to a Wireguard subnet IP for private network apps (so it resolves to nothing if you’re not on VPN). Having a real valid SSL cert is really nice vs self signing, and it keeps my browser with HTTPS-Everywhere happy.
I second this. It helps that basically every distro is highly customizable, so if you don’t like some default settings or something’s not supported on a specific distro, it’s usually still possible to get it working with some manual tweaking. You don’t want to be spending the time for every application though, so finding a distro that supports most of what you need out of the box is a good suggestion.
Well, we had Windows 10 for over 5 years before Windows 11. 10 was supposedly the last version they were doing, so it’s a little surprising they’re back to regular major releases now.
Based on a world population of 8 billion, that would be roughly 0.000000000000008% of a person. It’s also not even representable as a 64 bit float so I had to do this math in my head (Calculator just says 0)