The one thing I miss in bing is their advanced search doesn't allow for date ranges. Or at least I haven't found it yet. So I'm using Bing for normal searches and moving to Google when I want to find something by date.
Recent Reviews
-
I was given the Ipod nano 6th generation for Christmas 2011. I was starting to take up running and needed something to track my run. since I just started I was only using my Ipod roughly 3 times...
-
I have had the iPad Verizon 4G LTE for a month now, and over all I couldn't be happier with the machine. The only issue I have found so far is when on wifi it has a slower speed in processing...
-
I have owned at least a dozen different Mac laptops over the years, starting with a Powerbook 1400 back in the day. The 13-inch Air is my absolute favorite of the bunch. It's the first laptop...
-
I spent quite a bit of time reading the setup manuals and various Apple articles about manually setting up this device since I have an unusual setup, and the setup manuals indicated I would have...
-
all i have to say is i love it its so much faster and i could just slip it into my purse p.s it has a ton of space for the 64gb
Google found distributing Oracle's Java code within Android project - Page 6
- Joined: Jun 2006
- Location: South West Florida
- Posts: 8,341
- offline
- Select All Posts By This User
Maybe it's just me but date would seem a natural built in criteria so should be at the easy section not advanced. Just tried Blekko with .. /date ... at end of search (e.g. global warming/date) ... it works well as intended. It is beta so I assume that is why so many results have weird text issues. Hopefully it will get better. Their financial model seems to be the sharing of search tags as far as I can tell. There is a good into video.
Long on AAPL so biased. Strong advocate for separation of technology and politics on AI.
Long on AAPL so biased. Strong advocate for separation of technology and politics on AI.

