With that kind of propulsion politically available, I doubt finding workable combinations of mitigation strategies to interstellar medium hazards would be the showstopper. Especially not one to hold us back for time scales that oceans did. Getting humans interested in prioritizing projects like that, to me, is the real headscratcher.

We could put people on Alpha Centauri in 88 years with 50s technology like Project Orion. The really hard part is figuring out a way to make us use the technology we do have for things like that, instead of for bombing each other back to the stone age.

It was a lot later (1300s), but Ibn Battuta seems to have done just that. Guy leaves Morocco and just keeps going on and on, till he ends up in China. Though perhaps even more incredibly he actually does come all the way back. The historicity of his accounts is disputed and maybe only a part of it is true, but even if he only got as far as India, I still find it fascinating to imagine doing at that time.

A random deployment is certainly risky, but no riskier than a random apk. I’d argue the random deployment is less risky because it’s easier to inspect it in the browser and see what it’s doing with your password. But of course both are to avoid. Self-hosting or compiling your own clients if you can, official deployments or releases otherwise.

Sure. Both compiling your own apk or self-hosting are ideal. If you’re not doing either though, the web app is more easily inspectable.

Its less dumb than entering it into a regular app compiled into an apk, which is more opaque (even if it’s also FOSS). Voyager you can host it yourself.

Closed source ones.

Voyager (formerly wefwef) is a self-hostable web app, so it doesn’t have this problem. Of course this only means you can inspect the code you’re running. You still have to able to understand the code to be sure it’s not doing anything malicious.