Just like modern cars… I wish there was some kind legislation that would limit phone-home telemetry to emergency service telecommunication frequencies, and be opt-in only. That way any OEM operating under commercial cellular frequencies would thus be unlicensed, and subject to FCC violations and import bans. Like what OnStar was originally pitched as; only auto dialing to 911, and 911 only, if you were unresponsive after airbags deployed. OEM couldn’t use the telecommunication frequencies for anything other than networking with emergency service endpoints on the same VLAN.

Anything recorded by the vehicle would be required to stay on the vehicle due privacy regulations, like the black box recorder for warranted forensic investigations. OTA updates could also be distributed offline for users to download and flash via USB, like any motherboard bios, so transactions would be write only.

What? I’m using neon with Nvidia’s v550 driver right now. I’ll try switching switching to v555 driver as linked in OP via apt once it available through Nvidia’s (compatible) debian repos for Ubuntu.

https://neon.kde.org ? Not sure if it’s received this patch yet, but it ships the latest version of KDE 6.

Are the two Linux devices on the same IP subnet?
Are any of the other KDE connect features working?

It feels like we’re finally, and thankfully, coming full circle. I remember buying my first digital camera in the early 2000s, specifically chosen because it was one of the many that included USB web camera functionality. Aside from downloading the photos on its internal storage, external storage was optional, you could also use the included software to serve as a webcam source.

I can’t remember if it included a microphone, I’m thinking it didn’t. It also ran off on those small stubby film camera batteries, and not off USB power from the cable you connected it to, which was kind of dumb, and made it expensive to use as a webcam. The video quality must have been something around 140p, and any kind of conference call software was garbage back then as well. Yet the premise of a single device having multi-use features was such a no-brainer, given you already had have the PC USB integration to use it as a point and shoot digital camera.

Modern smart phones have such excellent cameras, it felt really odd that you had to use a lot of hacky work arounds and reencoding over network streams to emulate the same functionality that some of the first affordable digital cameras on the market had decades prior. I spend some time looking into weather a custom Linux kernel could be used with Android to emulate the standard USB profile of a UVC camera device, but it’s really nice to hear that this kind of functionality is being pushed through Android mainstream development.

https://github.com/tejado/android-usb-gadget

Guess it only took a pandemic and Apple to showcase the same functionality to spur the core Android development into gear to match feature parity.

I do as well. I really appreciate the information density, key bindings, and optional web UI. Although I found if I leave glance is running for a prolonged amount of time, it has a tendency to crash from some python issue I haven’t dissected yet, as it takes so much time to reproduce.