A very elemental *Google* search would resolve your confusion about "willful" infringement. But since you clearly can't be bothered, let me share some verifiable information:
1. Copyright at its core doesn't require willful infringement - it operates on strict liability. Either you did a proscribed act (in this case, at least two proscribed acts - reproducing and distributing code) or you didn't. If you did, you're liable for statutory damages at the very least, unless a "fair use" exception excuses your violation (needless to say, no court would find that fair use applied in this case).
2. In addition to the strict liability, you get hit with even higher penalties if the plaintiff can demonstrate that you "willfully" infringed on her copyright (e.g. MP3.com putting all those songs on their server "because their users had already purchased the songs" or Google scanning all those books and putting them on the web because...well they're Google and I suppose information wants to be free...to sell ads).
3. To get statutory damages, a plaintiff does not need to show that you made a dime from violating her copyright. Just that you violated at least one of her exclusive rights. If she can prove that you did in fact make profit (and if the free of charge distributed Android violates the code, again no court would find that Google did not profit from it), then she can get significantly more damages.
You may spin the facts (which remain somewhat unclear) as you see fit but you, like Velben, also seem keen on recasting intellectual property LAW to mesh with your view of the world. Doesn't work that way.
Needless to say, there is no "my bad" exception to copyright law, where by you "remove" the "pointless" copyrighted work after having violated the owner's rights and magically escape liability.
I think Google is 100% liable for having these particular files within their repository. I just don't think that these particular files were used by Google in a way which significantly damaged Oracle based on the information we have about them. These do not appear to be central to Google's development process at all, they simply existed out in a branch of their repository. From my understanding the commercial gain or loss of the infringement is central to damages. I don't think these files in particular would cost Google a significant amount in damages should Oracle include them in their lawsuit. Since the code in these files wasn't used significantly during the development process and thus wasn't included in the code that shipped I don't think it's likely they'd receive per handset damages like some have suggested. Even if they were found guilty and charged the maximum of $150,000 per infringement, 37 * 150,000 is about 5.5 million. As I've had time to think about this story, I also wonder why if these files have existed since Oracle began it's lawsuit why Oracle didn't include them. Was it because this Mueller individual was more thorough or was it because Oracle didn't think them worth mentioning? My opinions don't have anything to do with anything more than the files mentioned in the Apple Insider article and shouldn't be assumed to apply to all of the code involved in the Oracle vs Google suit.
I don't have any particularly strong feelings for or against Google. Perhaps because I'm a system admin and have been friends with people who administer software repositories I relate more with the difficulties of their job. I can imagine them out at lunch complaining to me about how some 3rd party developer's script globally replaced the licensing headers in code that was eventually uploaded into the repository. How the the developer uploaded the files in compressed format into an obscure branch of the repository and because the code wasn't used it didn't go through internal code review. How it was probably excluded from any scripts analyzing the code because it was compressed. I can imagine executives sending emails asking them to document in detail procedural minutia to relate why this wasn't caught. I can image my words to them, "That sucks." Sounds like a bad Monday at work to me.
- hill60
- Tomorrow Calling
- Joined: Dec 2008
- Location: straya
- Posts: 4,866
- offline
- Select All Posts By This User

I think Google is 100% liable for having these particular files within their repository. I just don't think that these particular files were used by Google in a way which significantly damaged Oracle based on the information we have about them. These do not appear to be central to Google's development process at all, they simply existed out in a branch of their repository. From my understanding the commercial gain or loss of the infringement is central to damages. I don't think these files in particular would cost Google a significant amount in damages should Oracle include them in their lawsuit. Since the code in these files wasn't used significantly during the development process and thus wasn't included in the code that shipped I don't think it's likely they'd receive per handset damages like some have suggested. Even if they were found guilty and charged the maximum of $150,000 per infringement, 37 * 150,000 is about 5.5 million. As I've had time to think about this story, I also wonder why if these files have existed since Oracle began it's lawsuit why Oracle didn't include them. Was it because this Mueller individual was more thorough or was it because Oracle didn't think them worth mentioning? My opinions don't have anything to do with anything more than the files mentioned in the Apple Insider article and shouldn't be assumed to apply to all of the code involved in the Oracle vs Google suit.
I don't have any particularly strong feelings for or against Google. Perhaps because I'm a system admin and have been friends with people who administer software repositories I relate more with the difficulties of their job. I can imagine them out at lunch complaining to me about how some 3rd party developer's script globally replaced the licensing headers in code that was eventually uploaded into the repository. How the the developer uploaded the files in compressed format into an obscure branch of the repository and because the code wasn't used it didn't go through internal code review. How it was probably excluded from any scripts analyzing the code because it was compressed. I can imagine executives sending emails asking them to document in detail procedural minutia to relate why this wasn't caught. I can image my words to them, "That sucks." Sounds like a bad Monday at work to me.
So how's Oracle's income stream from J2ME coming along?
Pre-Android compared to post-Android?
"The cobbler's children have no shoes", is a saying that applies a lot to companies who provide products and services. -KDarling on Google Search.
"The cobbler's children have no shoes", is a saying that applies a lot to companies who provide products and services. -KDarling on Google Search.
Patent infringement is like having stock options. It's all about watching your stock price grow, then cashing in at the right time. I mean, so how long has the "open source" Android OS been distributed and Oracle hasn't been bothered until recently to look through it? Taking any of this seriously is a mistake.
I'm just talking about the 37 files referenced in the Apple Insider article.
"My opinions don't have anything to do with anything more than the files mentioned in the Apple Insider article and shouldn't be assumed to apply to all of the code involved in the Oracle vs Google suit."
If these files weren't used significantly to create Android how would their existence significantly affect Oracle's income stream from J2ME pre and post android? I'm not seeing the correlation between these files in particular and decreased income stream from Oracle. Now I can see Google being found liable for their existence in their repository, but for these files in particular I don't see how the damages would be more than 7 digits at the very most. It's my opinion on the relative insignificance of these files which caused me to post in this string. I have not expressed any opinion on the broader Oracle vs Google suit.
Here is the detail on the files I am talking about.
"The second set of 37 files is actually zipped up into one file called MMAPI.zip and tucked away in a directory used for native code audio drivers for one particular type of chip set. Florian really had to go digging for this one. I double-checked the make files and its clear this file is not shipped with Android either. Somebody uploaded it by mistake and it should simply be deleted." - http://www.zdnet.com/blog/burnette/o...n-android/2162

It's all about Oracle's lawyers talking with Google Lawyers and seeing how much of the Android pie Google is willing to give to Oracle.
Patent infringement is like having stock options. It's all about watching your stock price grow, then cashing in at the right time. I mean, so how long has the "open source" Android OS been distributed and Oracle hasn't been bothered until recently to look through it? Taking any of this seriously is a mistake.
Of course it is serious. If Oracle get $10 a licence and retrospectively it means that Google's business model is shattered, or the manufacturers is.

Maybe it's just me but date would seem a natural built in criteria so should be at the easy section not advanced. Just tried Blekko with .. /date ... at end of search (e.g. global warming/date) ... it works well as intended. It is beta so I assume that is why so many results have weird text issues. Hopefully it will get better. Their financial model seems to be the sharing of search tags as far as I can tell. There is a good into video.
The problem with Google date preferences is it only uses the page modification date in the header data, not whether the content on the page has changed or not. This is easily spoofed by SEO.
I am personally dealing with a competitor who has a high page ranking (as do I) and we are constantly swapping the top spot however I am updating my page with new content where he only re-saves his page and uploads it again to make it newer than mine. His content is still from 1999. Unfortunately for him though his content actually mentions our company because without that he would have no relevance whatsoever.
Life is too short to drink bad coffee.
Life is too short to drink bad coffee.

Here is the detail on the files I am talking about.
"The second set of 37 files is actually zipped up into one file called MMAPI.zip and tucked away in a directory used for native code audio drivers for one particular type of chip set. Florian really had to go digging for this one. I double-checked the make files and its clear this file is not shipped with Android either. Somebody uploaded it by mistake and it should simply be deleted." - http://www.zdnet.com/blog/burnette/o...n-android/2162
Just because the body is hard to find, doesn't mean that murder wasn't committed.

Frivolous lawsuits are usually dismissed early in the proceedings.
Your solution would certainly add additional discouragement to frivolous suits. However, it would also discourage novel suits by all but the wealthy. This is America, and we like justice better than that.
New and novel causes of action are good for all of us. For example, many product liability lawsuits used to get thrown out as frivolous, but the law has since expanded to give us additional protections against defective and dangerous products.
Don't throw the baby out with the bathwater. Instead, try to get the existing protections enforced more often, like sanctions which can be imposed on those who bring forth frivolous cases.
I understand that this affects not only frivolous lawsuits but the US is in serious need of tort reform and "loser pays" has several benefits.
I know this is an old article but I think it is a good read which points outs some of the advantages of the "loser pays":
http://reason.com/archives/1995/06/01/civil-suits
Yeah sort of like those home wifi hacks that accidentally happened while doing routine street view photos.
Life is too short to drink bad coffee.
Life is too short to drink bad coffee.
Comparing a zip file of code for testing audio drivers for one chipset with murder... seriously? I've read this forum for years, I read your posts and usually agree with you. That's not a statement that's commensurate with these files. These files didn't aid in the development of Android. I agree they are liable for having them there but the damage is minimal if any. If anything it's more like a paper cut, not murder.

I think Google is 100% liable for having these particular files within their repository. I just don't think that these particular files were used by Google in a way which significantly damaged Oracle based on the information we have about them. These do not appear to be central to Google's development process at all, they simply existed out in a branch of their repository. From my understanding the commercial gain or loss of the infringement is central to damages. I don't think these files in particular would cost Google a significant amount in damages should Oracle include them in their lawsuit. Since the code in these files wasn't used significantly during the development process and thus wasn't included in the code that shipped I don't think it's likely they'd receive per handset damages like some have suggested. Even if they were found guilty and charged the maximum of $150,000 per infringement, 37 * 150,000 is about 5.5 million. As I've had time to think about this story, I also wonder why if these files have existed since Oracle began it's lawsuit why Oracle didn't include them. Was it because this Mueller individual was more thorough or was it because Oracle didn't think them worth mentioning? My opinions don't have anything to do with anything more than the files mentioned in the Apple Insider article and shouldn't be assumed to apply to all of the code involved in the Oracle vs Google suit.
It should be a frightening thought for Google if Oracle knew about the above files and just did not believe they were central to case. It will be interesting to see if they add this issue or are confident that there case does not need this additional embellishment.

Comparing a zip file of code for testing audio drivers for one chipset with murder... seriously? I've read this forum for years, I read your posts and usually agree with you. That's not a statement that's commensurate with these files. These files didn't aid in the development of Android. I agree they are liable for having them there but the damage is minimal if any. If anything it's more like a paper cut, not murder.
I thought it was obvious, but, just to make it clear, I was showing how ridiculous your line of reasoning was by showing how it would apply as a general principle of law. In other words, just because a crime is hard to discover, doesn't make it less of a crime. Note, this criticism dismisses at least 99% of the pro-Google arguments made in this thread, since that's really the only defense there is, that Google's violation of copyright law wasn't easily discovered. Doesn't make it any less of a violation, just like burying the body doesn't absolve one of murder.

Comparing a zip file of code for testing audio drivers for one chipset with murder... seriously? I've read this forum for years, I read your posts and usually agree with you. That's not a statement that's commensurate with these files. These files didn't aid in the development of Android. I agree they are liable for having them there but the damage is minimal if any. If anything it's more like a paper cut, not murder.
There are two issues here. The copyright issue - where publishing the source code in any tree is a violation, and 2) the patent issue which is similar to the case against MS for using J++.
Now if Google can prove the first, it probably proves the latter.
I am not sure how the GPL comes into this, Google's defence is that Oracle are entrapping people by putting the GPL at the top of the files and then adding other licensing caveats. That might work as a defence, I dont know.
Copyright is definitely violated here, as the original licence was changed ( idiotically, if they werent using it). Thus this violates the GPL. You cant move from GPL to Apache, you can only get more restrictive. What I dont know, however, is whether invalidating the GPS licence therefore resets the previous licence - that is the patents, and the Oracle copyright prior to the GPL is then invoked.
Judges are going to have to be very technical aware.
Apple pulled AirPrint functionality from printers attached due to licensing issues right? They had the offending files in their development versions of OS X which were distributed to developers. You can even download the files which were included at http://netputing.com/2010/11/11/airprint-hacktivator/. Apple realized these files had licensing issues and didn't ship them to non development versions. To me it would be preposterous for anyone to think that just because Apple included these files in the development versions of their code and distributed it in this limited basis that there is any danger to OS X as a platform or that Apple would end up being liable for a per installation judgement. This case would be a more egregious violation of a copyright than the Google example because the files were actually used in the main development code base of OS X. In this example I wouldn't consider that Apple had no respect for intellectual property. They realized the code was a license violation and removed it before shipping it to their non-development install base. This kind of stuff happens all the time and doesn't endanger the viability of the platforms themselves.

