If domain check fails, make it call a url which sends you an email with the domain name someone is trying to use it on.
If someone is silly enough to upload a stolen/decompiled swf you will get an email with their website address / ip address
Would be fun simple bit of code to put together – I don’t have any flash files on here – so if anyone is interested in trying it out pm me and I’ll see what I can whip up.
But if a swf is decompiled wouldn’t the culprit be able to tell from the code that the file employs domain-locking? An alternative solution is to use non-interactive video demos. They seem to be the most secure method of protecting ones files.
+1 – 1000000
Non-interactive? Worrying too much about something means we do too much of unnecessary works which results nothing. Not implementing simple solutions means we are lazy. The efficient way stays middle.
For me it doesn’t takes more than 10 minutes to secure preview files from direct usage. Secondly we can’t do much about decompiling (if encryption fails) and at the same time, the source files created by that way will not be easy to use. No worries.
I’m talking about lifting the files off the preview, so they just use the SWF and XML and use the files ‘as is’ and add their own content and customise through changing setting in the XML . So a watermark would make the preview unusable.
2. For the preview, just don’t use xml at all. I just add a field array inside the fla which has same content as xml in the source package.
I think together these two steps if implemented would help a lot. However, I wonder if there could be something even easier so all development and creative efforts go into what they are actually meant for “Create great items” that is.
Thought for an additional second and have a suggestion to make. It may sound a bit stupid but giving unconventional names to your preview xml may help as well. They can download the swf but how are they going to get the xml? without actually exporting it into a fla (assuming Envato’s encryption tool prevents this from happening in most cases if not all). Keeping a obvious xml name like config.xml or preview.xml or main.xml just makes it more obvious and easy to download by a simple guess. I want to know if the preview files are renamed or if all file names are kept intact? Anyone??
If someone is silly enough to upload a stolen/decompiled swf you will get an email with their website address / ip addressIt wouldn’t be so easy imho: – for one, I think the guy would test the file locally first (so you’d get only an IP, or “localhost” and an IP) - and if you try loading an external source, you’ll need a crossdomain.xml on your site, otherwise flash player will complain there is a sandbox violation when it will try to access your email script (unless it’s an AIR app, but AD doesn’t sell any afaik).
Also, that applies only to Flash, graphics and movies can’t contain scripts calling home (except maybe photoshop actions or the sort, but that’s another thing).
using complex names for external xml is useless,
just embed all configuration in preview.
i don’t think that watermarking flash item is a good idea.
a less intrusive solution could be a popup window which get
displayed after some time, like
“ACTIVEDEN PREVIEW , CLICK HERE TO CLOSE ”