Cool to see this, it's a cool in-between step for not having additional wraparound screens or a VR headset.
I used to run a similar software[1] for when I was really into playing F1 racing games. However one of the problems I found was the initial disconnect in your head and eye movement that took some getting used to.
For example, if you want to look left to see an upcoming turn, naturally your eyes move before your head, and your head follows after.
With this software enabled, you have to consciously inverse the process where your head moves a direction, but your eyes still remain looking forward at the screen.
It took a some getting used to and resulting in some dizziness afterwards, but was fun.
I'm somewhat confused to why Google needed to open source the original Pebble source code for this project to exist?
Was it not possible to already create a comparible e-ink screen, long life battery, smart watch without the source code? Is it the pebble branding itself that is important somehow?
And this isn't some esoteric use case used as an excuse. The core need the author has is "export my diagram to SVG and have it render the same in all browsers".
I'm really not sure how you can argue that "AI is great at explaining code snippets" while also acknowledging that it will just give you flat out wrong answers some times.
Either it's good at explaining and is right, or is bad at explaining and is wrong.
Applying the logic of it being "right most of the time" seems really bad for a tool applied to a reference documentation website.
I sincerly hope that they remove this feature and apologise for its integration in the first place.
I don't think a reference website should include any sort of feature that can hallucinate incorrect documentation for you on demand.
It's bad enough that they have to include a disclaimer[1] on their upsell page, which states that the "AI Help" may occassionally return incorrect results.
It feels like of bleak to discourage childish computer tinkering on a website named "Hacker News". Not entirely sure what this says about the direction of this website.
It would be illegal specifically if you _collected and stored_ the IP address information from the phone home requests to process in some form later.
If you simply process the web request, and don't store the IP address then there it no issue.
If you do end up storing IP address in a log somewhere, then simply having the logs deleted in a documented and reasonable timeframe will be enough.
"Documented and reasonable timeframe" is intentionally vague since business requirements are varied, but if you can justify whatever you come up with, then there is no issue.
Simply do not hold onto user data for longer that what is required for the purposes of the user request. That's it.
Imagine, during a war, a missile that has been set to target a city.
The casualties will be many, and random, and innocent, but this is wartime and horrible things happen.
Now, imagine that this missile is set to target the city, but will launch at a random time in the future. The missile may launch during the war, or many years after.
Now it's obvious to me that the missile that lauches at the random point in the future is more evil than the one fired immediately.
It's a poor analogy, but the random missile is how I view landmines.
I think this is less about the casualties of war itself, but the effects of when trying to move on after the war.
If people die due to landmines many years after a ceasefire are they a casualty of the war?
I think landmines represent a physical device that artifically extends the destruction of war in a time that is way after the parties may have agreed to peace. In that sense, the landmine inflicts death on people with no agency. A bomb dropped on a someone has intent and an army responsible for it. A landmine planted decades ago is so divorced from its original intent that any resulting death or injury feels random and injust.
I used to run a similar software[1] for when I was really into playing F1 racing games. However one of the problems I found was the initial disconnect in your head and eye movement that took some getting used to.
For example, if you want to look left to see an upcoming turn, naturally your eyes move before your head, and your head follows after. With this software enabled, you have to consciously inverse the process where your head moves a direction, but your eyes still remain looking forward at the screen.
It took a some getting used to and resulting in some dizziness afterwards, but was fun.
[1]: https://facetracknoir.sourceforge.net/home/default.htm