In the world of animal experiments it's not unheard for a group to publish papers under the name of one person in the group. This person is typically paid danger money to compensate their risk from animal extremists.
Would somebody be prepared to stand up and publish papers written by somebody else to deal with the SDMI extremists? Would we be prepared to pay them danger money?
Another alternative might be to publish under a pseudonym. The Student's T-test is named after the statistician Gossett who published in the name "Student". Student worked for the Guinness brewery, but they didn't allow publication to be associated with the brewery. (The "drink guiness makes you smart" slogan didn't go down well:-)
There are times when you'd rather not have your email forwarded. That's what copyright is all about and in most cases it should deter others from re-distributing private correspondence.
If the server is going to be down for a prolonged period just move the repository to a new machine. All that is required is copying the repository directories to a new machine and configuring an access method on that machine, i.e. pserver, kserver, sshd, etc. There is nothing in the repository itself that is specific to the server. This is a painless process that I've done a few times with projects I've been involved with.
There are variations on this. If the server is lost without warning, set up a local server, import your project(s), and retire the old server or copy diffs when server comes back. This can get ugly real quick.
IMHO, the notion of using email sounds like a complete nightmare. Handling multiple code collisions via email? The basic system with interactive commits and updates is easy to understand and forces users to deal with collisions early.
When / if SDMI is ever deployed people are going to have access to all aspects of the technology. Being able to examine the watermaking and checking binaries, and being able to examine the same stream pre- and post- watermarking, will make the task considerably easier.
Even if it were deployed and not cracked, it's hard to see how it will gain any market share. Traditional formats take a long time to die. Most new music exists on both tape and CD, some is still on vinyl, and there will be a large market for these formats for a long time to come. Music companies use whatever formats offer a viable market. How many of these companies (and artists) will want to go all digital and lose revenue stream from traditional formats? Until then compression schemes that home users can apply are going to be where it's at...
Slashdot Mirror
In the world of animal experiments it's not unheard for a group to publish papers under the name of one person in the group. This person is typically paid danger money to compensate their risk from animal extremists.
Would somebody be prepared to stand up and publish papers written by somebody else to deal with the SDMI extremists? Would we be prepared to pay them danger money?
Another alternative might be to publish under a pseudonym. The Student's T-test is named after the statistician Gossett who published in the name "Student". Student worked for the Guinness brewery, but they didn't allow publication to be associated with the brewery. (The "drink guiness makes you smart" slogan didn't go down well :-)
There are times when you'd rather not have your email forwarded. That's what copyright is all about and in most cases it should deter others from re-distributing private correspondence.
whatiscopyright
is a good overview too.So who want to inform the australian government...
If the server is going to be down for a prolonged period just move the repository to a new machine. All that is required is copying the repository directories to a new machine and configuring an access method on that machine, i.e. pserver, kserver, sshd, etc. There is nothing in the repository itself that is specific to the server. This is a painless process that I've done a few times with projects I've been involved with. There are variations on this. If the server is lost without warning, set up a local server, import your project(s), and retire the old server or copy diffs when server comes back. This can get ugly real quick. IMHO, the notion of using email sounds like a complete nightmare. Handling multiple code collisions via email? The basic system with interactive commits and updates is easy to understand and forces users to deal with collisions early.
When / if SDMI is ever deployed people are going to have access to all aspects of the technology. Being able to examine the watermaking and checking binaries, and being able to examine the same stream pre- and post- watermarking, will make the task considerably easier.
Even if it were deployed and not cracked, it's hard to see how it will gain any market share. Traditional formats take a long time to die. Most new music exists on both tape and CD, some is still on vinyl, and there will be a large market for these formats for a long time to come. Music companies use whatever formats offer a viable market. How many of these companies (and artists) will want to go all digital and lose revenue stream from traditional formats? Until then compression schemes that home users can apply are going to be where it's at...