Apple pulled AirPrint functionality from printers attached due to licensing issues right? They had the offending files in their development versions of OS X which were distributed to developers. You can even download the files which were included at http://netputing.com/2010/11/11/airprint-hacktivator/. Apple realized these files had licensing issues and didn't ship them to non development versions. To me it would be preposterous for anyone to think that just because Apple included these files in the development versions of their code and distributed it in this limited basis that there is any danger to OS X as a platform or that Apple would end up being liable for a per installation judgement. This is case would be a more egregious violation of a copyright than the Google example here because the files were actually used in the main development code base of OS X. In this I wouldn't consider that Apple had no respect for intellectual property. They realized the code was a license violation and removed it before shipping it to their non-development install base. This kind of stuff happens all the time and doesn't endanger the viability of the platforms themselves.
No amount of explaining that copyright has nothing to do with the compiled executables will apparently work in this thread. Those files are binaries ( there is a hint in where they get installed), not source. Apple is implementing their own version of the idea and the patent is about the workings of the software, not the copying of the source files line by line. in that case pulling from a release is good enough. They are not publishing any source.

I thought it was obvious, but, just to make it clear, I was showing how ridiculous your line of reasoning was by showing how it would apply as a general principle of law. In other words, just because a crime is hard to discover, doesn't make it less of a crime. Note, this criticism dismisses at least 99% of the pro-Google arguments made in this thread, since that's really the only defense there is, that Google's violation of copyright law wasn't easily discovered. Doesn't make it any less of a violation, just like burying the body doesn't absolve one of murder.
That was not obvious to me because the files being hard to find hasn't been my argument. My argument is that the files in the zip file were not used for development of anything significant on Android. Their distribution in whatever limited fashion to the development community was likely a violation of the copyright. However, since a significant portion of copyright violation damages have to do with the damage done and gain from the violation, we have to look at the importance of the files themselves and how they were used to estimate what we think the damages might be and how significant the effect of these damages would be to Google.

