Even if we discount various other confounding factors, and assume in good faith that the 99.98% "accuracy" is somehow meaningful on individual recognition basis one should consider this:

Sainsbury's stores serve millions of customers per week. As per usual, they do not seem to be publishing any current customer amounts themselves, but https://rspo.org/members/3-001... claims "Over 16 million customers visit 740 Sainsbury's stores each week", and that was nearly 20 years ago.

Assuming that figure has any truth in it, it would mean over 160 thousand mis-identifications per year (52 weeks * 16M customers / week * (1 - 0.9998)).

These are exactly the kind of questions that came to my mind too.

Russinovich's post offers scarce details on how it was done. I would be interested if the "AI decompiled" code was compared to actual disassembler output to verify accuracy (or if the model used some external disassembler tool for it? Shrug.)

.. of the largest providers, aka Gmail and MS (Outlook/Hotmail/whatever domains they have). Maybe Protonmail too, if you are lucky.

Microslop has been blocking wide network ranges for a long time, and probably for good reasons too.. The problem is that there are almost no mitigations. My own server ended up on such blocked range some years ago and trying to rectify it was like talking to a stone wall.

Maybe do something about all the scam advertisements on your (Google/Alphabet) platforms. No? Thought so.

Indeed .. https://rust-lang.org/tools/in... .. and many others that just instruct you to "curl | sh".

I would not be surprised if it is for something nefarious like the AI training fad or selling the information. And/or for providing the data to law enforcement at request.

While I generally think Rust (or some other "more secure" language) is better, I do agree very much with the "security guys who happen to like rust" sentiment.

While using Rust can almost inevitably improve a number of other security-related aspects, it does not protect vs. timing and sidechannel attacks that are very important in cryptography. Casual re-implementation of an algorithm might easily reintroduce such issues.

Issues like that might stay buried for a long time, apart from the "three letter agencies" that will most likely do their own private analysis in any case.

The death clock for it is already probably ticking. Gone in a year or few. Investing any time on it would be a waste.

The pessimist in me thinks that if anything is to be learned of past history of Firefox development, the next step after removing a feature from core and into extensions is to deprecate / remove the API(s) this extension relies on to function. Or at least the APIs that enable it to work in a comfortable manner vs. UI experience.

Personally I use RSS feeds of 7 different blogs (wow, blogs still exist?) in order to easily follow when new posts are made. It's not much, but at least I don't have to manually check them out, quick browse through live bookmark menu is enough.

Actually some sources say that it has been in the "North Bridge", e.g. what has been known as "Platform Controller Hub" ( https://en.wikipedia.org/wiki/... ) for some time. For example, see ME references in https://www.intel.com/content/...

However, it is stated in the above Wikipedia article: "Beginning with ultra-low-power Broadwells and continuing with mobile Skylake processors, Intel incorporated the clock, PCI controller, and southbridge IO controllers into the CPU package, eliminating the PCH for a system on a chip (SOC) design." This makes it unclear whether also the ME component has been integrated into the CPU package in SoC style in these newer CPUs (assuming that it has been there in the first place.) ... I sure wish Intel themselves would explain all this. And also state their reasons for pushing this crap.

.. case sensitive filenames by default? :D

Just wondering. I know HFS+ can have case-sensitivity, but not sure if it is on by default. And some people seem to be discouraging that, based on quick googling.

I see that you don't realize that randomizing, etc. just makes your "signature" more unique. And if you give less information, it makes you more unique too.

The best way to be less unique would be to be very average, or at least look like the majority - e.g. probably the average Windows installation with basic fonts, etc. and most common version of Firefox/Chrome (which varies as time goes by).

The first thing that popped out as I glanced through the post was:

And I thought to myself, "slowly? .. well, it's father of Java, after all."

And this surprises you exactly .. how?

TFA and the original source (press release from Forum Nokia, http://blogs.forum.nokia.com/blog/nokia-developer-news/2011/03/25/open-letter-to-developer-community ) reveal that:

And further ..

Finally it is stated:

So there's nothing saying that Nokia will suddenly stop supporting Symbian in 2012. It'll just fade out gradually, and even they don't admit knowing when it will fade out completely.