Hollywood doesn't care who loses, so long as they win.
The electronic manufacturers are playing the same game, as long as they win they don't care who gets screwed.
That's why this proposed legislation would have "all" the industry players get together and hash out a solution agreeable to "all",
which Congress can then pass without getting their hands dirtry. "We just rubber stamped what the experts in the industry said we needed."
This is how they got the DMCA passed; the "all" at the table won't include you.
The DMCA represents the new model for passing legislation of this type.
If you want a seat at the table, you need to speak up now.
If I can come up with a way to maintain an open
SMTP relay on the internet while at the same time
ensuring that SPAM is never relayed, would you
object to my deploying it?
Mail from MIT was not being blocked because it
was SPAM, but rather because the ORBS people
thought MIT might allow SPAM.
Now, think about a certain Russian hacker sitting
in jail, not because he infringed copyright, but
because he created something which might allow
someone to infringe copyright.
Lessig's background is law, and one of the advantages
this provides him is the ability to recognise
bad law in the same way a good programmer can
recognise bad code. This is what he is reacting to in his
article: this little 'war' is an example of how
policies should NOT be created.
Don't underestimate what I will call the resume'
factor.
Why would I recommend a quarter-of-a-million-dollars
for something based on open source when I can
recomend some well marketed and proprietary closed
source solution and add a half-million-dollar project to
my resume without having to explain why I'm doing somthing
different than what the boss was expecting?
Hold on a second. Maybe I don't want my honeypot
patched behind my back?
Or maybe I maintain that vulnerability to support a legacy
application I MUST have, and I've put other devices in place
to avoid exposure.
Whose box is it anyway?
Slashdot Mirror
So, does this mean we're going to federalize
Windows security, and impose a $4-per-boot
surcharge to pay for the additional security
measures?
That's not how the game is played.
Hollywood doesn't care who loses, so long as they win.
The electronic manufacturers are playing the same game, as long as they win they don't care who gets screwed.
That's why this proposed legislation would have "all" the industry players get together and hash out a solution agreeable to "all",
which Congress can then pass without getting their hands dirtry. "We just rubber stamped what the experts in the industry said we needed."
This is how they got the DMCA passed; the "all" at the table won't include you.
The DMCA represents the new model for passing legislation of this type.
If you want a seat at the table, you need to speak up now.
Go re-read the article.
Here's a little thought experiment:
If I can come up with a way to maintain an open
SMTP relay on the internet while at the same time
ensuring that SPAM is never relayed, would you
object to my deploying it?
Mail from MIT was not being blocked because it
was SPAM, but rather because the ORBS people
thought MIT might allow SPAM.
Now, think about a certain Russian hacker sitting
in jail, not because he infringed copyright, but
because he created something which might allow
someone to infringe copyright.
Lessig's background is law, and one of the advantages
this provides him is the ability to recognise
bad law in the same way a good programmer can
recognise bad code. This is what he is reacting to in his
article: this little 'war' is an example of how
policies should NOT be created.
But they said I did it 3 times.
That means I slowed down not once, but twice.
I'm innocent, I tell you.
Don't get your hopes up.
If you want to see how well a Linux version of Office 2000
[B
Don't underestimate what I will call the resume'
factor.
Why would I recommend a quarter-of-a-million-dollars
for something based on open source when I can
recomend some well marketed and proprietary closed
source solution and add a half-million-dollar project to
my resume without having to explain why I'm doing somthing
different than what the boss was expecting?
Hold on a second. Maybe I don't want my honeypot patched behind my back? Or maybe I maintain that vulnerability to support a legacy application I MUST have, and I've put other devices in place to avoid exposure. Whose box is it anyway?