Sleepkever

joined 3 months ago
[–] Sleepkever@lemmy.zip 1 points 6 days ago (1 children)

No need to be so hostile.

Installing docker desktop is fine but if you are on Linux and in any way comfortable using the command line I'd definitely run without the desktop part. Just docker and the composer addon is enough.

That nginx proxy manager recommends desktop for Linux environments which most of the time don't even have a GUI is a bit bizar tbh.

[–] Sleepkever@lemmy.zip 18 points 2 months ago (1 children)

The usual trick is hdparm I guess? For me with a 8 disk raidz2 pool I found that playing a movie from that might put it to sleep between reads, because the longest timeout is a bit short. I've been using hd-idle with a 30 minuten timeout because of that for quite a few years already which has worked quite nice for me.

The only issue I've run into is that smart data reads count as activity, so make sure that any smart data software has a long timeout between reads and is configured to not wake disks.

[–] Sleepkever@lemmy.zip 10 points 2 months ago* (last edited 2 months ago) (2 children)

The attack vector is an autofill function on a compromised website that has attackers javascript running either injected in a webpage or on a subdomain hosting user content. Since autofill will never fill passwords from another domain, others won't be at risk. But why bother with clickjacking at that point, you could just have your malicious script read the password values silently once the user enters it, password manager or not. That's not a password manager problem, that's the problem of the vulnerable website.

The one which is actually dangerous that shared all password for all domains actually had a bug bounty awarded to the guy and is now fixed, good for him on finding that. The rest is really a non issue , I wouldn't worry that much.

Though credit card details and personal user info autofill might be problematic since those are not site-bound. I would either disable those or just not store them in the password manager.

[–] Sleepkever@lemmy.zip 6 points 3 months ago

Looking up similar images and searching for crops are computer vision topics, not large language model (basically text predictor) or image generation ai topics.

Image hashing has been around for quite a while now and there is crop resistant image hashing libraries readily available like this one: https://pypi.org/project/ImageHash/

It's basically looking for defining features in images and storing those in an efficient searchable way probably in a traditional database. As long as they are close enough or in the case of a crop, a partial match, it's a similar image.