Cool, yeah, that part I know. Not having a problem, just thinking through a suggestion. My suggestion is that you consider the bandwidth savings (if any,) the shift to client side storage, and the added value of providing a system which streams a game runners content into a view window placed underneath transparent layers which constitute the roll20 interface. Currently, you are providing storage space into the library. Each map tile must be uploaded and then displayed on a fixed layer as part of the roll20 system. This presents grid alignment functionality, and necessitates cloud storage per member. If however you placed a streaming embedded layer at the bottom, then layered transparent roll20 functionality over it, you would be streaming from the client and utilizing the same bandwidth levels as something like twitchtv or riot stream. (which may be too costly.I dont know.) Game masters would be able to use robust graphics programs outside roll20, then embed them in a streaming layer, scrolling over them in work windows, while players see streamed versions. Just a suggestion I thought you might want to consider if you haven't already. Obviously bandwidth costs money, if thats the obstacle then telling people to use google hangouts is the solution. Additionally, have you considered creating a product that exists client side, selling that product, then integrating it with google hangouts in a partnership with google that basically allows hangouts to stream that client side application?