That was not obvious to me because that the files were hard to find hasn't been my argument. My argument is that the files in the zip file were not used for development of anything significant on Android. There distribution in whatever limited fashion to the development community was likely a violation of the copyright. However, since a significant portion of copyright violation damages have to do with the damage done and gain from the violation, we have to look at the importance of the files themselves and how they were used to estimate what we think the damages might be and how significant the effect of these damages would be to Google.
The main case against Google is the patent violation. This copyright violation ( and these are probably not the only examples) will make it hard for Google to claim that they "clean roomed" their own JVM.
Their counter argument is that Oracles licences are invalidated by the GPL.

No amount of explaining that copyright has nothing to do with the compiled executables will apparently work in this thread. Those files are binaries ( there is a hint in where they get installed), not source. Apple is implementing their own version of the idea and the patent is about the workings of the software, not the copying of the source files line by line. in that case pulling from a release is good enough. They are not publishing any source.
Binaries can violate a patent or license. You don't need to publish the source code to violate a patent or license.

The main case against Google is the patent violation. This copyright violation ( and these are probably not the only examples) will make it hard for Google to claim that they "clean roomed" their own JVM.
Their counter argument is that Oracles licences are invalidated by the GPL.
So If I'm understanding you correctly you are saying these files are important because they show that Google used Oracle code as a starting point to reverse engineer the JavaVM to make the Davlik VM. Are you saying that this code in particular shows how the original Oracle JavaVM code worked thus allowing Google to reverse engineer the Java VM code in the Davlik JVM?
- Joined: Dec 2010
- Location: Don't hate me br0
- Posts: 121
- offline
- Select All Posts By This User
This was a good (but lengthy) read on the recent revelations over this (alleged) infringement. This thread has been fascinating too.

