

I’m 90% on-board with disliking these, but I can see uses for ‘Augmented Reality’ glasses. I just wish they worked the way they do in Sci-fi and video games.
Lots of interactions we have on our phones could be done hands-free on a HUD
automatic translation of text or voice when traveling navigation/directions and similar guidance, like automatic subway/train maps instant access to biometric data trends like heart rate, glucose levels and more
I’ve also been part of a pilot to get a HUD to provide AR data to a manufacturing operator, showing things like line speed, temperature and other kinds of data they would otherwise have to go to a computer for. This was around the google glass era, though, and the devices were too pricey to justify and the tech wasn’t there yet.
I do think these devices need to be more obvious. We called them glassholes when google was starting this wearable computing trend and people were using them inappropriately; and we’ve seen how any internet-connected camera like Ring and Flock can be abused.
The concept of the personal HUD is useful, but it still needs workshopping to make it socially safe. Also, the ones like the Meta/Rayban glasses are just pervert tools. No AR, just a camera has no value other than creeping.




The OS angle is huge, and worth picking a fight with, but I haven’t seen any coverage over how this goes after developers too.
I think this is an attack on ALL open-source.
These bills are written by people who are clearly or maliciously tech illiterate and don’t understand either the terminology or the practical impacts. And of course it’s wrapped in ‘what about the children?!’
They include definitions like (paraphrasing; not quoting a specific bill, but New York, Colorado and California do this):
And then require both developers and operating system providers to handshake this age verification data or face financial ruin. I think the original intent or appearance of intent is that the store developer needs to do the handshake. I’m not a lawyer, but I can’t imagine these definitions aren’t vague enough that they can’t be weaponized against basically anything software.
I have a github account, and have contributed to “applications”. As I read them, these bills pose a serious threat to me if I continue to do so, as that makes me a “developer” and would need to ensure the things I contribute to are doing age verification – which I don’t want to do.
I think that even outside the surveillance aspect, the chilling effect of devs not publishing applications is the end-goal. Gatekeeping software to the big publishers who have both the capacity to follow the law and the lawyers/pockets to handle a suit. These laws are going to be like the DMCA 1201 language (which had much much more prose wrapped around it and was at least attempting to limit scope), which HAS been weaponized against solo devs trying to make the world better.
I fully expect some suit against multiple github repo owners on Jan 2, 2027.