You're going to get sued in the US if you try to market this thing and require voice input. This is potentially a huge accessibility issue.
You've essentially eliminated (most) people who are deaf and people with speech issues from being able to use your product.
It's a neat idea and the design looks like it could be nice but I can't really get past the first page because I cannot use it (no mic attached to this device and I wouldn't want to grant you permission to it anyway.)
Did you click the create button? It takes you to a page where it specifically mentions stable diffusion and allows you to create your own "vr image" with a prompt.
This is really cool! Thank you for making/posting this. I played around with it for about half an hour to 45 minutes or so. I did manage to break it two or three times but I can't reproduce it reliably yet. I'll provide a proper bug report if I can figure out the exact conditions, but mostly if you go off road and get to the top of a big enough hill and then accelerate down the hill as quickly as you can and crash into a barrier you can sometimes flip yourself over it. When you do, you are no longer tethered to the ground and, instead, kind of hover above it and the road. Sometimes you can slip through the ground and the water, and all other barriers become passable.
Thanks for the kind words! That screenshot looks like the tail-end of the road - the world despawns behind you as you drive, leaving behind this weird-looking trench. That isn't a bug, but it definitely looks like one - the plan is to add a little achievement for driving back that far, so that people will know it's expected behaviour. Don't worry about replicating bugs, or finding exact coordinates; I've been seeing them all stream in on my analytics backend, and they come with all the metadata I need :)
Oh, nice re: the analytics backend. Good thinking! This project has prompted me to dust off some code I was working on a couple years ago, I'm excited to play around with it.
I had a Macbook pro gpu go bad a couple years outside the warranty of the laptop. They replaced the entire thing for me and also noticed a little dent in the case and swapped that out too, I essentially got a new (old) machine handed to me with my hard drive swapped to it.
They clearly mean from one specific event. What one event in the USA has lead to 2 million deaths? You're combining all deaths and treating it as if it were the same thing.
No? Are we in an influenza pandemic or epidemic right now? Again, we're talking about events here.
There have been six of them in the last 140 years with respect to influenza. The Spanish Flu pandemic killed 675k (in the USA, like 50 mil worldwide or something wild like that.)
How long ago was that? There used to be a bug related to that, but disabling iMessage on your device before you switch off would resolve it. Not obvious, I know. I'm unsure if that's still a thing or if I'm even remembering it correctly.
That's definitely a problem. I wasn't claiming it wasn't an issue, I was curious how long ago it happened because I wanted to know if it was the same as the issue I experienced years ago.
I'm genuinely curious how this is an antitrust thing?
Apple phones can send texts and communicate with any other phone on any other network and vice versa. They just don't use iMessage to do so. I can't DM my discord friends from my work Slack, for example.
The SMS fallback experience in iMessage is pretty bad. Some of it may be because SMS is bad itself (the unreliability), but the way iMessage features get downgraded to SMS creates a terrible experience for everyone. Add MMS in the mix and it gets even worse. To be fair this can be ascribed to technical limitations; in Apple's view iMessage works great and it's too bad you're using something crappy like SMS/MMS. But then Apple hasn't put any effort into making the non-iMessage experience better.
As for why it's anti-trust, it's right there in the WSJ article. Apple executives are explicit in the lock-in being useful for their market power.
Also it may have been years ago but I'll never forget the way Apple originally captured phone numbers into iMessage. Once a phone number was registered in to iMessage no Apple system would ever send SMS to it again. That created a major problem if the owner of the number had stopped using Apple phones. They were sued over this lock-in and finally implemented a way to release your number from iMessage jail. It's still kind of awkward though.
I uploaded a private video of a screen recording of me demoing an in-development feature of a website for a client so that I could ask them if that's how they intended it to function. There was no audio.
That video received a strike and was flagged as a scam... before I ever even sent it to the client. YT is ridiculous.
Per-page is pretty common in the legal industry generally. It's a holdover from the paper days, when the provider's costs were more a function of page count than document count.
I was once brought over to a project that used exceptions for flow control, sometimes nested several layers deep. It was a nightmare to debug and untangle.
What's funny to me is their solution is very natural and commonly used in unix. My guess is because signal handling on unix is much more prevalent and brings with it many of the same control flow issues you'd see in exceptions.
You've essentially eliminated (most) people who are deaf and people with speech issues from being able to use your product.
It's a neat idea and the design looks like it could be nice but I can't really get past the first page because I cannot use it (no mic attached to this device and I wouldn't want to grant you permission to it anyway.)