Pretty sure the gpu BIOS is limited by default, nothing the OS can do about that.
Same for other parts like the cpu - core voltage is determined by the motherboard.
I doubt the os can just go “2V vcore” and blow up hardware.
Pretty sure the gpu BIOS is limited by default, nothing the OS can do about that.
Same for other parts like the cpu - core voltage is determined by the motherboard.
I doubt the os can just go “2V vcore” and blow up hardware.
I’ve been to the US exactly once in my life, and I clogged the toilet at the hotel I stayed at. Never had it at home.
Probably just coincidence, but hey
Wireguard (which is what tailscale is built on) doesn’t even require you to open ports on both sides.
Set up wireguard on a vps first, where it is accessible, then set it up from within your network. It’ll traverse NAT and everything, and you don’t have to open a port on your network.
Tailscale is the exact same thing, just easier because it does everything for you (key generation, routing, …). Their service replaces your vps, up to you if you think that’s acceptable or not. IMHO, wireguard is worth learning at least. I eventually (partially) switched to tailscale because I’m lazy, and all services I host have authentication anyway, with vpn just being a second layer.
How? The sublinks devs started the project just because they didn’t want to work on Lemmy for whatever reason. If they did, they would have worked on Lemmy. It’s either Lemmy AND Sublinks, or Just Lemmy with the same developers.
Having multiple implementations is a good thing, regardless of what language they use. They all implement the same protocol, should be (mostly) compatible, and can learn from (and compete with) each other.
Look at other OSS. There’s so many Linux distributions, Why doesn’t everyone just work on a single one?
Because everyone has a slightly different view on things. This makes the OSS community stronger.
I have seen people wanting to do Java, and while I personally prefer rust, I do see why.
Outside of the entire Sublinks discussion, it’s important to note that Java is not just Java anymore either. Kotlin offers many of the same advantages syntax-wise that Rust does (including the lack of null), and has access to Java’s excellent ecosystem.
Ultimately, it is up to people to decide what they want to use. Regarding of your opinions on Java or Rust, it is a valid choice either way for this type of software. It’s a personal choice.
I’ve never really seen this in (Java/Rust/PHP) backend personally, only in client-side JS (the CORS preflight).
It’s a security feature for browsers doing calls (checking the CORS headers before actually calling the endpoint), but for backends the only place it makes sense is if you’re implementing something like webhooks, to validate the (user submitted) endpoint.
Even if that were true - does it matter?
Java is a perfectly valid choice for something like this.
Yes, Rust is “faster”, uses less memory, etc…
Java is fast enough, though. It offers a fantastic ecosystem and, seeing as these projects are ran by volunteers who do this in their free time, there’s a lot more people willing to chip in some work.
They don’t because it’s not true.
There’s a few things moving to quarkus, but a lot of that is being pushed by Redhat (whose own software was not even spring boot but JEE)
I can see the case for some of them after you’ve been in a crash (although if the pyro fuse has blown, not much requiring switches will work anymore, regardless of the type of controls), but if you want physical controls for the rear view mirror for safety, you should probably start adjusting that before you start driving.
Same for cabin lights, whatever you’re doing that needs the lights on should probably be done stationary, if you care about safety.
Kubernetes yes, but minikube is kinda meh as a way to install it outside of development environments.
There’s so many better manageable ways like RKE/Rancher (which gives you the possibility to go k3s),Kubespray or even kubeadm.
All of those will result in a cluster that’s more suitable for running actual workloads.
Which is why we have HTML5, CSS3, and JavaScript, supported by all major browsers.
Unless you’re doing something outrageously non-standard, there is no reason to block specific browsers.
The difference being that when you’re 10 billion into a renewables project, you usually have SOME generation already, whereas your nuclear reactor isn’t doing shit until it’s fully completed.
I don’t mind nuclear, but the fact is that the reactors take decades to build, whereas renewables can be deployed far quicker. Going all-in on nuclear, and then twiddling your thumbs for 10-15 years while the reactors are built doesn’t sound like a great idea.
I don’t think programming language is a good metric for security. I assume everything I host has issues, and then try to mitigate from there.
IMHO, a better approach is to vet the project beforehand, looking at whether it is still actively maintained. I usually use things like commits, issues, etc to try and gauge whether a piece of software is actively maintained so that when an issue arises, it can be fixed.
You can mitigate much of the risk by using some basic best practices, like isolating all apps from each other (using docker, for example), using a reverse proxy, tools like fail2ban or a web application firewall, using proper database permissions for each app, etc
What I also do is add another layer by making certain applications accessible only over vpn. That won’t work for some tools, obviously, but also reduces the risk for tools you are only using yourself.
I’ve set up several Kubernetes clusters in a professional setting (and work with it daily), but I still use straight docker for running my own stuff.
Using tools like Rancher it’s pretty much no effort to set it up, but the overhead is just not worth it if you’re not using the orchestration IMO.
.eu and your local tld are often quite a bit cheaper too!