Journal: 2008-02-02

Two topics for today: DRM and Bresenham's algorith.

(Actually, I'll talk about Bresenham later to keep it on a separte page.)

˜ ™

First, DRM.

I read an article a couple of days ago where the author claimed that the music companies giving up DRM on music is a bad idea and will further hurt the music industry. I think he's probably right. I think DRM is actually really important. I think we really need a strong DRM infrastructure. The problem is that music is a terrible place to start working on the DRM problem.

You want to know why we need DRM? Well, let's see, has any company lost its credit card database this week? Anyone stolen a laptop full of social security numbers they weren't even supposed to have in the first place? If you want consumers to care about DRM, you should use it to protect information consumers care about protecting! DRM should be used to protect your bank statements, your medical records, your social securiy number, your credit card number.

If the music industry cared about protecting your credit card number as much as they cared about protecting their song, we'd be much better off. It's exactly the same: here we have a piece of digital information that we want to securely give a copy to another person such that only that person can access it and no one else. No one else should be able to read the original data. No one should be able to make a readable copy of the data. If the companies that use this data find the DRM too onerous, maybe we'll finally get better DRM.

I was starting to work on a wishlist of features for a good DRM system. I'll put down my thoughts, but DRM is hard. I can already see cases where putting two features together allows you to defeat the system. That's why we need people working on this seriously and not distributing root kits that crash your computer.

I wonder how many other people lay awake at night and think about these things?

[ < Prev | Calendar | Next > ]
C o m m e n t s :    
(nothing yet)
Edit