New alleged evidence of Android infringement isn't a smoking gun (ars technica)
New alleged evidence of Android infringement isn't a smoking gun (ars technica)
Posted Jan 22, 2011 16:51 UTC (Sat) by RogerOdle (subscriber, #60791)In reply to: New alleged evidence of Android infringement isn't a smoking gun (ars technica) by drag
Parent article: New alleged evidence of Android infringement isn't a smoking gun (ars technica)
1) How did the files get onto the Google server? Was the access authorized? What is Google's legal responsibility if it was authorized? What is Google's legal responsibility if it was not authorized?
2) Assume for the sake of argument that these are materials that Google does not have a right to. Google did not put those files onto it's servers. The situation is like some stranger parking a stolen car in your driveway. You did not steal the car. How does this effect the legal situation?
3) Did Google ever access the files themselves, other than for legal reasons resulting from their discovery?
4) How is liability shared in an open source project where patches may be posted. They have to be accessed in order to vet them for legal reasons before they are accepted or rejected. Does accessing a copyrighted patch that has not been accepted yet constitute a distribution of copyrighted material? It may but I would call this unintended and therefore not a violation of law if action is taken promptly when the situation is understood.
Anyone with a server with public access storage capability needs to know what their responsibilities and liabilities are. We know there are specific laws regarding the use and accessibility of personal information. What are the responsibilities and liabilities for general file storage and retrieval? Is the file space for an open source project with public access "public property" because it is publicly accessible or "private property"? How does that effect the situation?
The LWN site is currently under high scraper load, so comment display has been suppressed for anonymous users. If you are a human, you may read the comments by clicking the button below:
Note: you can avoid this step in the future by logging into your LWN account.
