There is a health app that is very important to sufferers of a specific disease and it is freemium and I find this detestable. I am doing a clean room rewrite of it in its entirety and plan to release it on fdroid. Is there a license that prevents some ghoul from forking it to profit from people’s misfortunes? I am trying to avoid legal issues by being clean room but will try to keep my publishing of the app as anonymous as possible regardless. Thanks
Some folks are saying that decompiling violates copyright law. I can’t speak to any jurisdictions other than the U.S… (And for that matter, IANAL and this isn’t legal advice, so really I can’t speak with any authority to U.S. copyright law. I’ve read a bit on the topic, but that’s the most I can say.) But I think that’s at best an oversimplification.
A court case that dealt fairly directly with the question of whether decompiling violates copyright law was Sega v. Accolade. Just to hedge further, court cases are very fact specific and a lot of caution should be exercised when applying that ruling to a different case. Also, it’s possible that in the future, a court could simply overturn the previous ruling. However, in that case, the courts found that:
(Yes, it uses the term “disassembly” there, but the Wikipedia page appears to interpret that to include decompilation. As the Wikipedia page says: “Accolade’s decompilation of the Sega software constituted fair use.”)
All that is not necessarily to say that “decompiling is legal”. There are other parts of law which in one specific circumstance or another might make decompilation “illegal”. For instance, an EULA might forbid decompilation. (A lot of EULA’s do just that.)
So, I guess the moral of the story is: to find out whether decompilation is legal or not in a given case, seek legal advice from a lawyer.
Sorry that didn’t really speak to your actual question, but I believe the folks who are saying that what you’re describing couldn’t qualify as an Open Source license are correct.
“disassembly” is pretty much a synonym with “decompiling”.
I think the ambiguity is in the extent of “the only way to gain access to the ideas and functional elements” (are we sure there’s no other way to re-implement the ideas behind the software without dissasembling it?) and what counts as a “legitimate reason for seeking such access”.
Yeah, for sure there’s a lot of complexity in evaluating the specific case at issue.
The “the only way to gain access to the ideas and functional elements” bit kindof goes back to the legal theory that copyright gives protections to “expression”, not “ideas”. (For instance, Baker v. Selden. To oversimplify, Selden came up with an original way to do bookkeeping and wrote a book about it, Baker learned the method from Selden’s book and wrote his own book about the same method, and Selden sued Baker. The courts said that since all Baker “copied” was the “ideas” and not the “expression”, there was no copyright infringement, so Selden didn’t get any damages or anything.) And “functional elements” basically count as “ideas” more than “expression”. So, they’re kindof saying that (again, oversimplifying, IANAL, seek legal council, etc) if your method of keeping people from understanding your algorithms is just the difficulty barrier involved in decompiling, then copyright won’t say that decompiling isn’t allowed. Which is still open to a lot of interpretation, don’t get me wrong.
The “legitimate reason for seeking such access” in this case was understanding the Sega Genesis scheme for preventing unlicensed games from working on their systems and the algorithms involved. Accolade did that specifically in order to defeat Sega’s “DRM” and create games that would run on the Genesis.
Of course, that was before the DMCA, which… who knows how Genesis v. Accolade would have gone had the DMCA “circumvention” thing been in the mix. It probably would have to have been considered, but who knows if it would have changed the actual ruling.
Anyway. Yeah. This stuff fascinates me.
My knowledge basically comes from reading through that whole IP caselaw textbook that I linked in my previous comment. But it’s cool to have a little insight into some of the legal theory involved in such things as copyright licenses and such.
IANAL either, but even under that interpretation (which I think it’s similar to what I said), I see it can be problematic still.
It implies that one would need to demonstrate in court that “your method of keeping people from understanding your algorithms is just the difficulty barrier involved in decompiling”. Because if it is not (lets say… you are openly offering documentation / help / manuals for your software describing the ideas, without detailing how those ideas are expressed in the software), then you might be able to successfully make the case that decompiling the protected “expression” of the ideas was not necessary to access those ideas. And so it might no longer be true that “copyright won’t say that decompiling isn’t allowed”.
Yeah, I don’t mean to imply otherwise. My point was basically just that decompilation qualifies as fair use in some cases.
Sure. I could see some counterarguments that might be persuasive, though.
(I could also see the argument, however, that the first ruling was in error because automated decompiling makes a copy in the same way as translating a novel to another human language makes a copy. So, yeah. Definitely dicey territory legally. But may main point is just that it’s definitely incorrect to blanket statement that “decompiling is copyright infringement”. And the fact that it was found to be fair use even in one specific circumstance really makes it feel like a neat legal loophole. Just like how recipes or fashion designs or car designs or board game rules aren’t covered by copyright.)
All that said, if the documentation is so comprehensive that decompiling the code isn’t necessary, then… why would one want/need to decompile it in the first place. I’d imagine anyone who wanted to make a reimplementation could just… reimplement it from the documentation.
I’m guessing that’s kinda how GNU Octave came about. It’s a mostly-compatible clone of the proprietary “Matlab” application. (Matlab is basically a programming language.) There was probably good enough documentation out there about Matlab that the people behind GNU Octave could just build a replacement without needing to decompile the existing application.