![](/static/66c60d9f/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/8286e071-7449-4413-a084-1eb5242e2cf4.png)
Some (probably most) domain registrars allow to use different nameservers. So for example i use namecheap, since its cheap as domain registrar but cloudflare for DNS, since the API is free and widly supported.
Some (probably most) domain registrars allow to use different nameservers. So for example i use namecheap, since its cheap as domain registrar but cloudflare for DNS, since the API is free and widly supported.
Not what i am saying. I said that it is not a given, that translation means less performance.
In theory you can achieve similar or even higher performance, all depending on how well or how bad the original machine code is. Especially when you can optimize it for a specific architecture or even a specific CPU.
And yes ARM has shown to be more power efficient then x86 CPUs even on higher load (not just low powered embedded stuff).
and any efficiency gains these fancy new ARM chips supposedly have will be lost when translating x86 to ARM.
Not a given. Translating can still be more efficient.
Everyone knows what the blue screen is. This makes the implication when the screen does appear really obvious.
No need to reinvent the wheel.
And you need a team managing it. I doubt that they have not considered it.
No Gitlab is not AGPL, it is partly MIT and the corporate branch is under a proprietary license
No, cat is not for writing files. Cat is for reading files and directing the data to standard output.
With “>” you are directing standard output to a file, in this case a blockdevice.
Why? I am free to use whatever I want. This is not Microsoft Windows.
Or just cat file.img > /dev/…
They would not be able to really. In theory every contributor (or at least the vast majority) would have to agree to that license change.
Yes. But it allows to define a custom storage layout based on user date time filename typ and album.
That would depend on the context. How the logo looks like does not matter most of the time, only when the logo itself is the topic.
I self host because i do not trust companies. I will not even consider giving tailscale the keys to my kingdom.
The company Tailscale is a giant target and has a much higher risk in getting compromised than my VPN or even accessible services.
Understand the technology that you use and assess your use case and threat model.
Why not file a bug report when it does not find all your photos?
Also may file a feature request to delete photos after set period from your device via immich?
guess a username and a password.
Security by obscurity is no security. Use something like fail2ban to prevent brute force. When you use a secure password and or key this also does not matter much.
disable root login
That does not do much in practice. When a user is compromised a simple alias put in the .bashrc can compromise the sudo password.
Explicitly limit the user accounts that can login so that accidentally no test or service account with temporary credentials can login via ssh is the better recommendation.
Imagine that the xz exploit actually made it into your server, so your sshd was vulnerable. Having it on another port does seem helpful then.
Nope. Your entire server can be scanned in less than a second for an open ssh port.
IPv6 does not change the fact since when your server is attacked the hist IP is already known.
Security by obscurity is no security.
Who the hell is pulling the docker-compise.yml automatically every release? I find myself already crazy by pulling the latest release but the compose file is just a disaster waiting to happen.
Have found it by accident too. Just amazing.
Would love something like that for the Desktop. Basically a Cockpit+Serverbox+xpipe for my desktop clients.