dr_zoidberg

MS Paint wanted to add the "this is AI" tag on a picture they just resized. OP didn't like that, so they went and downloaded Paint.Net to avoid having to deal with (MS) Paint shenanigans.

Not sure about that, SSDs historically have followed base-2 sizes (think of it as a legacy from their memory-based origins). What does happen in SSDs is that you have overprovisioned models that hide a few % of their total size, so instead of a 128GB SSD you get a 120GB one, with 8GB "hidden" from you that the SSD uses to handle wear leveling and garbage collection algorithms to keep it performing nicely for a longer period of time.

It's at the end, in the "What are the standards units?" section.

Yes, the thought crossed my mind too... But then I tried a private window and it opened, so maybe the other suggestion that the cookies are very long lived is right.

A little bit off topic: but I couldn't even start to read the article because "I reached my article limit" out of I site I never visited before... What are they using to determine how many articles I've read?

Opening in a private window solved the issue, however I'm pretty sure I don't regularly read anything on this site (maybe never was an overstatement?).

The abstract of OPs link mentions "Processing-Using-DRAM (PUD)" as exactly that, using off the shelf components. I do wonder how they achieve that, I guess fiddling with the controller in ways that are not standard but get the job (processing data in memory) done.

Edit: Oh and cpldcpu linked the ComputeDRAM paper that explains how to do it with off the shelf parts.

No, I just went to search if the topic is mentioned in guidelines (which it is, multiple times). I'd then expect a (good) expert to pick on those breadcrumbs and search on how to do that (if they don't have the skills already). If I were working on a computer, I'd try to find IOCs that point to an infection (or lack of evidence for it).

If there's a memory dump to work on, a more in-depth analysis can be done with Volatility on running processes, but it usually falls back on the expert having good skills on that kind of search (malfind tends to drop a lot of false positives).

But at least the guides gave a baseline/starting point that seems to be better than what was described. It's very difficult to prove a negative, so I'd also be careful with the wording, eg: "evidence of a malware infection was not found with these methods" instead of "there's no malware here".

That's interesting. A project at work is affected by Windows slow open() calls (wrt to Linux/Mac) but we haven't found a strong solution rather than "avoid open() as much as you can".

As of now 9%. I thought hitting the HN front page could have a much larger impact on this, but it seems that's about it this time.

When I moved some projects from OpenCV 3 to 4 I got a nice speed up pretty much everywhere, some things no speed up at all and some others pretty big. I can't really remember the numbers, but at the moment it was a global 10 to 20% perf improvement just on updating a library.

Might want to check that. Also 4.something got SIFT as part of OpenCV (instead of living in the contrib module) because the patent expired and you can now use it for free.

As for blowing up with NN packages and such... I don't really use those parts, but if the NN module had easier support to run networks trained on popular frameworks I might've used it. Disclaimer: it's been quite a while since I last tried to use those parts, so maybe now the latest version has fantastic support and I'm talking nonsense.

Indeed, it's their trademark style. It has also worked great for them.