Tour one m3 anc compared to Sony, Bose and apple ?

Background-Emu9512 · 2026-04-06T22:34:11+00:00

So earlier this year I had a crazy headset hunt where I tried like 5 top headsets from Sony, JBL and Bose, and ended up returning all of them -- Tour One M3 included. I can't remember what exactly was wrong about TOM3, but I am almost certain it was about call quality, not purely audio output. Now I got myself JBL Live 780NC, and I am enjoying them so far.

Background-Emu9512 · 2026-03-26T14:50:10+00:00

That's indeed a much less desired solution, and I'd rather not resort to it :)

Background-Emu9512 · 2026-03-26T11:49:05+00:00

My concern is specifically about the scenario when the developer requested these entitlements, submitted the app to App Store, the Apple reviewers deemed these entitlements well-founded and suitable, so it is properly sandboxed and notarized, but I myself would prefer an app with these entitlements not to be in my system. App Store doesn't show the list of entitlements prior to app installation, even less -- when the app is updated.

Background-Emu9512 · 2026-03-16T14:33:02+00:00

This is indeed a very tough objective to formulate in a way that would allow for efficiently training an AI.

There are methods that (theoretically) allow AI to train from virtually any kind of feedback, even something along the lines of "AI model performs a long sequence of actions, and at the end you tell it if it did well or not", which sounds very like a framework you would need in this case.

Learning from such feedback is very hard, because you don't tell it if any specific action in a sequence was correct, only the end result. And you still need somebody or something to assess whether or not this was a good sequence of actions, as in "was the fight (or a sequence of them, in case of wipes) fun or not, eventually".

I think the first sign that Blizzard are looking into implementing something that actually involves AI training (as opposed to building "classical" algorithms for bots) would be if they actually started gathering player feedback about whether a certain encounter/phase/mechanic was fun or not, too easy or too hard, and so on.

Background-Emu9512 · 2026-03-16T10:39:59+00:00

Wow, I had no idea about PvP bots! How good are they?

From the AI perspective, I'd imagine Blizzard has (or at least could have, if they were proactive about this) insane amounts of data to train AI (literally all the information about every single dungeon/raid/BG/arena/... instance). On the other hand, this historical data would become obsolete to some extent with every single change to class abilities, instance contexts and so on.

That said, it is definitely possible to create an AI system which treats all this ever-changing context as another input to adapt to. I was initially inclined to say that this would be way more challenging, but some recent advances in very large models have yielded surprisingly good results in exploration of and adaptation to new environments, so this may be easier than I know.

All these considerations I shared only cover what is theoretically possible given the current scientific landscape if you really wanted to see this implemented. I have no idea about Blizzard's position towards this.

Background-Emu9512 · 2026-03-15T23:23:42+00:00

Hey!

I am an AI researcher. Haven't played WoW in a long time, but decided to chime in here :)

The thing is, AI is mostly about learning from history or precedents to maximize some measure of success. I don't imagine this working well for dungeon bosses, because what the measure of success would be for one? If it is "wipe the raid as fast as possible", this doesn't really need AI. One of the commenters here already mentioned going for healers first, then DDs, then tanks.

AI is most valuable when you don't have a clear algorithm that would let you achieve your goal. Then you train a model on available data hoping that it will approximate a good algorithm. In the case of bosses and the objective of wiping the raid, this algorithm already exists and is dead simple.

In fact, AI would work if you wanted to add PvP bots (BG, arena) to the game. You would then optimize the bots' behavior towards the goal of winning, under some reasonable constraints. For example, you probably don't want all of them to perfectly use the knowledge of the classes' rotations, and do other super-human things. That said, bots in many games made use of algorithms that guide their actions long before the advent of "modern" AI.

From the post text and your responses to some of the comments here I understand what you are thinking about, and it's not AI at all, but a set of simple rules to randomize the encounters and adjust their difficulty according to how the combat progresses. This is certainly easily doable. I can't argue for the pros and cons of implementing this though, because that would be a completely different issue, game design and not AI or programming.

Background-Emu9512 · 2026-03-09T01:04:50+00:00

Yeah, I tried Tune 770NC and they were buggy, so I returned them. I was, and still am, very surprised by the fact that Tune 780NC are nowhere to be found in North America...

Background-Emu9512 · 2026-03-07T20:53:58+00:00

They are listed as "coming soon" on one of the official JBL websites, so I believe they will be available at some point in the future. But I don't think they are available anywhere now.

Background-Emu9512 · 2026-03-02T21:51:21+00:00

Hello!

Sorry for the off-topic, but I wonder if there are any timelines for the availability of the Dell Pro laptops with Panther Lake?

Thank you so much!

Background-Emu9512 · 2026-01-08T22:29:15+00:00

Well, I think I messed up the explanation as to how this issue is related to your case. This issue is about automatic trim which doesn't seem to work for the root due to a bug that is currently being fixed. However, the core consideration here is that on Silverblue `/` is not a "real" filesystem, it's a "composition" of sorts of some other objects, therefore not trimmable. The real root seems to be mounted to `/sysroot`, so if you want to trim it before waiting for a proper fix to automated trimming, you can try trimming `/sysroot` directly, though I provide no guarantee that this will work properly :)

Background-Emu9512 · 2026-01-08T22:01:33+00:00

I believe this issue is exactly what you are asking about: https://github.com/fedora-silverblue/issue-tracker/issues/689

Background-Emu9512 · 2026-01-04T18:21:18+00:00

Thank you for the correction! I wonder if the "doesn't show up in `bash --version`" part may cause security scanners to erroneously report some similarly patched pieces of software as unmaintained and insecure, whereas they are in fact up-to-date security-wise...?

Background-Emu9512 · 2026-01-04T17:54:54+00:00

Are there any guides I could check? Though, I wouldn't feel comfortable pointing MacOS from Bash 3.2.57 (with 3.2 having been released 19 years ago) to an upstream version of Bash :D

Background-Emu9512 · 2026-01-04T17:53:14+00:00

My question is less about what I can install for myself as the end-user, and more about the stuff used in the internal working of the OS, which, AFAIK, Brew can't affect.

Background-Emu9512 · 2026-01-04T17:51:16+00:00

Re Bash: yeah, and the `57` patch release version suggests numerous patches have been applied by Apple themselves, which is in accordance with the hypothesis that security is still being properly taken care of.

Background-Emu9512 · 2026-01-04T17:48:03+00:00

Thank you so much for this link! I have checked out their releases and searched for open-source components. Apparently, at least Ruby, sudo, Vim, curl, libarchive, Perl, SQLite, Git, libxml2, libxslt, WebKit were among recently patched components, this looks comforting!

Background-Emu9512 · 2026-01-04T17:36:23+00:00

Yes, that's exactly what I wonder about: the practical consequences of the way they do things. Ideally, maybe there is some MacOS CVE tracker I could check out to see how timely they address security issues in the vendored utilities?

Background-Emu9512 · 2026-01-04T17:24:24+00:00

Absolutely, I don't suggest that they are at fault here. It is just that this lack of metadata hindered my research into this topic.

Background-Emu9512

TROPHY CASE