I feel like the fade-in animation when starting/stopping the simulation takes too long. Also, I think it would be helpful if the currently connected row was highlighted when dragging a pin.

Could allow only the path to the zip bomb for this user agent.

That will work once at most and then quickly get fixed.

Yeah it seems like this team takes a really tough stance on obvious bugs

Are you so sure? :)

I can access the IMU without root on my M4 mac running Sequoia

The sample rate is only ~800hz (probably very difficult/impossible to increase)

The fundamental frequencies of voice are below half that, I think that means you can use it to determine what is said writing it's sensitivity range.

Did you try exporting it in the OpenDocument (.ods) format?

There's lots of noise in the accelerometer readings, even without shaking

On my M4 14-inch MacBook Pro, it looks like there are two accelerometers: One with {"DeviceUsagePage"=0xff00,"DeviceUsage"=3}, and one with {"DeviceUsagePage"=0xff00,"DeviceUsage"=9} - They both identify as Bosch BMI286

Ah, after some testing, it looks like these both refer to the same IMU, DeviceUsage=3 is for the accelerometer and DeviceUsage=9 is for the gyroscope. The serial number is also the same for both.

I've been wondering about this for a while, glad someone's finally managed to access it.

I think it's used for the motion sickness reducing feature in MacOS Tahoe that puts a bunch of dots on your screen that react to motion.

I think there's some sort of motion sickness reducing feature in MacOS Tahoe which would require an accelerometer.