jheising
Joined 12 years ago
Joined 12 years ago
If you can tell me where you saw the wrong names for locations I would love to look into it. Thanks!
Other factors like rain could happen in the future.
When I was a kid — back when travelling still felt new and exciting — I would see a plane crossing the early evening sky and try to put myself in it. Not to go anywhere in particular. I just wanted to know what the world looked like from up there, right then, to whoever was sitting by that window.
The feeling was strongest at sunset. I'd be watching a good one from the ground and think about how much better it had to be from up there, above the haze, with the light coming in level. The same sunset from a perspective I couldn't reach.
Travel has lost most of that. Airports, queues, delays: everything wrapped around flying has got steadily worse. But the flying itself hasn't changed. An hour into a clear evening flight, forehead against the glass, looking down at a world you almost never see from that angle, and it is still one of the quietly moving experiences I know.
Stowaway is that part, without the rest of it.
All this attention has maxed out my Google 3D Tiles quota, so the ground textures in ride-along mode are being throttled. Everything else works — sky, aircraft and satellite tracking, sound — it's just the terrain that may come in flat or missing. I'm working on a caching layer and a proper fallback rather than just buying my way out of it, and I'd take suggestions if anyone's solved this before.
Thanks for checking it out!
To answer your questions about the alert code, yes it runs in a sandbox, but we also parse it and take it through a pretty lengthy pre-check process to weed out any code that might cause performance bottlenecks or general security problems.
As for websockets, we actually do support them (well, technically socket.io) but just don't make it very clear in the documentation. If you take a look at our open-source javascript client (https://github.com/buglabs/dweetio-client/blob/master/dweet....) you can see that we're actually using it there.
Hope that helps.
It's something we'll have to fix— maybe an option to turn off SSL for the freeboard, or like you say, create a proxy.
We'll look into it and have a solution soon.