Boof
Yes, it’s a full 24 hours, but a library doesn’t use 24:00:00 to represent the last hour, it’s 23:59:59. Once it hits 24:00, it rolls over to 00:00:00.
Hence my initial error of answering 23.
It’s not valid, but I don’t edit out erronous answers because I believe all data should be preserved, no matter how dumb it makes one look.
Pseudocode and/or a variant of lua.
Most date libraries count to 23h 59m 59s then roll over to 00h 00m 00s. So the answer is 23 hours, not 24.
Edit: I’m big dum dum. It’s asking string length of “Monday”, thus 6.
Spaces have been a thing for over 2 years now.
This is in addition to forums, git, wiki, etc, which those communities also provide.
Matrix is the best platform IMO, and actual dev communities agree. (See: Github, Mozilla, KDE, Nix, the list goes on)
Absolute chads those madlads
I can’t anymore. Leads to system crashing randomly. 11 works unfortunately.
Could you elaborate a bit?
Isn’t Proxmox etc. “Gpu less”, as they only use tty instead of anything like a WM or DE?
I’d prefer a “master” / hypervisor running a bunch of VM’s for different purposes.
Whether they be for gaming, pirating, development, pen testing, home automation, porn, or anything else really.
'Course I’d only be running gpu passthrough into a single VM at a time, can’t split a single GPU into 50 passthroughs yet.
iGPU shares one monitor with the dGPU, but on different protocol, which from what I read online is supported.
It only really needs output when I flick it open.
So maybe it needs a KVM switch instead of trusting the monitors splits.
How would hooking up everything to the GPU be beneficial when it comes to GPU passthrough?
Albeit is it even necessary these days.
You can disable it explicitly, yes.
It should be possible to use it with the dgpu.
Edit: You can also prioritize using the iGPU over the dGPU in bios. Maybe that’d work, hmm.
Sadly not sarcastic. Ideal is Radeon handling the base, and NVIDIA being used in passthrough.
They just refuse to cooperate.
Scenario 1. X11 “works”, wayland doesn’t. Trying to update NVIDIA drivers leads to boot failure.
Scenario 2. Wayland works. Only on igpu. Only via HDMI. Only on one monitor.
Scenario 3. Wayland works on Displayport. Doesn’t even recognize second monitor.
Scenario 4. Everything seems to work. Trying to do GPU passthrough fails.
Scenario 5. IGPU is hogging displayport, despite being connected via HDMI, thus preventing the DGPU passthrough on either HDMI or DP.
The good ol fashioned,
<center><div>hecc</div></center>
div {display: inline-box; text-align: initial}
Well to be fair, Microsoft used to be entirely proprietary until recent.
Same thing with things like Ghidra; used to be a completely locked up proprietary software for NSA, now it’s open source.
Hashing on client side is both more private, and secure. All the user ever submits is a combined hash (auth/pubkey) of their username + password.
If the server has that hash? Check the DB if it requires 2FA, and if the user sent a challenge response. If not, fail the login.
Registering is pretty much the same. User submits hash, server checks DB against it, fail if exists.
Edit: If data is also encrypted properly in the DB, it doesn’t even matter if the entire DB is completely public, leaked, or secured on their own servers.
Argon2 is the best (secure) crypto currently.
That said, adoption is slow, Bitwarden only recently implemented it for example.
That said, due to Argon2 being security-oriented, the recommended settings for it are pretty heavy.
Well to be fair, if they’re hashing serverside, they were doomed to begin with.
But yeah, there’s a lot of ways to DDoS, and so many tools that just make it a 1 button click.
It’s more so lucky that there was someone diligently doing that. It could’ve easily gone unnoticed had there not been someone like him.