No, it doesn't. You said:
And I was educating you that the app does not communicate with the car.
Except you were, again, wrong.
The app
does communicate with the car.
But like your cell phone, computer, or virtually every other electronic communication in the world, it goes through other devices on the way.
I even explained how- which part was unclear to you?
Yes, it does. Words actually matter. Going through even one intermediary is a vastly different thing than a direct connection, be it one hop or 100 hops.
Then literally
nothing "communicates" other than in person talking.
Your
magic dash cam doesn't communicate with your app either- it
also goes through servers. I even told you who hosts them (it's not the people who make the app or the dash cam)
No need to mansplain to me how networks work. If that's what you meant, then why didn't you say that to begin with?
I think there's pretty clearly a need based on the above. And still seems to be.
you are the one who still seems to incorrectly think your Magic DashCam works any different than these other examples.
Webcams are not the same as dashcams.
Of course they are.
They are
literally both cameras that send digital video from one place to another.
Show me ONE dashcam made 10 or more years ago that sent any video to the cloud. Just ONE.
You realize "the cloud" is just "a server that's located somewhere else" right?
I mean- maybe not given your other posts so far...
But the concept and technology existed long before the marketing term came along.
So... all of them?
BUt sure- here you go-
Yahoo launches live cam site, but can't handle traffic
That's a story. From
ten years ago about Yahoos
live video from webcam service crashing from traffic.
And it mentions 3 or 4
other services that already existed at the time doing the same thing.
So, once again, you are factually wrong.
Are you smoking something, because that's just absolutely not true and your arguments are quickly losing credibility over it.
Except where it is, and I just gave you yet another source directly disproving your misinformation.
No need to be a condescending twit. I didn't say video couldn't be sent over the internet
I mean- you
just said that didn't exist 10 years ago- and it clearly did... so....
, I said that all the SOFTWARE to do that has to be developed on BOTH ENDS to send and receive the video in the formats available and for the requirements specified.
Again- not really.
The car
already does that for crashes.
You'd have to change the conditions under which it sends it, and possibly tweak the stream, but the basic functionality is, once again, something the car
already does
You keep insisting that all the HARDWARE to do this exists, which I agree, it does. BUT NONE OF THE SOFTWARE TO DO IT EXISTS.
Except it does.
The car already knows your location, in software.
The car already knows gforce info, in software.
The car already captures video from the cameras, in software.
The car already uploads that video to cloud servers in certain conditions, in software
The car already makes that video available to view (only to tesla employees right now) in software.
The car already communicates with the owner via the app (again, through servers, since you seem to need that spelled out). In software.
The only thing that needs significant development is a UI- because I'm sure the one they use to view uploaded video now is ugly.
I manage a large AWS infrastructure
Show of hands on anyone who believes that based on your other posts?
Sure, you can spin up as many virtual servers as you wish.. but let me ask you this, genius. Who is going to develop and deploy all the custom SOFTWARE to run on those servers?
Well, not the same guy for one.
Development and deployment are usually different people.
But again since their servers already
do most of these functions you really just need a little integration and a decent UI on top of it.
It continues to not be the rocket science you seem to think it is.
You think there's some pre-packaged AMI out there that does everything and exactly what a Tesla dashcam service needs to do? ALL of that will need to be custom developed.
Except, again, it doesn't.
Most of those pieces
already exist
The car
already does them
You don't seem to be well versed in security, do you?
I mean.... more than you so far...
Just because certain parts of the car have access to the data, doesn't mean it's available to other, less secure parts.
Sure. But we're talking about the end user app.
Which
already has location data
So you don't seem to be familiar with what the car
already does
Again.
And once again, just because the data already exists doesn't mean there is one line of code to integrated it all together into a dashcam product.
In the case of location data- yeah, that's pretty much what it is.
Especially when the car
already uploads video with GPS data to Teslas cloud servers
It does it
now
No "new code" needed
at all to do that.
You seem totally out of your depth regarding what level of software development is required to integrate all these disparate data feeds, hardware components, video feeds, user interfaces, and back-end servers.
I agree one of us does. I just disagree on which one
You make it sound like you could just throw it together over a weekend and spin up a few AWS instances.
A weekend? naah. I could absolutely do it in a month, minus the pretty UI.
I'm more back-end that pretty-UI.
Which is why I mentioned, with some authority, that the rest is pretty trivial.
I'm saying that a Tesla dashcam will NEVER have all of these features working at parity with an advanced dashcam of today.
And you continue to be unable to support what you are saying.