Tech Paysite protection still a thing?

[blogsy]

What are folks doing / using to protect their pay sites atm for password sharing and content leeching?

[TheLegacy]

as far as content I have a specialized program that embeds coding to your site and also SEO meta the picture. Easy to find stolen pictures and prove they are yours.

[cerulean]

I've developed login management software named LoginBlue, which solves part of this problem. It integrates quite painlessly with existing paysites and other content protection schemes.

It uses (currently email based) two-factor authentication to prevent password sharing, among a variety of other features that help reduce your costs (and in some cases, increase your profits.) It was specifically designed by webmasters with their direct input and is actively being developed. I just released an update a few weeks ago, actually.

You can read more about it in the Announcements forum, here:

https://gfy.com/announcements/137986...rotection.html

Or you can click on the link in my signature, if you'd like. I have a website setup with a FAQ, screenshots of the application, and more information about how it helps protect your content.

If anyone has questions, I would be more than happy to answer them.

For other forms of content protection, there are a variety of tools and firms I've worked with that can help identify and reduce piracy. My clients have been generally happy with these implementations, but they can be costly.

To track users who download your content, I employ a video fingerprinting and transcoding firm, who has developed an imperceptible watermark that can withstand a good deal of manipulation. It pairs a video download (through their CDN) to a specific tag, in most cases, a username. Downloads are instantaneous and the fingerprint is unique per download. No complaints from users about speeds. It's brilliant. Even if a user edits the video through compressing, cropping, cutting, or flipping/reversing, in most cases it can still detect who downloaded the original copy. I've used it to weed out and shut down compromised accounts with multiple clients.

To reduce the amount of uploaded content to fairly legitimate video sharing sites, there are a handful of firms I've worked with who have a service that reads your original video file, makes a fingerprint, and then goes through tube APIs to request removal of unauthorized uploads.

Finally, I have also worked with a DMCA organization who uses a similar fingerprinting service, and then employs a sophisticated bot system to seek out unauthorized piracy links, and then issues DMCAs to both the pirate website and Google to get the links delisted.

The combination of all of these things have been quite effective, but there is no way to attain 100% prevention of piracy.

I am not 100% sure these firms want to be advertised, so if anyone wants an introduction or needs consultation on an integration or game plan, just DM me or send me an email through my signature.

Originally Posted by TheLegacy

as far as content I have a specialized program that embeds coding to your site and also SEO meta the picture. Easy to find stolen pictures and prove they are yours.

I would love to know more about your stenography system if you would be willing to share. It's on my list of features I want to include in LoginBlue. What language is it written in? Does it crawl sites or just embeds a fingerprint into the content? No worries if you aren't comfortable sharing, I'm just a geek with this stuff.

[BunnySys]

In our solution, we block compromised credentials where the number of IP changes exceeds the set limit within a specific time frame. A similar algorithm can also be applied to geolocation based on IP.

[CurrentlySober]

Just make your paysite wear a condom...

[CaptainHowdy]

Originally Posted by CurrentlySober

Just make your paysite wear a condom...

Paysite subscriptions should carefully wash their hands before logging in as well . . .

[zerovic]

well, i usually log ips and attach them to the usernames. if the ip changes constantly, i simply lock the account and send out an email for a verification.. simple and easy. With this, the limit is the sky, for example, use geo location, so if the user is originally from Germany, and it suddenly logs in from the US, lock the account immediately. you don't want to get annoying with locking, but there are different scenarios which clearly shows if an account is leaked or not. I also do web searches from time to time to see if any of my users have their credentials leaked. if so, I do the locking manually and contact the users directly.