oh lovely, haha

We talked internally about getting rid of these tabs and moving most of this stuff to the right-hand column, but that would make this problem even worse.

Maybe these details should just move to the API -- I don't think they're useful to anyone but the most technical users doing stuff like implementing new storage engines, and making a Conduit call from the web console if you need to double-check a value like this doesn't seem totally unreasonable to me if your hands are already dirty.

Or just say "go look in the database".

I think adding it to conduit is a good compromise; there's very little that's useful in the UI, and if anyone complains about something it should be easy enough to pin just using file.info. file.info already is very short anyway, so adding a fileHandle field should be relatively kosher, I think.

Actually, now that I think about it, the chunked representation overlays the underlying object storage system, so file.info by itself isn't enough - it needs to also extend file.querychunks.

Actually, now that I think about it, the chunked representation overlays the underlying object storage system, so file.info by itself isn't enough - it needs to also extend file.querychunks.