For example, if you picked a camper van, your next stop may be a gas station (for snacks), after that it may decide to head for an RV-park, then for some natural attraction and so on.
Having 256 people on a call must be a crazy experience, but the app only connects you to other drivers in vicinity, the radius is about 100 km.
The frontend is built with Svelte. This was my first time using the framework and I found their website super helpful: https://svelte.dev/docs
Used Mapbox API and geolib (https://github.com/manuelbieh/geolib/) for building routes and for other geospatial tasks.
"Talkie" was built with simple-peer (https://github.com/feross/simple-peer) and WebRTC. Great tutorial can be found on MDN: https://developer.mozilla.org/en-US/docs/Web/Guide/API/WebRT...
On the backend I use Vercel's serverless functions which are mostly acting as trivial proxies for various open API's.
Feel free to email me if you need more info.
Starting point is always the geographical center of the US near Lebanon, Kansas. The route and general direction are not pre-determined and depend on the vehicle choice. There is no destination really, you can stop at any time.
Available radios change as you progress depending on your location in the game.
>edit: nevermind, I managed to open it after the third try, there must be something wrong on my end lol
Everyone start at the geographical center of the United States in Lebanon, Kansas and later statistically most likely find themselves on one of the coasts. Just because of the overall direction of the highways.
Ended up in Anchorage once. Must say rural Canadian craigslist is wild.