I've never found it useful that parts after # in url is not sent to server. Now I do, it should never be removed. This is perfect way to add a decryption key as demonstrated.
Awesome! Love the idea and implementation. Are you planning on building more clients around this?
I've been interested in building a private, low-friction photo sharing app for a while, and I might start on one with your server code as the jumping off point.
We're actually not sure what most people use (apart from ShareX) for uploading images, but we're looking to implement functionality into new clients to support Up1 for sure.
That would be awesome! If you run into any trouble, be sure to hit us up in the IRC or throw an issue on Github.
There were no plans to password protect images, but that's a good idea! For now, the post key itself (after the # in the URL) somewhat acts as a password.
Also be sure to check out ShareX at https://github.com/Upload/ShareX , a popular screen-shot tool adapted to work with Up1.
Contributions to the code are always welcome, and we hope you enjoy!