Generic Openpilot out of the box is just super nice cruise control right now. So it can do longitudinal and latitudinal control. So it lane keeps, stays behind the car in front of you, etc.
If you use Sunnypilot or one of the other friendly forks, you can do more, but it's not (currently) to the state of Tesla's FSD.
Personally, I recommend buying it if you do a lot of road trips. It's amazing for that. In/around town it's only useful if you have a lot of stop and go traffic, like if you live in LA or other large car-centric city with a big commute.
What we do is range types for when a row applies or not, so we get history, and then for 'immutability' we have 2 audit systems, one in-database as row triggers that keeps an on-line copy of what's changed and by who. This also gives us built-in undo for everything. Some mistake happens, we can just undo the change easy peasy. The audit log captures the undo as well of course, so we keep that history as well.
Then we also do an "off-line" copy, via PG logs, that get shipped off the main database into archival storage.
The docs lead to a 403, but I'd be curious to know how it is simpler. I believe the Phoenix version uses Erlang iolists and immutability to make diffing more efficient, and perhaps the Django version has something similar?
Yeah, so many places ask for phone number that don't really need it that I assume the phone number is a unique identifier used to combine individual's data across websites.
Most of the time I use a made-up 555 number or if it needs to send an SMS to verify, I'll use a free SMS numbers.
Mostly only because Tesla doesn't share this data outside of Tesla, unless they leak it to news outlets to make it look like the accident was all your fault and not Tesla's.
Tesla tends to only leak that stuff when they look bad. It's not like they are necessarily outright lying, they are just telling their version of the truth....
VRR is Variable refresh rates, so if there is nothing going on in the content, they can bring the refresh rate down and save processing, thermal issues and energy. If there is a lot going on(say a game), they can ramp the refresh rate back up super high.
There are a few different "standards" around VRR, not every device supports all of them.
Their explanation of the reason for VRR is bad. The primary reason people want it is gaming where the game is not locked to a specific frame rate. Without VRR, the timing of a frame being delivered isn't necessarily going to match when the display is expecting a new frame. This leads to one of two effects. Either the display is forced to hold an old frame for longer and pick up the new frame on the next refresh cycle, which creates stutter. Or the display switches which frame its using partway through the refresh cycle, which creates a visual tear in the image.
If you use Sunnypilot or one of the other friendly forks, you can do more, but it's not (currently) to the state of Tesla's FSD.
Personally, I recommend buying it if you do a lot of road trips. It's amazing for that. In/around town it's only useful if you have a lot of stop and go traffic, like if you live in LA or other large car-centric city with a big commute.
reply