http://www.groklaw.net/article.php?s...10122054409107
This was a good (but lengthy) read on the recent revelations over this (alleged) infringement. This thread has been fascinating too.
That just made the whole thing a lot more grey and murky than it already was.
- Joined: Feb 2010
- Location: Tokyo, Japan
- Posts: 394
- offline
- Select All Posts By This User

You are inaccurate when you say "Damages are based on whether or not it was intentional" and dead wrong when you say "I can host music on my computer all I want; until someone downloads it from me no infringement took place."
Copyright operates on STRICT liability. You will incur statutory damages for a copyright violation regardless of your intent (if you're thinking of the "innocent infringer" defense, the judge only reduces damages, and anyway it pretty much would never apply to a sophisticated defender like Google.)
Once you make a copy of copyrighted music without authorization, you could be liable for violating the reproduction right. Now on a practical level, if you just copied it to a hard drive that you unplug and put on a shelf for the next 20 years, nobody's going to be able to sue you.
If you put the same music files on a publicly accessible server, you could additionally be liable for violating the right to distribute, whether or not a single copy was ever downloaded.
Your statement is like saying if you made 1000 copies of the Lion King and put it on a shelf in your store, you wouldn't be liable for infringement unless someone actually bought one of your bootlegs. Now even if the copies were in your home, if there were a reason to raid your home (say if a search warrant were issued because you are a notorious bootlegger), you'd still be liable for violating the reproduction right. Now, no judge is likely to issue a search warrant for a fishing expedition into people's homes unless there's a very good reason to think they're engaged in serious violations.
A more accurate statement would be "I can host music on my computer all I want; until someone downloads it from me, no one's likely to sue me for the infringement I've already committed."
Google cannot escape liability simply because only one person or 100 people downloaded an otherwise protected work. The number of people who downloaded it is completely irrelevant to base level liability, as is whether those people were internal or external to Google.
For your two blah blah blah posts, you need to read up on actual court cases, not just what the law says. Without proof that any downloading took place, there cannot be any damages assessed to a person by the RIAA.
Of course, just like you, the RIAA thinks making available = infringement. It doesn't, and court case after court case has proven this. That's why mediasentry collects a log of those who share on torrents to collect proof of infringement.
Same case with bootleggers that sell actual copies of "Lion King" (what the heck are you like 12?); unless they actually sell something in front of the authorities they cannot be arrested.
It's a refreshing change from the typical classless Google/Android advocate that we get here that you're doing your best to try to come across as reasonable, but you're just talking in circles, and backpeddling when your arguments don't work out. However, your argument was in fact that the files were hard to find, tucked away in a little backwater, wrapped up in a zip file, who would ever even notice them. And, it's an argument that carries no weight whatsoever. The body was hidden, but it was found.
The rest of it, that they supposedly, apparently, possibly weren't being used for anything important is not only a moot point, but entirely beside the point.

No worries on missing the distribute part.
In reference to B) I believe one of the arguments Google was making was that some of the files were only used on internal test devices and were not distributed to external parties.
You mentioned that even if the only people who Google distributed the code to were bloggers who just analyzed it for copyright issues that Google was guilty. I agree, but in this scenario what financial damage did this do to Oracle and what did Google gain from the infringement? This just looks like a little nit picky error that lawyers are going to make a big deal about. Little mistakes like this happen all the time. To me this just makes Oracle look like a patent troll.
Calling Oracle a "patent troll" for protecting its IP shows how little respect you have for IP. When a corporation spends millions of dollars on developing a product, it has every right to protect it from being stolen. Oracle has every right to protect its innovation, Java. If Google accepted the license and the license prohibited distribution of the code, then Oracle has every right to go after Google.
- hill60
- Tomorrow Calling
- Joined: Dec 2008
- Location: straya
- Posts: 4,866
- offline
- Select All Posts By This User

