Keeping a Weakness Secret If a company invents a padlock with some obscure weakness that most criminals would not guess, is there anything the company can do (before or after selling it to the public, or within some "user agreement" contract) to legally prevent people from publishing the details of that weakness? For example, this video exposed a weakness, thereby hurting all owners of the padlock: https://www.youtube.com/watch?v=RxM55DNS9CE In principle, the company could now sue the video's owner for negligence, but I doubt that the company would win, so I'm here asking if there is anything the company could have done beforehand to improve its chance of winning. Suppose the company and all customers are in Los Angeles, California.
On the one hand, there are statutes that prohibit the delivery of instructions which distort or circumvent the official/intended use or safety of a device. For a somewhat related example of this, see MCL 750.540c(1)(3). On the other hand, the company/manufacturer is unlikely to prevail under contract law no matter how clearly and conspicuously its EULA prohibits the disclosure of discovered weaknesses. That is because the prohibition in the EULA is outweighed by the severe vulnerability to which all other unsuspecting customers are subjected. From the standpoint of public policy, people's awareness of the discovered vulnerability is certainly in the public's best interest. The disclosure will warn both (1) potential customers not to purchase a product that fails or misses its primary purpose, and (2) current customers to adopt precautions now that the product's reliability has been disproved. Thus, the effectiveness of broadcasting the discovery of such weakness is in stark contrast with the technical deficits and managerial politics that typically hinder a company's ability (or its will) to respond to the issue. If the weakness was known to the manufacturer prior to the disclosure, the release of that product would constitute fraudulent misrepresentation. The details of the demonstration in the video supports the argument that the manufacturer knew --or should have known-- about that weakness, since a padlock design is supposed to pass all kinds of tests of breakability and not be disabled by a screwdriver. It is hard to deny that the notion that "the padlock is secure" induces customers to purchase the product. As such, the misrepresentation violates the contract law principle that a contract --such as a purchase-- be entered knowingly. See Restatement (Second) of Contracts at § 161-167. With respect to the publisher of the weakness, that misrepresentation renders the EULA-prohibition void. See Restatement at § 164(1). Regardless of whether or not the manufacturer incurred misrepresentation, the manufacturer's decision to sue the publisher is only likely to backfire by bringing more attention to the poor design of the product. In all, the manufacturer's best option is to do a product recall ASAP and enhance the design.
From what I can see on the USPTO registry, &quot;tweet&quot; is still not trademarked for the purposes you're talking about. Twitter has been working to secure that trademark, but I can't find any record of them having actually secured it. Just the same, I'd predict that using it will get you at least a cease-and-desist letter, and possibly a lawsuit. Whether you'd win that case seems to be a very open question, but that presumes you have the resources to litigate.
Such use might well be illegal, and subject the user to tort liability, or possibly even criminal liability. Parties For this discussion let us call the person or company that developed and wants to protect the information D, the person or company that downloaded and wants to use the information U, and the person who placed the information on the server P. Trade Secret One possible source of liability is if D considers the information to be a trade-secret. The law on trade secrets varies to some extent in different countries, although there is a general similarity. Since no jurisdiction is specified in the question, I am going to look at the united-states law. Definition The LII page on &quot;Trade Secrets defines a trade secret under the US Uniform Trade Secrets Act (&quot;UTSA&quot;) as: &quot;information, including a formula, pattern, compilation, program, device, method, technique, or process that: Derives independent economic value, actual or potential, from not being generally known to, and not being readily ascertainable by proper means by, other persons who can obtain economic value from its disclosure or use; and Is the subject of efforts that are reasonable under the circumstances to maintain its secrecy. A similar definition is given by the USPTO page on &quot;trade secret policy&quot;. Prior to the USTA, and still in those US states that have not adopted the USTA, trade secrets were/are protected under the common law. The LII page lists the common law factors, as given by the Restatement of Torts (1939) § 757, comment b: The extent to which the information is known outside the claimant's business The extent to which it is known by employees and others involved in the business The extent of measures taken by the claimant to guard the secrecy of the information The value of the information to the business and its competitors The amount of effort or money expended by the business in developing the information The ease or difficulty with which the information could be properly acquired or duplicated by others These factors may apply in other common-law countries. In either case, one must consider how the would-be user came to acquire the information, and thus how it came to be on the server from which it was downloaded. One must also consider whether it was the subject of &quot;reasonable efforts&quot; to protect its secrecy, under the circumstances. Circumstances If P was violating an obligation of confidentiality, such as an NDA or a duty as part of an employment relationship, then the placement of the info on the server was improper. In such a case its acquisition by another, such as U might constitute misappropriation. The same would be true if a person under an obligation of confidentiality arranged for the server to be indexed by a search engine, when it should not have been. The case for misappropriation would be stronger if U knew that the information was considered confidential by D, and also if P had informed U about where to find the info, or what search terms would uncover it. If P was acting with the permission of D, and P or someone else at D simply failed to realize that the server was, or might become, indexed, then the question is whether the steps taken by D to keep the info secret were reasonable. If this a case of &quot;inadvertent disclosure resulting from the trade secret holder's failure to take reasonable protective measures&quot; then there is no misappropriation, and the actions of U are lawful. That will depend of a judgement of whether D's actions were reasonable in light of the value of the info and the overall circumstances. If the placement of the info on the server is considered to constitute &quot;general publication&quot; of the info, so that it is no longer secret in any meaningful sense, then D may have a claim against P, but not against U unless U acted in collaboration with P. Copyright Law The documents downloaded from the4 server are almost surely protected by copyright. Directly incorporating them into an open source project without permission from the copyright holder would be copyright infringement, and would subject U to a suit for infringement. However, copyright does not protect ideas, methods, or facts. If U learns a method or idea from the document, and uses that knowledge without directly copying or closely paraphrasing the document, there is no copyright infringement and no claim under copyright law. Patent Law The question does not mention any patents. It is possible that D has patented the method describe in the downloaded documents. If so, and if the patent is valid, any use by U would be patent infringement, and the question of how U learned the info becomes irrelevant. However, most software developments such as data structures are not patented, so this is a somewhat unlikely, albeit possible, case. Notre that if the information is covered by a patent is is by definition not secret, as all patents must be openly disclosed. But they may not be widely publicized, and if U does not make a patent search, U may not realize that the document includes patented technology. This possibility is largely incompatible with the trade secret possibility, althogh it is possible to use trade secrets in connection with patented tech. Conclusion In short whether U may lawfully use then info, or is subject to a tort claim by D, or even criminal action, depend on the details of the overall facts. U would do well to take legal advice on the matter before proceeding to use the info.
are there any safeguards you could take to preemptively block such behavior, such as a disclaimer inside the book cover that reads something like The safeguard you outline would be overridden as soon as the author enters any contract that requires assignment of copyright. (I would not delve in the differences between licensing and copyright assignment because that hypothetical author is dealing with a contract of adhesion which readily requires assignment; the author has no option to change the ToS to allow for licensing only) Under contract law, one of the essential prerequisites is that the conditions of a contract be entered knowingly and willfully. By deliberately clicking on a ToS page to move forward with the uploading a copyrighted work, the author is signaling his awareness and acceptance of the ToS. The fact that the author chose not to read the ToS is irrelevant and very unlikely to strike whatever entitlements the website owner formulated in the accepted ToS. For the same reason, the author's safeguard disclaimer does not bind the website owner: It cannot be said that the website owner was aware of that disclaimer at the time of the formation of contract between the author and the website owner. That is, the website owner did not knowingly and willfully accepted the author's safeguard. The website owner is not even expected to know about any safeguards which one of its potential user intends to establish. The length of a ToS document is also irrelevant because the website owner has the valid argument that "the user-author could have skimmed through the ToS or do a search (via Control-Find) of keywords such as 'copyright' or 'property', whence any allegation of 'inadvertent' assignment of copyright is untenable". Is there a way to protect your IP from inadvertently being licensed/stolen/assigned via TOS "agreements", without having to waste your life reading huge one-sided online "contracts" that are "subject to change without notice" anyway? Yes. That consists of not uploading one's works in such platforms. In contract law that would be expressed as "declining an exchange of considerations". There are many other alternatives for an author to promote his work without being required to assign copyright.
In theory, a store can ban you or anyone else for any reason except those protected by law against discrimination. As a practical matter, you potentially have various forms of recourse. The first thing to do is to write the the CEO of the chain, with a long detailed letter describing the incidents, and naming names. Most CEO's don't want to deal with this kind of bad publicity, and will at least order an investigation, and make amends, if the internal investigation is in your favor. This would apply even to the late Sam Walton, if the chain is WalMart, or whoever the current CEO is. If you are a member of a protected minority, or even have dark skin, you can sue the chain on those grounds. There will be a presumption that they barred you on grounds of race or color. Then the burden of proof will be on them to show that they didn't bar you for those causes. As a form of "entrapment," you should take a witness, basically the most influential person you can get hold of that's not a family member, to the store with you to ask them why you were barred. The mayor of your town would be ideal, more llkely it would be a boss, teacher, or clergyman, but in any event, someone who knows you well. If you can get them to accuse you of stealing in front of this third party, you have the makings of a defamation case. And even if you aren't a minority, you can sue them anyway. You can demand "discovery" of all internal documents, videos, etc. relating to your case. Your lawyer will also the right to "depose" (cross examine) all offending managers.There's a good chance that something embarrassing will turn up in the process. (Many defendants settle in connection with discovery.) You might want to hire a second (libel) lawyer to teach you how to publicize the case without running into libel laws. If all this fails, the store can probably bar you, but you want to make it prohibitively expensive for them to do so, meaning that most rational people wouldn't bar you after the above. If they do, they're not rational and you're better off not using the store.
If it was something important to the owner, they would file injunctions/suits against everybody that they find the code in, and make those very public. This isn't unlike what the RIAA did to individual downloaders of pirated music files, filing over 18,000 lawsuits. They could subpoena GitHub for information related to IP addresses for who downloaded the code and go after them. It is unlikely that they would get a financial award but they could have the court order them to stop using it. Eventually the RIAA found that filing these lawsuits was more trouble than it was worth and started going after the internet service providers. These reduced the number of lawsuits and forced ISP's to moderate its own users, blocking some sites and protocols that programs like Napster relied on. Basically they shifted responsibility from themselves to the ISP's.
You would have to look at your contract with the company or the company's rules. Some companies have clauses that say they own things you develop while working for them and some don't. Without knowing your specific company's policy, it is impossible to say.
Unless you have a legally valid IP right related to the specification that statement is meaningless. When a software license is granted it is based on the copyright of the code. The copyright of the spec. just stops people from copying the spec - it does not protect the information in it. You can restrict copying of the spec. under copyright, you can make up a name for the spec (like USB or Bluetooth) and get a trademark and only allow the trademark use in limited cases(doesn’t stop implementation of the spec), or get a patent that would be necessarily infringed if something complying with the spec was created and used, sold, made, etc. or you can keep it secret and only show it to people who contractually agreed with your terms.