[consulting] Copy Protection/DRM approach

[lapurd at gmail.com]

Don't we all hate to deal with "silly" clients (I use term "silly" just 
to be polite) and "silly" requests of "silly" clients.
Unfortunately, most of us have to deal with that from time to time. 
Don't forget, if all clients will be very smart, then most of them will 
do they web sites by themselves.
So, paradox is that more "silly" clients produce more jobs.
I hate to acknowledge this paradox but it is true.
;P


Matt Chapman wrote:
> Larry Garfield wrote:
>   
>> Printing: Go to your users' computers and unplug their printers.
>>
>> Screenshots: Hack into your users' computers and hack their OS to disable that 
>> feature.
>>
>> As for your client, he needs to be banned from using the Internet until he 
>> gets a clue that it's no longer the 1800s.  Hell, Xerox machines have been 
>> around forever and they allow all sorts of duplication of physical books.  
>>   
>>     
> Xerox machines are exactly the loop hole you've forgotten. Once we've 
> unplugged their printer and hacked out their screenshots, they can 
> simply place their monitor faced down on the xerox machine and hit 'copy.'
>
> What you'll need to do is run the site on a single computer in a locked 
> room that is not connected to the internet, and charge people an 
> admission fee. Don't forget to check their pockets for camera phones, 
> pencils, and silly putty.
>
> Speaking of silly...
>
> -Matt
>
>
>   
>> On Sunday 11 October 2009 3:47:23 pm Cameron Eagans wrote:
>>   
>>     
>>> I have a client that is requesting a sort of DRM/Copy protection scheme for
>>> his website. The site will be an educational site for medical students to
>>> help them prepare for an exam for their field of work, and access to the
>>> site will be granted on a subscription basis. The client is requesting
>>> something that I don't know how to do:  prevent getting the content out of
>>> the site in any way. He wants to disable copy/paste, printing, screenshots,
>>> etc. I'm reasonably certain that there is no foolproof method of doing
>>> this. Does anyone have a method of preventing users from copying website
>>> content and sharing it?
>>>
>>> (for the record, I don't support this approach -- I'm more partial to the
>>> 'Don't copy our stuff or we'll sue the crap out of you' approach. The
>>> client is asking for it though, so I have to at least make an effort =D )
>>>
>>> Thanks in advance!
>>> -----
>>> Cameron Eagans
>>> Owner, Black Storms Studios, LLC
>>> http://www.blackstormsstudios.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/consulting/attachments/20091011/fa2820fc/attachment.html