I'm just talking about the 37 files referenced in the Apple Insider article.
"My opinions don't have anything to do with anything more than the files mentioned in the Apple Insider article and shouldn't be assumed to apply to all of the code involved in the Oracle vs Google suit."
If these files weren't used significantly to create Android how would their existence significantly affect Oracle's income stream from J2ME pre and post android? I'm not seeing the correlation between these files in particular and decreased income stream from Oracle. Now I can see Google being found liable for their existence in their repository, but for these files in particular I don't see how the damages would be more than 7 digits at the very most. It's my opinion on the relative insignificance of these files which caused me to post in this string. I have not expressed any opinion on the broader Oracle vs Google suit.
I was giving an example of what Oracle may try to claim as damages, whether actual or not that is the scope that they'll ask a court to look into.
Now the same files have been found in the repositories of some Android licensees:-
http://fosspatents.blogspot.com/2011...te-oracle.html
"The cobbler's children have no shoes", is a saying that applies a lot to companies who provide products and services. -KDarling on Google Search.
"The cobbler's children have no shoes", is a saying that applies a lot to companies who provide products and services. -KDarling on Google Search.
Patent trolls don't make product...so Oracle can't be one.
However, I wonder just how much of a silly grin Ellison was sporting when he bought Sun.
Given Gosling's comments suing Google was the plan from day one so Oracle's lawyers must think there's a very good shot of a Google payday in their future. Maybe not 100% sure but pretty danged close if you're going to pony up 7 billion for a mostly failed company.
Groklaw sure would like to paint this as SCO 2 but Oracle isn't desperate and Ellison isn't incompetent. PJ is as biased as every other freetard out there...

