Himata is correct, too. After DMA-based stuff, it'll be CPU debugging mode exploits like DCI-OOB, some of which can be made detectable in kernel mode; or, stealthier hypervisors.

In my interactions with distributors, it seems streaming services tend to support up to two genre classifications; though they're pretty outdated and general (even more general and dated than the Winamp genre list). I don't think they use the metadata presented much in the classification; in fact Spotify does its own estimation of 'energy' and other subjective emotions using various classifier algorithms.

Tip: Patterns like “It’s not just X, it’s Y” are a more telltale sign of LLM slop. I assume they probably trained on too much marketing blurb at some point and now it’s stuck.

The RIAA's action there destroyed vast amounts of music, pretty much the equivalent of if someone just aggressively deleted Bandcamp and Soundcloud put together and everything on it because they were upset they didn't control it all. I will never forgive them for that.

(As told to me by Alec, they bruteforced the first bit, but found a very coincidentally attractive one for a backronym among the candidates and chose that.)

They did the first 8 characters of the v3.

Except to be fair, I didn't have a C toolchain, but R3000 assembly language is really nice when you get used to the delay slot.

rnnoise2 is an open-source model that does very well. There also are things like Waves Clarity VX, the Nvidia Broadcast (Audio Effects SDK) too, as well as plenty of other solutions like Supertone Clear, Krisp, etc etc etc.

K-Meleon and so forth was an attempt to take the core Gecko components out of the Mozilla Suite and just have a small simple browser built in it. Having seen that and a few others which had the same kind of idea but were native, Phoenix, which became Firebird, which became Firefox, was... kind of a grassroots disruptive community effort to try the same sort of minimum-viable-product browser thing in XPCOM as a cross-platform experiment, which rapidly gained adoption when people started realising how much faster and better it was to build it that way from the ground up instead. It certainly didn't feel like it was "AOL Time Warner" sponsored. If anything, it felt kind of chaotic. Nobody did a detailed name search because it was an experimental side project.

That worked so well, Thunderbird the email client was forked off too (during the Firebird era), and if I recall Sunbird (the calendar part)?

But to me this feels like a clear-cut case of interoperability, unilaterally and unconditionally removed after the fact of the sale of both millions of consoles and controllers (both first-party and not). Are they sure they want to do that? Now?

This also reminds me very much of Sony's removal of OtherOS in the PS3, and I draw the analogy with what happened to the console's security afterwards very much in mind.

There is a superior, free, open-source alternative called Inochi2D — https://inochi2d.com/ — developed primarily by Luna the Foxgirl, and used by all of nullptr::live, including Asahi Lina (of Asahi Linux fame). It really should see more love because it’s superior in almost every way.

I do appreciate your curiosity, but thank you for understanding. To date, to my knowledge, no-one ever guessed correctly, and maybe that's for the best. If they'd have wanted anyone to know who they were: they'd have said. They never have, and likely never will. I don't think you'll ever see anything from the genesis block or those keys. It's got to feel incredibly strange, yes, but remember: they _wanted_ to walk away from the whole thing, and I feel strongly that deserves respect.

Occasionally, that happened on the same floppy disk, via a horrific sector format interleaving trick invented by Rob Northen (who did a lot of copy protection stuff at the time). Notably, the Future Publishing magazines ST Format and Amiga Format started out as the combined ST/Amiga Format and the "coverdisk" was exactly that - readable by both, with different files on each machine.

Don't use SAE (which is, indeed, an instantiation of Dragonfly). I have a strong suspicion that the way it is used, there will be a practical attack.

I couldn't possibly speculate as to why, but one does feel inclined to agree that the people behind wireless LAN security haven't always generally chosen high quality methods in the past, and this feels to me like it could well be a continuation of that pattern.

I don't know how much (if at all) it might help—but other, similar overlay networks have previously noticed that (intuitively) inefficiency in the transport protocol is likely to be (broadly speaking) multiplied by the number of hops; so any improvements in that might be useful in improving the user experience by using the same available resources more efficiently.

What that might mean for Tor's perceived speed is a somewhat murky issue, as that's a function of the complex interaction of latency and bandwidth and crypto and routing overhead of all the involved nodes in a tunnel put together; which of course is also shared with other tunnels; not to mention it will _also_ be particularly affected by exit node outproxy bandwidth; _and_ any possible packet loss and delay caused by both incidental _and_ deliberate adverse network conditions…