There does not appear to be any limit (other than that imposed by the web.config httpRuntime node) as to the filesize of photos which may be uploaded as a journal entry attachment. Nor does it appear (in CTP2) that uploaded photos are resized. For example, with the httpRuntime node setting a default maxRequestLength="8192" I successfully uploaded 25 jpg files each having a resolution of 2592x3872 and a file size of just under 8 MB. After clearing the browser cache I revisited the journal page and noted (on localhost) that it too nearly a minute for the page to finish loading. Examining the requests or checking the properties of the displayed images shows that the uploaded files are not getting resized but simply reduced in display area to fix each <img > tag's inline height and width.

Most non-profit organization websites which I design are configured with a maxRequestLength of 40 MB to allow for upload of large mp3 files using the repository module. Without an an admin imposed filesize limit on journal photo and file uploads and without automatic resizing of image files (preferably a thumbnail and preview image) to an admin imposed maximum resolution, I am concerned that the Journal will quickly become unresponsive - let alone quickly fill up the file system.

Hopefully this will be addressed in the final release. It is encouraging that I see in the CTP2 source that there are now core API image re-sizeing utilities available.