Are you not allowed to ask questions? Are the people who write the specs your team mates or are they your enemy? Of course you can play dumb, but that might result in your colleagues thinking that you are dumb.
Are you not allowed to ask questions? Are the people who write the specs your team mates or are they your enemy? Of course you can play dumb, but that might result in your colleagues thinking that you are dumb.
If you happen to have a Fritzbox with VoIP capability it contains a SIP server and you can register SIP clients on it (e.g. Fritz App Fon, linphone, twinkle) and use them to phone internally.
You can use your phone with mobile connection (not WiFi) to check if it can see the file that you made available on your web server.
You’re correct that it won’t draw 650W. You could get a power meter or a power measuring plug and measure the energy consumption.
HTTP3 uses UDP, which is 6 years younger than TCP.
Don’t put it in /usr/bin, that’s where your package manager puts executables, not you. Other than that, do what you want. /usr/local/bin is good, or if it’s only for your user ~/bin, ~/local/bin or ~/.local/bin - I don’t care. Also just let your users decide where they want to put the script.
Programmers use rubber duck debugging sometimes.
Recently I got a new PC with Windows, and it could resize its partition without problems. You can do it even with Powershell. I don’t know how dangerous it is, but with the whole “copying user data” I would hope that the installer would advise users to create a full backup anyway.