It's a refreshing change from the typical classless Google/Android advocate that we get here that you're doing your best to try to come across as reasonable, but you're just talking in circles, and backpeddling when your arguments don't work out. However, your argument was in fact that the files were hard to find, tucked away in a little backwater, wrapped up in a zip file, who would ever even notice them. And, it's an argument that carries no weight whatsoever. The body was hidden, but it was found.
The rest of it, that they supposedly, apparently, possibly weren't being used for anything important is not only a moot point, but entirely beside the point.
I believe I understand your argument. I think we can agree to disagree on this. I'm sure there are many things I'll agree with you on in the future.

Calling Oracle a "patent troll" for protecting its IP shows how little respect you have for IP. When a corporation spends millions of dollars on developing a product, it has every right to protect it from being stolen. Oracle has every right to protect its innovation, Java. If Google accepted the license and the license prohibited distribution of the code, then Oracle has every right to go after Google.
I backed off of my statement calling Oracle a "patent troll". I've included my quote below. Calling Oracle a patent troll was a mistake.
- hill60
- Tomorrow Calling
- Joined: Dec 2008
- Location: straya
- Posts: 4,866
- offline
- Select All Posts By This User
I'm wondering why they aren't using the Psystar vs Apple ruling as an example, it's a bit more current than Apple vs Microsoft.
"The cobbler's children have no shoes", is a saying that applies a lot to companies who provide products and services. -KDarling on Google Search.
"The cobbler's children have no shoes", is a saying that applies a lot to companies who provide products and services. -KDarling on Google Search.

That was not obvious to me because the files being hard to find hasn't been my argument. My argument is that the files in the zip file were not used for development of anything significant on Android. Their distribution in whatever limited fashion to the development community was likely a violation of the copyright. However, since a significant portion of copyright violation damages have to do with the damage done and gain from the violation, we have to look at the importance of the files themselves and how they were used to estimate what we think the damages might be and how significant the effect of these damages would be to Google.
Finally, you seem to have gotten the point that *liability* for copyright violation has nothing to do with the "extent" of the infringement. But then you go and continue pulling stuff out of...
Let me explain how the process works (as opposed to how YOU think it should work):
Was there a violation of one or more of the exclusive rights in the copyrighted work?
If yes, then unless one of the limitations on the exclusive rights (i.e. fair use, first sale etc.) applies, the court finds that copyright infringement has occurred, liability is established and ONLY then does the issue of damages come up.
Damages would have nothing to do with the "importance" of the copied files or how they were used; though perhaps a court might look at the economic value of the infringing work (i.e. Android, if it indeed contains infringing code). However, for statutory damages, that examination is not necessary at all.

Finally, you seem to have gotten the point that *liability* for copyright violation has nothing to do with the "extent" of the infringement. But then you go and continue pulling stuff out of...
Let me explain how the process works (as opposed to how YOU think it should work):
Was there a violation of one or more of the exclusive rights in the copyrighted work?
If yes, then unless one of the limitations on the exclusive rights (i.e. fair use, first sale etc.) applies, the court finds that copyright infringement has occurred, liability is established and ONLY then does the issue of damages come up.
Damages would have nothing to do with the "importance" of the copied files or how they were used; though perhaps a court might look at the economic value of the infringing work (i.e. Android, if it indeed contains infringing code). However, for statutory damages, that examination is not necessary at all.
Your right I should have used economic value instead of important in that statement. I understand that statutory damages for each violated work up to $150,000 per violation could be assigned. I should have included that as well.

