This is equivalent to saying ‘guns don’t kill people, people kill people’ which is a way of implying you shouldn’t regulate the tool. The tool matters, and how its positioned and what it’s given access to do matters.

Plus, speaking as an OSS maintainer for some rather large libraries… Its obvious. You can also just close MRs and if the user comments and engages in meaningful discussion you reopen. Cost of a wrong decision is low.

Can you let us know what happens when you connect the keyboard? Also potentially the model of the keyboard.

I think it's more that a ton of popular python libraries (things like pandas, tensor, etc) are actually built in C, so python is just C wearing a mask

It sounds like this isn't E2EE based on the article - there has been no papers published, and the verbiage in privacy agreements still states Twitter can decrypt your messages as needed. That indicates this is functionally similar to the old messages.

Not quite - batteries have something called self-discharge, which happens faster at higher temps. If you're actively using the deck, it can get warm which speeds up this process. It's not fast, but it's absolutely possible to see depending on how long you leave the deck docked