blocks|key|4288671|text|如果一切都是在客户端运行，那么你能做的事情并不多。您可以尝试混淆JavaScript，但这不是一个非常有效的解决方案。您需要做的是以吸引人的方式将其绑定到后端，例如|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4288672|4288673|Highscores|unordered-list-item|4288674|Multiplayer+|4288675|Achievements|4288676|Integration与您的其他游戏|4288677|4288678|通过提供更好的体验，给他们一个回来找你的理由。|4288679|最后，积极寻找并保护你的知识产权。当你发现一个敲诈勒索的网站时，尽你所能关闭它。|4288680|entityMap^0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|T|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|U|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|V|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|W|8|@]|9|@]|A|$]]|$1|J|3|K|5|E|7|X|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|Z|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|10|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|R|$]]

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

<ul>
<li>Highscores</li>
<li>Multiplayer </li>
<li>Achievements</li>
<li>Integration with your other games</li>
</ul>

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.

blocks|key|2822145|text|首先，当您分发应用程序的源代码时，任何有一点技术知识的人都应该能够理解它是如何工作的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2822146|但是，您可以使事情变得更加困难--通常，使用+(这样有意义的变量名，如'hero_score'就会被无意义的变量名，如'a45'__所取代)|offset|length|style|CODE|2822147|对于Javascript代码，请查看|2822148|entityMap^0|0|Z|C|1N|5|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]|$D|P|E|Q|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|K|$]]

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 <a href="https://secure.wikimedia.org/wikipedia/en/wiki/Obfuscated_code" rel="nofollow">Obfuscation</a> (so meaningful variables names, such as <code>'hero_score'</code> are replaced by non-meanningful ones, such as <code>'a45'</code>)

For Javascript code, take a look at the <a href="http://developer.yahoo.com/yui/compressor/" rel="nofollow"><code>YUI Compressor</code></a>

blocks|key|853826|text|确保你的代码中有明确的版权。你不能仅仅依靠技术来赢得这场战斗。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|853827|正如Pascal所说，混淆和压缩你的代码是最好的技术解决方案。|853828|考虑链接到服务器以进行登录或其他操作。像Google+AppEngine这样的东西使得运行一个可伸缩的服务器变得非常容易和便宜。|853829|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Make sure you have a clear copyright in your code. You can't win this fight on technical grounds alone.

Obfuscating and compressing your code is the best technical solution, as Pascal says.

Consider linking to the server for login or something. Something like Google AppEngine makes it really easy and cheap to run a scalable server.

blocks|key|847555|text|我建议添加一个javascript函数来测试它在哪里被播放，然后保护你的代码，在web上你可以找到很多关于混淆/加密javascript的信息。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|847556|编辑:在这种情况下，我会做什么，并且知道窃取/重新编辑javascript，即使是模糊的，也可以做到：|847557|我将有一个服务器端页面来保存文件，一些核心变量将通过服务器端编写。|847558|困难的部分是以一种不能完全用javascript+(没有服务器端)来完成的方式来编程。|847559|然后，也许一些物品也可以通过服务器端构建/放置，这样盗版者就很难重新制作所有的东西。|847560|此外，域检查的脚本可以通过服务器端完成。|847561|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

I suggest adding a javascript function to test where it is behing played, and then protect your code, in the web you can find a lot of info on obfuscating/encrypting javascript.

EDIT: What I would do in this case, and knowing that stealing/re-editing javascript even obfuscated, can be done:

I would have a server-side page to hold the file, and some core variables would be written via the server-side.

The tough part is to programm this in a way that can't be done exclusively in javascript (without the server-side).

Then, maybe some items could be constructed/placed via the server-side also, this way it would be difficult for the pirate to remake everything.

Also, the script for the domain check could be done via the server-side.

blocks|key|506864|text|我发现这个Javascript混淆器是你将得到的最好的保护，它使你的代码完全不可读，它理应缩小它，我做了一个JSPERF，它看起来运行得更快。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|506865|www.javascriptobfuscator.com|506866|506867|+About+-+Free+javascript+Obfuscator是一个专业的Javascript混淆工具。它将JavaScript源代码转换成混乱的、完全不可读的形式，防止它被分析和窃取。|blockquote|506868|506869|506870|输出代码如下所示。|506871|var+_0xe305=["\x48\x65\x6C\x6C\x6F\x20\x57\x6F\x72\x6C\x64\x21","\x0A","\x4F\x4B"
];var+a=_0xe305[0];function+MsgBox(_0xc87ax3){alert(_0xc87ax3%2B_0xe305[1]%2Ba);}
;MsgBox(_0xe305[2]);|code-block|syntax|javascript|506872|只需确保您保留了原始文件的副本:)|506873|entityMap^0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|W|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|X|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|10|8|@]|9|@]|A|$]]|$1|L|3|M|5|N|7|11|8|@]|9|@]|A|$O|P]]|$1|Q|3|R|5|6|7|12|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|13|8|@]|9|@]|A|$]]]|T|$]]

I have found that this Javascript Obfuscator is the best protection you will get, it Makes your code completely unreadable, it supposedly shrinks it, and I have done a JSPERF and it seems to run faster as well.

<h1>www.javascriptobfuscator.com</h1>

<blockquote>
 About - Free Javascript Obfuscator is a professional tool for obfuscation of javascript. It Converts JavaScript source code into scrambled and completely unreadable form, preventing it from analysing and theft.
</blockquote>

The output code looks like this.

<pre><code>var _0xe305=["\x48\x65\x6C\x6C\x6F\x20\x57\x6F\x72\x6C\x64\x21","\x0A","\x4F\x4B"
];var a=_0xe305[0];function MsgBox(_0xc87ax3){alert(_0xc87ax3+_0xe305[1]+a);}
;MsgBox(_0xe305[2]);
</code></pre>

Just make sure you keep a copy of the original :)

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.

HTML5 App Anti-Piracy techniques?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我正在写一个基于HTML5的游戏，作为一个独立的应用程序运行。它是通过web发布的，但没有其他服务器要求--没有数据库等--一切都是“应用内”的。这是设计上的，因为额外的服务器会增加分发成本。既然它只是一个带有很多JavaScript的静态html文件，那么有什么可以阻止用户在他们自己的网站上托管这个文件呢？有什么技术可以帮助缓解这种情况吗？我关心的不是奇怪的用户，而是另一个网站的身份窃取。非额外

问HTML5应用反盗版技术？
EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问HTML5应用反盗版技术？EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问HTML5应用反盗版技术？
EN