For your two blah blah blah posts, you need to read up on actual court cases, not just what the law says. Without proof that any downloading took place, there cannot be any damages assessed to a person by the RIAA.
Of course, just like you, the RIAA thinks making available = infringement. It doesn't, and court case after court case has proven this. That's why mediasentry collects a log of those who share on torrents to collect proof of infringement.
Unlike you, I'm not talking about RIAA cases, I'm talking about COPYRIGHT cases - which clearly only one of us has actually studied in any depth. I have a more than 10 year history of criticizing the RIAA's wrongheaded approach towards online infringement (google "Nine Things The Record Industry Should Note About The Future Of Music").
Copyright infringement cases historically were never pursued against END USERS (mostly because the technology for infringing was never available on any significant scale to this group). The RIAA law suits violate this unspoken tradition, and that's why they'll continue to have difficulties.
However, the RIAA's challenges are not a good indicator of what would happen in more traditional copyright cases such as this, with a well-heeled corporation as a defender.
Pull your head out of your ass, not liking what I have to say won't make it any less true. And btw, you cannot understand copyright law by just reading the RIAA's bullshit cases.
As to your last (characteristically dumb) point, you should talk to Brooklyn DA, Charles Hynes. Apparently, he didn't get your memo on bootleggers rights - [http://www.nytimes.com/2010/11/05/ny...nollywood.html. I hope you don't plan to make a career representing bootleggers, just stick to talking out of your ass on the internet.
I suspect Google knew they were walking a thin line and the real issue is Google thought they could get away with all this because what were the chances Sun would do anything about it. Then Oracle bought Sun...oooops....
i think they thought that AND had the notion that Chrome OS was the future and they would ditch android.....EPIC FAIL!
Recent Discussions
- › New Microsoft Windows 8 ad turns Apple's Siri against her maker 2 minutes ago
- › With spotlight on it & Apple, Ireland calls for worldwide tax... 2 minutes ago
- › Corning touts Gorilla Glass 3's advantages over sapphire in... 5 minutes ago
- › Your ideas, hopes and links for green travel. 11 minutes ago
- › Google's new 3D Maps destroy Manhattan in the wake of Apple's Flyover 20 minutes ago
- › Like Apple, Google & Yahoo also avoid taxes by way of Ireland 21 minutes ago
- › Apple's iWatch to come in late 2014 with focus on biometrics,... 30 minutes ago
- › Popular game engine Unity drops licensing fees for iOS app developers 30 minutes ago
- › Microsoft unveils 'Xbox One,' a voice-controlled all-in-one... 36 minutes ago
- › Google to activate voice search in Chrome iOS app 47 minutes ago
Recent Reviews
- › Apple iPod nano - 16GB, Silver MC526LL/A (6th Generation) by cc420
- › Apple iPad with Retina Display Wi-Fi + Verizon/Sprint 4G - 64GB,... by Aaron Krahn
- › 13.3-inch Apple MacBook Air MD231LL/A (Mid-2012) by ahilal
- › Apple Time Capsule - 2TB (MD032LL/A) by biyahero
- › Apple iPad Wi-Fi - 64GB, White (MD330LL/A) by raeganapril
- › Apple Magic Trackpad (MC380LL/A) by WisdomSeed
- › Aperture 3 by bcbcbroderick
- › 17-inch Apple MacBook Pro MD311LL/A (Late 2011) by bcbcbroderick
- › Apple iPod touch - 32GB, Black MC544LL/A (4th Generation) by bcbcbroderick
- › Apple iPod touch - 8 GB, White MD057LL/A (4th Generation) by bcbcbroderick
New Apple Wikis
- › 2013 'Modified' iPod touch by Mikeycampbell81
- › 2013 MacBook Pros by Mikeycampbell81
- › iPad mini 2 with Retina display by Mikeycampbell81
- › 2013 iPhone 5S by Mikeycampbell81
- › Trade in your old devices for holiday cash by Mikeycampbell81
- › How to sell your old iPad for cash by Mikeycampbell81
- › How to offset the cost of a new iPhone by... by Mikeycampbell81
- › How to save money on AppleCare extended... by Kasper
- › How to offset the cost of a new iPad mini by... by Mikeycampbell81
- › Apple Prototypes by Mikeycampbell81
About AppleInsider | Join the Community | Advertise
© 2013 AppleInsider is powered by Huddler Tech | FAQ | Support | Privacy/TOS | Site Map






