You enter a house / shop / club in SL and in the foyer or living area, BAM, the builder has plopped down a dozen picture frames each rotating through half a dozen pictures. And each picture?
A drag-and-dropped snapshot image.
Now, my resolution is 1024x768, and my snapshots are ... oh, 2.35 megabytes. I imagine most people are running my resolution or higher... let's do the math:
2.35meg x 12 frames x 6 pictures a frame = ...
... 169.2 megs!!!??? 
Oooh, that feels SO good going through my download pipe. /rimshot
And this is just for the snapshots, let alone prims and other textures!
The ideal solution:
In a perfect sim-world, land-owners would download the picture, resize it, compress it to jpeg format, and still have a sharp looking picture for under 50kb, then reimport it for a paltry $10L. It doesn't even need Photoshop - just about any image handler program can resize and save into another format.
But this does remove the ease of use of being able to just drag and drop that snapshot right onto a prim.
My suggestion to LindenLab:
Make a translation algorithm that automatically resizes snapshots into small compressed textures. It could be done on the fly as snapshots are dragged to prims, -OR- simply disallow snapshots from being directly dragged onto prims, and have a small feature added to snapshots to convert them to texture. - Like right clicking a texture, selecting "convert to texture".
I can think of two different ways that you could disallow snapshots from being used on prims: (a) Ban them by type on dropping onto the the prim. (b) Make a maximum texture size, something reasonable, like 500kb. (Heck, for that matter, if you reduced texture sizes, you probably could raise prim limits on land!)
My suggestion means:
(a) Linden Labs is saving serious RL cashola on bandwidth (and possibly data storage, depending if you store textures redundantly).
(b) Load times on many places will go noticeably down.
(c) Average Joe/Jane who doesn't know photo editting can optimize their creations more easily.
(d) Doing a resize and compress algorithm shouldn't be too difficult to do, so you're not diverting very much time to implement this feature.
There will be much rejoicing in the villages....
I'm really tired of having a cable modem and still having to wait a long time for a place to load, because people don't have the will or know-how to optimize their creations.
I believe this suggestion could noticeably cut into this, while saving you folks at LindenLabs bandwidth at the same time.
-Hiro Pendragon
Varney 200,200
