Validate/limit input state #13
Description
Maybe I'm just paranoid, but we might want to consider some sort of validation of the input, or at least a size limitation on the input link. Technically, we're giving free storage to anyone who uses the shortener, as long as their input is valid JSON.
Ideas:
- We could consider placing a reasonable limitation (e.g. 10MB) on the size of the input link.
- We could try to validate the JSON state against some sort of basic neuroglancer schema.
- This would have to be done very carefully, since the neuroglancer state schema evolves over time. We wouldn't want to reject links just because the user as a newer version of neuroglancer than the one we were using when we built the shortener service.