explicitly handle imagemagick exceptions by not attempting to save image

https://www.pivotaltracker.com/n/projects/914728/stories/84945642
https://www.honeybadger.io/projects/3240/faults/9911107

Hm... how would you suggest organizing? And to support what use cases? (like browsing by user, or by level or by script...)

I was thinking of the filenames acting just like a key (the filenames are essentially a hash based on the object type and id, with the plain id appended so we can go backwards). It is pretty much impossible to browse the images from the s3 bucket.

If we wanted to we could 'browse' things from the dashboard side because the references to the images stored there are still attached to the metadata (like the level and the level data). Would it be helpful to duplicate some of it in the S3 directory structure or would it be more helpful to have a browsing UI that could take advantage of the whole data model?