CubitOom

Yeah, you’d have to figure out how to define a “problem” first. It’s a better IDE to define what metrics might indicate you need to replace soon before a problem actually happens.

You could just run it in a cron and have it tee to a file or even send an email report

I was running the numbers in my head and realized that if hosting media like music and video files where it’s just written to once and read from a lot, a large 2.5 inch SSD might be a better buy than a HDD (especially if size limited to a 2.5 inch HDD). My reasoning is that a HDD needs replacement after around 50,000 power on hours. But an SSD needs replacement depending on how often the entire drive is overwritten. For a media server that should mean that the HDD will be replaced much more often than an SSD. And that’s without considering vibration related issues of having multiple drives in the same server or if you experience frequent power outages (both of which would make a better case for an ssd.

So what I do is I use an M.2 SSD for the OS, and the largest 2.5 sata SSD I can find which will fit my storage and backup solution. (recently bought 4x 8TB SSDs). For the m.2 drive, try to get the best value size as I’ve never heard anyone complain about having too big of a drive.

For all SSDs (m.2 and data) make sure that it accurately reports SMART data for you can keep tabs on their health metrics.

Well again, the claim was that somehow passkeys would stop Lemmy from being flooded by bots.

So in that situation, we aren’t talking about hacking. We are simply talking about if a login could be triggered programmatically. So if Lemmy required passkeys to be used instead of passwords. And if the passkeys required scanning a QR code to sign in. I imagine It would provide minimal disruption to an automated login.

Now if the passkeys somehow enforced a real human to do something that only a human could do, then yes it would stop an automated registration/login. However if it’s possible to automate then it wouldn’t stop bots.

Oh I don’t know what it is, sorry I thought I made that clear. But a quick search on the internet said it was basically 2fa with a qr code and since the issue was how it would protect Lemmy from bots I just thought it wouldn’t be hard for a bot to read a qr code.

Insane

Consider buying a previous generation card. You can sometimes find good deals on used ones.

Oh, you can easily bypass passkeys with automation. Don’t even need an image recognition model, just a QR-code scanner like zbarimg.

But i never tried googles passkey feature since it never seemed as secure as a 48 char computer generated password. So I’m not sure exactly how it works.

What would you propose replace passwords to not be susceptible to those things?

I personally like how secure and non intrusive passwords are, especially when using a self hosted password manager synced with git.

If you don’t have a smart phone in the US, even temporally, your almost a second class citizen.

Then if you don’t install corporate apps on your phone, there are even more problems for you.