Another Slideshow Player
in
Share your Work
•
2 years ago
http://pages.suddenlink.net/tls/std_applet_sm/
This is an application I am developing with Processing.org for traditional media artists to display their works online with somewhat safer protection/retention of intellectual property. It would/should provide most well known methods for protecting ip rights on public websites. It's best for displaying paintings and drawings on canvas, paper, or other two dimensional media where the vale of the art is as a piece on media for hanging on display where it can be affected by the light and shadows of the environment. The resolution necessary to display artwork in a web browser is nothing approaching the resolution (and corresponding file size) to display as it appears in real life.
When images are displayed through java applet, the entire .jar file is downloaded to the appropriate cache on the viewers machine. Each image shown by this player is stored in one .jar file. From my limited experience, .jar files are even easier than hack than flash files. The images can be extracted. Theoretically, the slideshow could then be re-created by running this open source script on the extracted images to create a new slide show.
I'm not sure, but I believe using signed certificate applets is supposed to be able to allow you to use up to 128bit encryption for packages with fully trusted and signed certificates. That would take some time to hack with dedicated equipment. But, even if you want to limit allowed viewers to hosts with signed certifcates, the images are not encrypted for the hosts with signed certificates.
When displaying original art on the internet, it's always a good idea to watermark your images. It is not necessary to use watermarks that are visible to the naked eye. In fact, some of invisible watermark technologies are better. Virtually any container or package containing images displayed on the world wide-web can be hacked to extract it's contents.
Even still, while processing carries the inherent limitations of .jar contents security, methods such as scrolling text, the use of a magnifying lens to show only part of an image at a time in higher resolution, jigger, caption overlays, barely noticeable distortions, display of copyright information, can convey to the casual viewer the essence of the artwork while leaving a sense that they still need to see the artwork displayed in it's native format.
Design criteria are that it be relatively easy to add images and descriptions, include 'plug and play' style for adding effects classes, and include easy to modify routines for animated text. It should provide watermarking; this script does not read and write watermarks to the digital images distributed in the applet. It should be able to detect whether images have been watermarked so it does not re-watermark them; but this script does not have that ability.
Another Slideshow Player is obviously incomplete without tools to determine whether it is being run under a specific signed security applet. If used as an application, it should have some way to determine if its running on a proper host. It would be nice too if it could delete itself after a specific time period.
For faster display at start up, this app may be a good candidate for processing.js as when running as javascript or html5 because these technologies may allow for the program to start executing draw before all images are downloaded. That could compromise whatever security packaging in applets provides, but, maybe javascript and html5 have better packaging security methods to explore. Processing.pde and libraries have a way to make chunked up .rar files that are read sequentially that should be explored.
On the other hand, it may still be preferable to maintain images of artwork for display on the internet deep in the bowels of some lamp server with https and ssl that only serves one image at a time, as requested by the script or host, rather than providing a package of all images.
I would welcome comments, coding errors (I know there are many), tips for watermarking and protecting intellectual property of images displayed within processing, as well as any offers to purchase originals of the fine artwork displayed.
Also, Credits are due to the authors of 'Magnifying Glass', liquid water, and 'boids'. I've modified these to run as classes. The names were included in the respective codes but I'll try to look them up and include them once this app is finished. I'll be updating the app from time to time at the same address above.
This is an application I am developing with Processing.org for traditional media artists to display their works online with somewhat safer protection/retention of intellectual property. It would/should provide most well known methods for protecting ip rights on public websites. It's best for displaying paintings and drawings on canvas, paper, or other two dimensional media where the vale of the art is as a piece on media for hanging on display where it can be affected by the light and shadows of the environment. The resolution necessary to display artwork in a web browser is nothing approaching the resolution (and corresponding file size) to display as it appears in real life.
When images are displayed through java applet, the entire .jar file is downloaded to the appropriate cache on the viewers machine. Each image shown by this player is stored in one .jar file. From my limited experience, .jar files are even easier than hack than flash files. The images can be extracted. Theoretically, the slideshow could then be re-created by running this open source script on the extracted images to create a new slide show.
I'm not sure, but I believe using signed certificate applets is supposed to be able to allow you to use up to 128bit encryption for packages with fully trusted and signed certificates. That would take some time to hack with dedicated equipment. But, even if you want to limit allowed viewers to hosts with signed certifcates, the images are not encrypted for the hosts with signed certificates.
When displaying original art on the internet, it's always a good idea to watermark your images. It is not necessary to use watermarks that are visible to the naked eye. In fact, some of invisible watermark technologies are better. Virtually any container or package containing images displayed on the world wide-web can be hacked to extract it's contents.
Even still, while processing carries the inherent limitations of .jar contents security, methods such as scrolling text, the use of a magnifying lens to show only part of an image at a time in higher resolution, jigger, caption overlays, barely noticeable distortions, display of copyright information, can convey to the casual viewer the essence of the artwork while leaving a sense that they still need to see the artwork displayed in it's native format.
Design criteria are that it be relatively easy to add images and descriptions, include 'plug and play' style for adding effects classes, and include easy to modify routines for animated text. It should provide watermarking; this script does not read and write watermarks to the digital images distributed in the applet. It should be able to detect whether images have been watermarked so it does not re-watermark them; but this script does not have that ability.
Another Slideshow Player is obviously incomplete without tools to determine whether it is being run under a specific signed security applet. If used as an application, it should have some way to determine if its running on a proper host. It would be nice too if it could delete itself after a specific time period.
For faster display at start up, this app may be a good candidate for processing.js as when running as javascript or html5 because these technologies may allow for the program to start executing draw before all images are downloaded. That could compromise whatever security packaging in applets provides, but, maybe javascript and html5 have better packaging security methods to explore. Processing.pde and libraries have a way to make chunked up .rar files that are read sequentially that should be explored.
On the other hand, it may still be preferable to maintain images of artwork for display on the internet deep in the bowels of some lamp server with https and ssl that only serves one image at a time, as requested by the script or host, rather than providing a package of all images.
I would welcome comments, coding errors (I know there are many), tips for watermarking and protecting intellectual property of images displayed within processing, as well as any offers to purchase originals of the fine artwork displayed.
Also, Credits are due to the authors of 'Magnifying Glass', liquid water, and 'boids'. I've modified these to run as classes. The names were included in the respective codes but I'll try to look them up and include them once this app is finished. I'll be updating the app from time to time at the same address above.