Menu
I'm writing an HTML5 based game that runs as a stand-alone application. It is distributed via the web, but there are no other server requirements—no database, etc.—everything is "in-app". This is by design since additional servers would raise the cost of distribution.
So given that it's just a static html file with a lot of JavaScript, what's to keep someone from hosting the file on their own site? Are there any techniques that can be used to help mitigate this?
My concern is not the odd user, it's the identity theft committed by the other site. Non-additional server solutions would be preferred, but any ideas would be appreciated.
767
The Anti-Piracy Screen is a normally unused screen from Super Mario 64 that was supposed to be shown when an individual plays a pirated copy of the game. In the base game, this screen is disabled from appearing in the game, regardless of what type of copy of it is.
Remove the Incentive One of the most-effective ways of dealing with piracy is by removing the incentive for the consumers to look for pirated content. Effectively this can be characterised by offering a good product and a good user experience at a fair price. There are several different interpretations of this.
Anti-Piracy is a service that can monitor and take down unlawful online distribution such as web, social media, and P2P sites for content that has been registered by the customers of that anti-piracy software. Anti-Piracy can also alert consumers when it finds illegal online distribution.
Google has joined other industry leaders in the “follow the money” approach to fight online piracy by ejecting infringing sites from Google's advertising services and promoting industry-wide advertising standards through groups like the Coalition for Better Ads.
There's not a whole lot you can do if everything is run client side. You can try obfuscating the JavaScript but that's not a very effective solution. What you need to do is tie it to the backend in appealing ways, such as
Give them a reason to come back to you by providing a superior experience.
Finally actively seek out and protect your intellectual property. When you find a site that is ripping you off, do everything in your power to shut it down.
142
First of all, as you are distributing the source-code of your application, any one who has a bit of technical knowledge should be able to understand how it works.
But you can make things harder -- typically, using Obfuscation (so meaningful variables names, such as 'hero_score' are replaced by non-meanningful ones, such as 'a45')
For Javascript code, take a look at the YUI Compressor
39
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
