Let’s say first that we know (some) users will inevitably agree to let malware compromise their system, no matter the popup or protections

A compromised system that’s transparent:

- Has only one way an executable can be started and, being designed as a “salt flat”, it’s easy to read

- Exposes all I/O and all network requests (to admins), regardless of driver abstractions

In this case, even a young enthusiast can look at a system and immediately see that it’s compromised, remove it’s ability to start or do work, and likely remove it from the system entirely.

The inspiration for this approach is a backlash against the absolute glut of places to hide in current user-focused systems. From multiple startup options, to services, to drivers, and in to the “hidden from the admin” executables that can be compromised it’s an ever-worsening problem that erodes user’s ability to keep their own system secure

It’s not even really the fault of the people who pushed for these setups, it’s a seemingly simple business decision: build it in a way that looks secure, add some black-box process, and tell the overseers that the reason there are no attacks is because it’s bulletproof, and definitely not because no one has really tried

Then, when someone finally turns their attention to you and walks in: fire whoever needs to be fired, patch that specific hole, maybe spend a bunch of money on a different system, assure the overseers that it’s handled, and move on with business as usual

It’s cheaper in the long-run, it makes stockholders happy, it relieves the bosses and their bosses, and for the most part there are “no security holes”.

Until now, of course

My gut says that there are some interesting discoveries waiting around the intersections of frequency of vibration, individual resonant frequency, and duration

I (presumably like the majority) assumed that sleep apnea was at least partially caused by weight gain, but if there is weight gain caused by sleep apnea it’s going to give doctors some new tools

Personally, when I have not slept well and need to be productive in a day, I’m much more likely to want to load up on sugar and unhealthy food

I think it can be summed up as “average CPU utilization, which is the common and intuitive first check doesn’t tell you the real story”

I would also suggest that these are “outdated” measurements as common CPU metrics are really designed for moderately multi-threaded, single-foreground-application on bare metal

To your point, someone who deeply understands the stack already knows these are not the metrics to look at, but this is clearly aimed at people who have not (yet) had to dive deep to figure out a scheduling issue

Why should an LLM even have these types of IDs anywhere in the prediction pipeline?

edit: Personally I don’t think they would take advantage of it, but still worth moving the BTC asap

I think you’re underestimating “average users”. If we talk about the median, then probably you’re right, but if we talk about “the group of people clustered around the average” I think there’s a lot of untapped potential, especially in people who assumed data and programming were unknowable/impossible and have therefore been held back by “good” tools like excel

User clicks on a project, views the details and returns to the same position in the list (including all the expansions via “Show more”)

Personally I don’t think that takes anything away

The AI listens as long as you hold the button, and the device is efficient enough to carry with you 24/7.