Whilst perfectionists might appreciate the idea, the difference between a normal round sphere and Earth's spheroid shape wouldn't be noticeable in a desktop-sized globe, to the bare eye. And you could maybe detect mountain ranges by running your fingers on them, but not really by seeing them?
It would be for those of us who like to apply a fairly big caliper to our globes...
> And you could maybe detect mountain ranges by running your fingers on them, but not really by seeing them?
On a 30cm globe, the Everest would peak ~200µm above the globe's average surface (though it would possibly/probably be too small to even represent), the tibetan plateau would be ~100µm above the average surface. It seems detectable[0] but would require a pretty ridiculously smooth globe, I don't think a plastic-and-paper globe would work.
> The smallest pattern that could be distinguished from the non-patterned surface had grooves with a wavelength of 760 nanometres and an amplitude of only 13 nanometres.
You could improve the video if you hold a loupe in front of the camera lens when trying to zoom in for fine detail, like when you were trying to show us a bridge on two pins.
> Be willing Copy & paste private key into application
I understand this is a prototype.
This is a hard boundary for me to cross when you have already stated it is a prototype and there are several vulnerabilities. Because of this, I haven't installed your app to try it out but I did watch the video.
In your video you show two users on a web chat application encrypting their conversation after typing directly into the site's input control. The chat site may have been recording the input you typed in. I think Gmail will do this, for example. How about changing the model so you only type into your app?
Interesting way to use keybase. Still seems to be a bit too much friction for the end-user. I would probably accidentally send the message without encrypting it.
What is your vision of where this could lead? How will you make it easier to use?
One thing I did to test this, is just using a different private key.
> How about changing the model so you only type into your app?
Indeed this is possible, but a bit more work than I was going for.
> What is your vision of where this could lead?
Honestly, my hope is that this triggers some other ideas and/or someone else is willing to work with me. Keybase is pretty awesome, and opens up a ton of options. I personally don't have a ton of bandwidth, and without anyone else being interested, I'll probably do very little.
> How will you make it easier to use?
Keybase has an API endpoint to export your private key. I requested Keybase to explain to me how to use it, because when you hit that endpoint you get a bunch of junk. It turns out only a portion of what is given to you is the private key, the rest is other data. They wouldn't tell me where to parse.
That being said, I hope they will improve that. When they do, it'll be possible to just plugin your keybase username & password and you'll be able to encrypt and decrypt.
> One thing I did to test this, is just using a different private key.
Absolutely. I just don't want to upload another key on keybase and have my correspondents start sending to a different key for me. I didn't think it was worth it to download and recreate the scene in your video of just testing to myself, rather I was thinking about trying it for a week or something.
Are you aware of any similar efforts that I can compare this to?
