Doom co-creator defends his code against ZeniMax copying accusations
arstechnica.com
arstechnica.com
Lines like this are why the expert reports from the lawsuit should be public. Carmack would naturally have very unusual computer use patterns.
It's easy to picture him creating an editing tool that accidentally used up almost all available swap space. Or filling up almost all of his drive space with generated textures and immediately deleting them.
That would look like use of obfuscation tools to a mediore expert.
A new feature or bug in a AAA asset pipeline can cause a wipe and rebuild of hundreds of GB of generated data. Compressed textures for multiple platforms, compiled optimized level geometry, platform encoded audio and baked light maps are standard culprits.
[1] http://www.pcgamer.com/zenimax-statement-reveals-john-carmac...
Isn't the standard in the US that one must "prove beyond a reasonable doubt", which seems like a higher standard than "more likely than not"?
However, many (especially people within the industry, so most of HN) disagree, as does the US legal code.
And they shouldn't. A good way to think about the task of a jury is to ask: if I take 100 situations where these facts are present, what conclusion is correct in the plurality of cases? They are not there to speculate about alternative explanations, they are there to pick the explanation that is more likely than the others.
Pretty much nobody in my opinion. From that premise, probability theory says this is a tiny piece of evidence.
Then again, most people are very bad at probability theory.
Destroying evidence is very very very bad.
We all have something to hide.
Do you mean "Most people aren't paranoid enough to be afraid to search for 'secure wipe' after being sued for an unrelated matter"?
Or do you mean "Upon being sued, most peoples immediate reaction would be to search the web about how to destroy evidence"?
My guess would that most people who believe they are innocent would have no interest in destroying evidence, and that most people who considered themselves guilty would have already taken care of hiding the evidence before being sued.
probability theory says this is a tiny piece of evidence.
In which direction? Slightly more likely to be guilty, because why else would the person be searching? Or slightly more likely to be innocent, because any guilty person would know not to search?
That one, but not exactly. It's not just about destroying evidence, but about destroying unrelated stuff such as the porn collection or downloaded movies. Or that "non-commercial" shareware you installed but did not bother to pay just yet. I bet everyone here have a couple such skeletons in their hard drives.
> In which direction?
Frankly, I don't know. I haven't consider how a guilty person would have covered their tracks before hand. I just figured most people would just panic and search for various way of covering their asses, regardless of their guilt.
---
My point was more, while most people would see guilty-looking behaviour as strong evidence of guilt, it is not necessarily so. And in this particular case, I don't think it is.
His search history over the last 10 years has probably included formatting instructions several times.
If he did securely wipe a volume on the drive of a machine he worked on after being notified of the suit, there are literally only four explanations, all of which can be attributed to malice or ignorance:
(1) Malice: he intentionally destroyed evidence. This would be on him.
(2) Ignorance: he was given a retention notice by Facebook's lawyers, but didn't understand it and innocently blew away the volume. This would be on him.
(3) Ignorance: Facebook's lawyers didn't immediately give him a retention notice when the suit started. This would be on Facebook's lawyers.
(4) Ignorance: Facebook assigned the most incompetent IP lawyers imaginable to defend Carmack, and it never occurred to them to issue a retention notice. This would be on Facebook.
This all only applies if Carmack actually did securely reformat a volume on a work machine that was relevant to this case, after being informed of this lawsuit. If that's not true, then there are other possible explanations, and this could in fact be a misrepresentation by ZeniMax.
If you break something, starting over and not doing the same thing is often a vastly better than trying to debug what happened and then fixing it.
PS: And yes, I have had training and been required to deal with data retention issues as a basic part of my job for years.
Now that's unusual for web servers, but client software that gets installed is it's own little world. VM's snapshots are generally better for this, but 3D software can have issues with VM's.
Now, it is best to set aside a relevant machine or HDD etc. But, for example if you buy a new phone and then brows the web on it, then as a basic fact of browsing the web cache files get deleted.
So, if you get such an order. Box up your current machine. Buy a new one, wipe it clean, reinstall from version control that's in no way suspicious. Assuming such things where documented and normal procedure.
PS: I would add, the court of public option may ignore such things. But, the court of law is actually far from stupid.
High up person X, gets that notice and takes it to his boss, and they talk about it. They agree to ignore it and just let the lawyers deal with it. 10 minutes later a lawyer assistant storms in, demands an immediate meeting with the accused and tells gives them a list of 10 things, including data retention, to immediately do. They get started on item 1 on the list, then tell some junior team member to do the remaining 9, and get back to work.
Two days later, lawyer finds out the net result of all this is that several computers in use and under discovery are lost. Several others were used in a manner totally ignoring the order, along with an angry high up VP complaining that complying with this order "effectively shut down the department" (read: inconvenienced a few people involved in the lawsuit). An employee that's due to be interviewed in preparation for testimony in 15 days just took a 14 day leave, another that's on the list of experts left under bad circumstances. And of course, all of this is the fault of the legal department.
Lawyer spends the next 30 minutes under his desk fighting the urge to buy a gun.
Mind if I give people a bit of advice: whilst deleting stuff once it's under discovery is of course very bad practice (it is not simply illegal though, the situation is more complex), limiting the amount of time you hold on to files, mails, chat logs, browser history, ... is a good thing. I would advise no more than 2-3 months unless there's a specific reason. If you're part of a big company, do this especially for your work related files. Oh and of course, whatever mechanism you put in place to do this, needs to be deactivated once you do have a discovery order and reactivated afterwards.
OTOH, that wasn't actual theft, IP or otherwise, just abuse of office materials and computers. Infocom did similar things at MIT in their early days, IIRC.
So this accusation is much more serious than anything that Carmack did when he was founding id.
The expert report is prepared before trial, and explains to the other side what the expert's opinion will be and the basis for that opinion. It is used to help prepare cross-examination when the expert ultimately testifies at trial.
Essentially what's happening here is that there are 2 parties that signed a contact, and then one of the parties violated said contract. The only people involved are those 2 parties (and anyone they hire/ask/... to represent them). Nobody else has a right to know.
"Copyright protection may, however, extend to substantial literary expression—a description, explanation, or illustration, for example—that accompanies a recipe"
To answer your question, then, the reason is that this doctrine only kicks in when the accused infringer had access to the original code.
(I have, in fact, seen cases where it was pretty obvious that someone had just taken code from an SDK or something similar and just changed the variable names.)
Clean room is a way to prove you couldn't possibly have infringed copyright. It is not mandatory.
It sounds like it's not "You made a knockoff, that's 'non-literal copying,'", it's "You made a literal copy, changed a couple of things, and called it yours."
Structure, sequence, and organization of a computer program -- not just code -- is subject to copyright per Whelan v. Jaslow. Note that the Whelan standard became relevant again after Oracle v. Google.
It would be sad if courts accepted a technically ambiguous approach effectively deciding arbitrarily which case is what.
I read this as the following example: So KFC has a secret blend of herbs and spices. If you worked there and stole a bag of the mix and sold it, it is pretty obviously theft. If you gave the recipe to someone else and they used it exactly, it is still theft of the secret as you can reproduce it exactly. Let's say instead that you use 5% less paprika in your mix but all other things are the same. This is a non literal copy but is still fully built on the trade secret.
Just my two cents....
if i > 0 then
non-literal copy:
if index > 0 then