I've written a bunch more on the link (+photos are there), but essentially this uses 2 fingerprinting approaches: - retro-reflectivity of the camera sensor by looking at IR reflections. mixed results here. - wireless traffic (primarily BLE, also looking into BTC and wifi)
For the latter, I'm currently just using an ESP32, and I can consistently detect when the Meta Raybans are 1) pairing, 2) first powered on, 3) (less consistently) when they're taken out of the charging case. When they do detect something, it plays a little jingle next to your ear.
Ideally I want to be able to detect them when they're in use, and not just at boot. I've come across the nRF52840, which seems like it can follow directed BLE traffic beyond the initial broadcast, but from my understanding it would still need to catch the first CONNECT_REQ event regardless. On the bluetooth classic side of things, all the hardware looks really expensive! Any ideas are appreciated. Thanks!
I would like to draw attention to this gem of wit, easily the best I've seen in a long time:
> I think the idea behind this approach is sound (actually it's light)
I also live in a US state that only requires one-party consent to record a conversation, meaning it is fully legal in my state to record any conversation I am a participant in, regardless of the consent of the other participants.
How should this be reconciled?
Not sure if the state laws you're referencing are in reality limited to phone calls, but I strongly dislike unregulated public camera use.
Your vision (no pun intended) is the story of the Black Mirror episode "The entire history of you", IMO from the show's golden age.
edit; I know that surveillance cameras pass this line already, but here they have to be announced with signs. And even when they aren't, to me state or police surveillance is different from potentially everyone stealthily recording me in private or public spaces.
> Sounds dystopian to me
Cameras everywhere just keeps everyone honest, right? Nothing to hide, nothing to fear, right? What's acceptable now will always be acceptable in the future, right? My mind never changes, whose does?
As I mentioned in a sibling comment, I'm not against a visual notification of such recording once the "start saving to storage" button has been pressed. At the same time, I realize that the 60 seconds or so leading up to pressing that button is also often vital (otherwise dashcams wouldn't use a rolling buffer). And in such a situation where audio (or video, in applicable jurisdictions) is being recorded only in volatile memory and overwritten when the buffer is exhausted, I don't think a recording notification should be necessary unless the user has actively engaged non-volatile recording. In that sense, it's similar to the difference between streaming and downloading media. Both are technically the same, but the intention of "streaming" is to download the media and decode it without storing it in a non-volatile fashion.
Look at social media. WE are the ones who surveil ourselves. Yes, the big social media companies process all that data and use it against us, but we are the ones who give the pictures, videos, and words to them. There's really no good way around this either. I put those same things on my blog and they still get scrapped.
So what ends up being the difference? It's not synced to the cloud, but we put it there anyways. Do you really think most people are just going to take the videos and not share them? Do you think most people are just going to run a NAS at home? In an ideal world, yes. But I don't think we're anywhere near that happening. So a good portion of those videos just get put online somewhere and bad actors have access.
Non-volatile recording doesn't really exist. We're on HN and I'd expect most people here to be familiar with how easy it is to download a streamed video. yt-dlp will do that for a lot more than youtube.