Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Hmm, I was talking about DRM in the context of published information.

Obviously, in the case of private and/or sensitive information, you don't release anything to the public, so I'm not sure the protections (login system, etc...) can still fit in the definition of DRM.

https://en.wikipedia.org/wiki/Digital_rights_management:

    Digital Rights Management (DRM) is a class of technologies that are used by
    hardware manufacturers, publishers, copyright holders, and individuals with
    the intent to control the use of digital content and devices after sale.
With publications, you give an access to other people (a restricted one if DRM is involved). It's not the same as not giving access to anyone but yourself.


The argument of copyright is that 'published' information is not public. It is still owned by its creator (or more often by one of the corporations that employ them), you just get a very limited license to do certain things with it, like reading it and maybe creating personal backups, but not other things, such as sharing it with others, either for free or as part of a commercial venture.

This distinction between owning and licensing information didn't use to be necessary in the publisher's business model for popular culture, because the cost (and, equally importantly, the profit margin) of distribution was significant: authors made and continue to make far less than their publishers, with rare exceptions.

The cost of distribution of digital information is so low that consumers will do it for free (BitTorrent). And since the power of publishers primarily derives from their ability to distribute copies, that is what they attempt to preserve, even though they do a lot of other things that continue to be valuable in today's digital world, like financing and advertising. This (not entirely irrational) attempt to preserve a dated business model is in turn perceived by consumers as a clampdown on their rights, leading to a backlash to the established publishing industry and enabling the (so far limited) success of new services like Spotify and Netflix, which don't have to take into account any reconceived notions of what their business is. People associate licensing an ebook with buying a treebook, but they tend to associate streaming with borrowing a book in the library.


>People associate licensing an ebook with buying a treebook //

People don't just associate it. Companies offer e-books for sale. Amazon says "Kindle Purchase" and give a price for the e-book: that's a subtle sort of fraud if they really mean you can "Kindle license" and to offer a "licensing fee" rather than a price.

Companies want people to think they are purchasing stuff because otherwise people would be reluctant to "buy". Unfortunately the largest companies have been able to play this fraud long enough to establish the system; only now are people realising that what they thought they had bought doesn't technically belong to them and the rights they thought they had are not in place. Like I said, it's a subtle fraud.

What's more egregious is that the copyright deal has been corrupted. With DRM companies are saying their work will not enter the public domain eventually - that means they've failed to uphold their end of the copyright deal ... why then are the demos upholding their end, there is no compulsion to if the contract has already been broken.

There is no protection for works which have been crippled so they can not enter the public domain; the contract has gone. It would be good if the legal system could come in line with the reality of this situation.


Yes, locking private information is not DRM. But if you separate "private" information from "published" information, then for DRM to become [logically] evil, you should restate your claim about why is it evil to prevent unlimited sharing, because the generic "virtual restraints" on bits no longer works.


So, some files on your system likely have read rights but no write rights were I to log in. Is that evil?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: