--- In [email protected], Saifi Khan <[EMAIL PROTECTED]> wrote: > > On Mon, 8 Dec 2008, Jer wrote: > > > I'm working on a website that will allow users to purchase the right > > to view videos on a per video basis. After they pay, they will get unlimited views. > > > > However, I'm concerned about two issues: > > > > 1) Leeching or downloading the FLVs. Is this easy to restrict? > > > > 2) Users passing around the log-ins. > > > > For #2, I'd like to be able to use something like FairPlay to allow > > users to authorize devices (such as their desktop computers and mobile > > devices). Any of them not on the list, wouldn't be able to access the > > page on which the video is located. > > > > So, it's not necessarily restricting the access to the video file. > > It's more about restricting access to the PAGE itself. > > > > I'm thinking that making it difficult for users to download the FLVs > > and adding a feature like FairPlay, I'll be able to restrict pirating > > of these videos. > > > > (Disclaimer: I'm a designer and entrepreneur...not a developer. So, > > I'm investigating if this is possible. And how time-consuming it is to > > build) > > > > Thank you! > > > > Hi Jeremy: > > When you say, FairPlay, guess you are referring to DRM technology by Apple. > > "FairPlay does not affect the ability of the file itself to be > copied. It only manages the decryption of the audio content" > > You can intercept the decrypted output and write a raw AAC file. > > Security by obscurity does not work. Page restricted access can > be and will be worked around. >
Hi Saifi - Thanks for the response. I'm not necessarily needing to protect the video files. They'll be watermarked and have download restriction scripts in the code of the page to reduce piracy. I completely understand that this isn't a surefire way. But it will help. Adult sites have a pay-per-view kind of structure. I just want to add the layer of being able to restrict the view of the actual page to certain devices. So, it's not the media file that I want to restrict. It's the page itself. So, I'm wondering. Can this be done using IP addresses? Or will DHCP screw that up? Are there any other unique identifiers that could be pulled from a user's machine to keep track of it? Unfortunately, advertising is not an option on this site as it is a site built around 1 video presentation (at this point). This video presentation will live forever on this site, so advertising will eventually dry up. In a nutshell, is there a unique identifier that could be added to a user's account on a site that could be used to restrict the viewing of a page or pages of content? Jeremy
