My understanding is that those settings just disable priority alerts, only some custom roms will let you disable critical alerts.

Some of these used the site using legitimate URLs, others were looking for back doors, most likely so they could get to the data before it appeared on the site, or to manipulate the data presented to users.

I'm sure they know what they're doing, making me very wrong, but bots probing for back doors is very common, and not at all anything to be concerned about. The attackers most likely don't even care about the data, all they want is another site to spread malware or to join their botnet.

AI scrapers can be brutal though, and is very relevant.

Do you know if I'm able to authenticate logins with wget? As in, I'm actually downloading from a cloud service and I'm worried that it'll give me a 401 Unauthorized.

If you open the network tab on the devtools, you can usually copy a request as a curl command. I believe downloads also show up there and it will let you curl the file with all the cookies and headers that the file was originally requested with.

There's a few websites now that support WebAuthn which Windows Hello (requiring a TPM) should support.

For example, the Australian passports.gov.au defaults to "passkeys" and makes it clear they're "recommend", my.gov.au also supports passkeys but prefers their mobile app. I just use a Yubikey (+ Linux) though, and it's always optional anyway. Though I also don't know of any banks using WebAuthn.

I don't think you can overwrite files, it was more intended so you can rebuild wheel files against a newer version of python, without having to create a new release.

e.g. you've built and uploaded: myapp-1.0.0-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl, and then after python 3.14 released you can rebuild your release outputting: myapp-1.0.0-cp314-cp314-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.

Though it's usually only for projects that contain non-python code. Most projects will build into: myapp-1.0.0-py3-none-any.whl.

You are talking about blocks as physical delineations in an ssd, containing many pages with erase cycles. Op is talking about the filesystem view of blocks, which is different altogether.

I'm pretty sure OP is confused themselves, but I read this as referring to the physical sector size.

I'm not sure what this means, pages are a concept in an ssd's physical structure, they don't mean anything to a filesystem (except in volatile memory).

Fair enough, I probably explained it poorly. The problem is that pages don't mean anything to the filesystem, but the way the filesystem is layed out means a lot to the pages. With 512e, the SSD has to buffer each write until it can make up the whole 4K page. It'll also buffer a read until the whole 4K page is read. So if those buffers never become full/read, such as when the filesystem isn't aligned to it's pages, or the read/writes aren't in the right sequence, then it destroys your performance.

This also happens with HDDs, but they're slow enough to be able to rearrange operations, though an unaligned filesystem will still cause unnecessary reads before writes.

Do not worry about emulated block size, because ssds only use that to report to the filesystem, no sectors exist on solid state media.

Well SSDs have flash pages, which are essentially sectors as they are the smallest unit you can read/write, and they're usually 4096 bytes on NAND flash. My understanding is to write to a flash page you have to erase the whole block of 32+ pages before writing, so if a 512e SSD doesn't receive the rest of the page in time (e.g. with IO scheduling, 512 byte fs sectors, unaligned partitions, or bad luck), then the controller has to do a read-erase-program across the whole block of pages (although wear leveling will probably read + copy the modified page to elsewhere instead), instead of just a single program operation on one page (assuming a properly trimmed SSD).

So IMO, 4Kn is more important on SSDs, yet every vendor sets 512e by default. Luckily quite a few NVMe SSDs (not Samsung), let you change the logical block size with an nvme format command.

But more related to the OP, HDDs are a lot slower and don't have to erase multiple sectors before a write, so it's not as important, however partition alignment is still important but usually handled automatically in every modern partitioning tool. Sometimes you can switch a HDD to 4Kn with hdparm, but this isn't common, and you've said your HDD is dead anyway, so it won't help.

Also, sorry about bringing you into this, I have strong opinions against 512e SSDs haha.

Just be careful, I think I got a fake. I noticed the firmware was out of date, so I tried the Intel SSD update tool, which errored out with "Please contact Intel Customer Support for further assistance". Now the SSD no longer mounts and puts a bunch of nvme errors in the dmesg.

I think Tā moko and similar, like I don't really like it, but it's a cultural thing, so I don't think it's stupid.

It'll go to the lock screen and eventually go dark. RDP (on Windows) doesn't let you share screens/controls, AFAIK.

What's strange is that the last rollover was in 2019. How did it go this long before failing?

It probably wasn't the week counter rolling over, but rather it forgetting that it had rolled over in 2019.

They previously said this was caused by a software update, so I guess that update may have reset that rollover counter.

Having DDR4 on a CXL card reminds me of having DDR on a PCIe card.