ES-Alexander

Hmm, I think in general that "adding context"/flagging is better captured by #594, but that's a much more involved idea (and isn't just related to video segments). Cockpit's video recording...

Hmm, I don't think I agree with this. Joystick buttons can be made intentionally hard to press accidentally (by physical design), and can also be composite actions already (by software...

May be possible using the [Touch events API](https://developer.mozilla.org/en-US/docs/Web/API/Touch_events), but from an initial read I'm unsure whether it provides access to touch positions relative to the pad, or just something based...

In case it's relevant, there's also the proposed [`GamepadTouch` Interface](https://w3c.github.io/gamepad/extensions.html#gamepadtouch-interface), but I don't believe it has browser support yet either.

While I think it's generally useful for Cockpit to be able to log everything that comes in and goes out (especially MAVLink comms, per #451), this issue in particular should...

Potentially relevant to #1291

My preferred approach for this is for it to be handled in BlueOS / a separate extension/add-on (per bluerobotics/BlueOS#1820), so extensions don't each need to download their own map data....

It would be nice to support proper photo capture for cameras that support it, but I view that as longer term because it requires potentially quite significant MCM changes. For...

> would storing EXIF geo-reference be done top-side or down in the ROV? It could be either, depending on where the snapshots are being captured, and whether they get sent...

In that vein, should we also create widgets for receiving and recording audio, or is that already possible with our existing video player and video recorder widgets?