内容水印
我们有仅限会员的付费内容，这些内容经常在未经我们许可的情况下被复制和重新发布。
我们试图通过将每个客户的用户 ID 包含在一个假的 css 类中来为我们的内容添加“水印”，例如
（当然，除非不那么明显:) ，这将帮助我们跟踪复制的来源，然后我们将该类放置在文章正文中的某个位置。
问题是，通过将特定于用户的信息包含到文章中，会导致文章内容不符合缓存条件，因为它现在对于每个用户来说都是唯一的。
这将每个文章页面浏览的页面加载时间从约 0.8 毫秒缩短到约 2.5 秒。
有谁知道仍然可以与缓存一起使用的任何水印策略？
或者，可以采取什么措施来加快数据库访问速度？ （哈哈，我确信这只是一个小主题。）
我们正在使用 CMS 表达式引擎，但我想听听任何策略。 它们不必是特定于 EE 的。
We have members-only paid content that is frequently copied and republished without our permission.
We are trying to ‘watermark’ our content by including each customer’s user id in a fake css class, for example <p class='userid_1234'> (except not so obivous, of course :), that would help us track the source of the copying, and then we place that class somewhere in the article body.
The problem is, by including user-specific information into an article, it makes it so that the article content is ineligible for caching because it is now unique to each user.
This bumps the page load time from ~.8ms to ~2.5sec for each article page view.
Does anyone know of any watermarking strategies that can still be used with caching?
Alternatively, what can be done to speed up database access? ( ha, ha, that there’s just a tiny topic i’m sure.. )
We're using the CMS Expression Engine, but I'd like to hear about any strategies. They don't have to be EE-specific.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
是什么让你认为在某些东西中添加 CSS 会阻止人们在没有 CSS 的情况下复制它？ 更有可能的是，他们只是处理您向他们展示的内容的来源，而忽略了围绕它的所有样式。 例如，我使用篡改数据查看 Firefox 发出的所有 HTTP 请求，如果我可以在页面上看到它，我就可以在日志中看到它。 即使一些网站试图采取所有“保护”措施，它们通常也永远不会起作用。 我可以抓取我想要的内容，而无需使用任何屏幕捕获/录制。
例如，如果您提供 flv，即使您用一些 CSS 覆盖它，我也可以轻松获取其源代码。 我认为最好的方法是让网站发布您的优质内容并要求他们将其删除。 它要么是这样，要么是在将实际内容发送到浏览器时动态添加水印。
What makes you think adding css to something is going to stop people from copying it without that CSS? It's more likely that they are just coping the source of the content you are showing them and ignoring all the styling around it. For example, I use tamper data to look at all HTTP requests made by Firefox, if I can see it on the page, I can see it in the logs. Even with all the "protection" some sites try to put in place, they generally will never work. I can grab what I want, without using any screen capture/recording.
If you were serving flv's, for example, I would easily be able to grab the source of that even if you overlayed it with some CSS. I think the best approach would be to get the sites publishing your premium content and ask them to remove it. It's either that or watermark the actual content on the fly while sending it to the browser.
如果您谈论的是图像，那么您可以使用 PHP 向图像添加水印。
如何添加像水印一样将图像放到 PHP 中的图像上
根据您的上述评论，您对用户复制您的内容感到满意，只是没有格式化等。所以您可以做的是为用户提供该特定内容的嵌入类型源代码，就像 YouTube 所做的那样视频。 在该嵌入源代码中，您可以将自己的链接添加回您的网站，利用您自己的 CSS 等。
这样，您仍然可以允许成员使用内容，但它总是会按照您预期的方式显示，并提供返回您网站的链接。地点。
谢谢
If you're talking about images then you could use PHP to add a watermark to the images.
How can I add an image onto an image in PHP like a watermark
Going by your above comment you are happy with users copying your content, just not without the formatting etc. So what you could do is provide the users an embed type of source code for that particular content just like YouTube does with videos. Into that embed source code you could add your own links back to your site, utilize your own CSS etc.
That way you can still allow the members to use the content but it will always come out the way you intended it with links back to your site.
Thanks
您始终可以缓存使用特殊字符串（例如 #!username!#）的版本，然后根据正在查看的用户使用 PHP 填充它。
我认为的另一种方法是从服务器上的缓存切换到让浏览器在本地缓存一点。 这样，它仅针对每个用户进行缓存，并且减少了对数据库的调用。 因为文章是相当静态的，所以您可以让本地计算机缓存它，并通过 JavaScript 提取评论。
最后一个可能不是你真正想要的，但无论如何我还是要站出来说出来。 你不能像对待小偷一样对待你的用户，而应该像对待小偷一样对待小偷。 找到托管您的内容的服务器的人，并向他们发送一封电子邮件，告诉他们未经您的许可，他们的服务器上托管了受版权保护的优质内容。 您甚至可以自动化该过程。
如何找出哪些网站发布了您的内容？ 在正文内容中添加指向您网站的链接，然后通过 Google 搜索/博客搜索链接到该网站的文章。 要使其自动化，请使用 Google 博客搜索，因为它提供 RSS 源。 任何有链接返回您网站的人都可以进入带有该页面链接的数据库，有人可以查看它，如果是整篇文章，请进行 Whois 并向他们发送电子邮件。
You could always cache a version that uses a special string, like #!username!#, and then later fill it in with PHP based on which user is viewing it.
Another way I believe is to switch from caching on the server to instead let the browser cache it locally for a little. That way it is only cached per user, and it reduces the calls to your database. Because an article is pretty static, you could just let the local computer cache it, and pull in comments via javascript.
This last one is probably not one you are really looking for, but I'm gonna come out and say it anyway. You could not treat your users like thieves, and instead treat the thieves as thieves. Go to the person hosting the servers your content is on and send them an email telling them copyrighted premium content is being hosted on their servers without your permission. You can even automate that process.
How to find out what sites are posting your content? Put a link in the body content to your site, and do a Google Search/Blog Search for articles linking to that site. To automate it, use Google Blog Search because it offers RSS feeds. Any one that has a link back to your site could go into a database with a link to the page, someone could look at it, and if it is the entire article, go do a Whois and send them an email.