Be careful, as they don't really delete the files, only don't show them on the site.<p>Here is an example. I uploaded a picture that was shown here <a href="http://jollyshot.com/Kzg7Xe" rel="nofollow">http://jollyshot.com/Kzg7Xe</a> where you can see that "This photo has expired!" but the image is still accessible here <a href="http://jollyshot.s3.amazonaws.com/media/5e34cc07d5fc6b390c1da16c533da679.jpg" rel="nofollow">http://jollyshot.s3.amazonaws.com/media/5e34cc07d5fc6b390c1d...</a>
I love the ease and simplicity: I've got 3 suggestions.<p>1) Next to the View Count ("3 Views") impliment a feature that keeps track of the number of different IPs that generate those views ("by 2 People"). This is important because it lets you know how many other people have seen the image, not just how many times the page has been reloaded.<p>2) Make it so users can drag and drop an image into whatever page they're on. Even if it's the user page, front page, photo page. Don't make me have to go back to the home page.<p>3) Instead of calling it JollyShot.com you should grab TempShot.com before anyone else does. I think the new name would fit better with the service.
I really like the simplicity and the 'guaranteed to self destruct' feature.<p>But... converting PNGs to JPGs makes it unusable for many many use cases.
There is always <a href="http://imagebin.org/" rel="nofollow">http://imagebin.org/</a> it's basic but has been around since the 90's. I think they get some OG cred in this, yeah?
I think one of the understated and potentially most interesting use cases for this app, is its ability to easily transform another service into an ephemeral photo sharing application. With Jollyshot, my Facebook post, becomes more like a Snapchat.