How is the cost of a software service determined? I just went through a Compliance eLearning which had a section covering anti-trust laws. My understanding of predatory pricing from that is inline with this description I found on wikipedia During the period of predatory prices, the predator's profit is negative, or the price is lower than the cost. At the end of the eLearning, a quiz asked: If a competitor tries to enter the same market one is in, what would be lawful behavior and what might lead to prosecution in regards to anti-trust laws? The correct answer, of multiple possible answers, suggested that One could try to make their products attractive by giving the best reasonable discount you could offer. While another possible answer was Giving a discount on the Software suite that will temporarily sell the software below cost price. But this can be changed again as soon the competitor is driven off the market. which obviously would be a breach of anti-trust laws. But this left me confused, if I ever was working in sales or a related department.... What is actually considered the cost of a software service in this regard? And what is considered a reasonable discount in that regard, and what is unreasonable?
There is no fixed rule for this. Every situation is different, and of course there is nothing specific to software in there. It is very much a matter of intent. For example, negative profits are no clear sign. Company X thinks they could make $6 million profit by developing a product and selling it, minus $4 million development cost. It turns out development cost is $10 million. Raising prices is not possible because of competition. Company X will suffer losses of $4 million, without being predatory in any way. The reality is that a judge will look at the situation, take everything into account, and make a decision based on what they see. Since this is all about competition law, the main point is the intent or effect that your pricing makes competition impossible. That's what the judge will decide. For example, if you offer your service for $500,000 while others offer a similar service for $1,000,000 you could be using some super efficient processes that allow you to make money at that price, or you might have an idiotic sales person who will drive your company into bankruptcy, or you are trying to drive your competitors out of business. That's what the judge will decide.
The customer will own exactly what is stated in the contract. As the contractor, who wants to be able to reuse code (which is in everybody’s best interest) you want to keep the copyright, with the client having the license to use the code any way they want. If the customer wants the copyright with the contractor losing all rights, that will be in the contract, and it will cost. If the contractor produced an application that use lots of domain knowledge supplied by the client, that will often not give the client copyright, if the contractor is the one producing the actual expression of that knowledge by translating knowledge into code. If the client provides knowledge that is actually a trade secret, then an NDA should be signed. And again, it’s contracts. The client can put into the contract that their domain knowledge must not be reused. That is quite reasonable. The client might add to the contract that the contractor will not write software for any competitor. That is legal if it is in the contract, but it will cost.
The user gains the use of the software, the EULA issuer gains the limitations on how the user of the freeware will use it, that for example, prevent the freeware user from exploiting the issuer's labor by reusing it for profit. Consideration doesn't have to be monetary. As a practical matter, sometimes the business model is to give the software away as a loss leader and to have the issuer make their money with training and consulting on how to use it. Also, even in the absence of consideration, a promise upon which the person benefiting from the promise reasonably relies is enforceable under the doctrine of promissory estoppel. Further, EULA stands for &quot;end user license agreement&quot; and there are many times that license agreements aren't full fledged contracts. They are merely limited grants of permission to use something, often not even amounting to a full fledged property right or contract right. For example, if I let my neighbor walk into my living room while we talk and have tea, the right of the neighbor to be in my living room is called a license, even though it is not a contract. A license can be embedded in a contract, but it doesn't have to be.
At least in theory an end user could be sued for infringing on a patent, especially a method claim. Given the cost of a patent lawsuit, this strikes me as extremely unlikely to happen though, unless the user in question were an extremely large company, or something on that order. Theoretically, the only difference between open-source software and proprietary software would be that availability of the source code makes it easier to prove use of a patent in open-source software. Releasing the software as open-source doesn't confer any immunity from patent law or anything like that though. Realistically, however, the chances of being sued for infringement if you're basically giving away the software in question are fairly remote. It rarely makes sense for a patent holder to spend millions of dollars on a lawsuit where they stand no chance of even recovering their cost (but no, that certainly should not be taken as legal advice that you're free to infringe on patents, or anything similar--in fact, none of this should be taken as legal advice at all). If you can actually prove that a technique was published or publicly known and used (e.g., in a product that was offered for sale) well before the patent was applied for, the patent is probably invalid (and if proven so in court, the case would normally be dismissed with prejudice, which basically means the patent holder wouldn't be able to sue anybody else for infringement of that patent). I'd note, however, that in my experience this is much less common than most people imagine--many look at (for example) the title of a patent, and assume it lacks originality because it refers to some well-known technique, and ignore the claims where it details the precise differences between the previously known technique and what the patent really covers. Just for example, the EFF used to have a web page talking about a (now long-since expired) patent on how to draw a cursor on screen. In an apparent attempt at scaring the unwary, they showed code they claimed infringed in the patent--despite the fact that the patent's "background of the invention" specifically cited the technique they showed as being previously known, and not covered by the patent.
Do I have recourse against seller? Is the seller liable or obligated to disclose this and if so what are my options? Probably not. The general rule is that you accept any condition which could be discovered with reasonable inspection. When &quot;At the time of sale I waived inspection and did As-Is&quot; you are greatly limiting your claims. If the seller believe that the work done fixed the problem, you probably have no remedy. It could be that the seller made a false representation in the disclosure (you'd have to look at the exact language) but even then proving it with only the kind of circumstantial evidence provided would be very challenging. In particular, as a practical matter, it isn't really economic to sue in a $10,000 non-disclosure case without open and shut clarity of fault, as opposed to some suggestive but ultimately inconclusive indicators. You could always ask and state the case in a demand letter, but if you came to me as a potential client, I wouldn't take your case because the high cost combined with the low likelihood of success would make it unlikely that an attorney could bring the case in a way that would generate net value to the client.
Can my water district's billing practices still be legal? They are likely to be legal, but it isn't entirely clear. Contract Law ETo data is not published in advance of billing, which seems to violate Contract Law's notion of agreement between parties. A contract can set forth a formula for determining a price, rather than a particular dollar amount. For example, my utility company charges me a rate for electricity and natural gas that is based upon the market price of those commodities that it has to pay (although since my utility is a regulated utility, it has to get approval from a government agency each time it does so to confirm that it is really charging the market rate). Similarly, in the construction industry, and in government contracts, &quot;cost plus&quot; contracts that charge based upon whatever is spent to get the job done plus a market up by the general contractor, are not uncommon. Proposition 218 The Proposition 218 analysis is trickier. This is clearly not a tax or an assessment. So the threshold question is whether this is a Property Related Fee. In December of 2018 a legislative analysis stated that: A fee is a charge imposed on an individual or business for a service or facility provided directly to an individual or business. Local governments charge fees for a wide range of purposes, from park entry fees to building plan check fees. The amount of the fee may not exceed the cost of government to provide the service. Proposition 218 restricts property-related fees, defined as fees imposed &quot;as an incident of property ownership.&quot; At this time, there is no consensus as to which fees meet this definition. The drafters of Proposition 218 indicate that it was their intent to include most fees commonly collected on monthly bills to property owners, such as those for water delivery, garbage service, sewer service, and storm water management fees. Other analysts of Proposition 218 contend that fees that vary by level of service (for example, a fee for metered water usage) should not be considered a property-related fee, because it is based on service usage, rather than property ownership. Because Proposition 218 does not restrict nonproperty-related fees, the definition of this term will be an important and sensitive issue for the Legislature and courts. But, the California Supreme Court clarified this in July of 2006 in the case of Bighorn-Desert View Water Agency v. Verjil, ruling that metered rates for consumption of water are “property-related fees” subject to Proposition 218. So, assuming that your Water District is a governmental agency and not just a private company like a Ditch Company from which you receive privately owned water because you have shares in it, Proposition 218 should apply. This leads to the second question: Does the amount of the fee exceed the cost of government to provide the service? This is a non-trivial question with lots of ambiguities associated with it, that are fundamentally accounting issues, regarding the level of generality at which you analyze it. At the most general level, the water district clearly isn't allowed to collect more in fees in the aggregate than is necessary for it to break even from purchasing the water from someone and conducting its operations (assuming that it is a governmental entity). But, assuming that this threshold is met, the question is then how much discretion the water district has to allocate its costs, many of which are fixed costs that benefit all of the people in the water district, to particular users. It sounds from the question as if some of its costs involve purchasing water from a wholesaler, and some involve things like distributing that water to individual customers, metering usage, invoicing customers and collecting payments. Also, another question of generality is over what time period costs have to match services. At a fairly broad level of generality, perhaps it is permissible to match fees to cost on an annual basis. Certainly, the matching doesn't have to be any more specific than for an individual billing cycle, but it isn't obvious that this much precision in timing is required. Almost certainly, the water district is entitled to some deference in how it decides to allocate costs to services when there is more than one reasonable way to do so. Very likely, the water district evaluated its billing policy with its municipal attorney in light of Proposition 218 when it adopted this system and obtained an opinion of counsel that its plan was compliant. Indeed, it probably has covenants in its municipal bond offerings that require it to do so. Therefore, it is very unlikely that the water district's billing policy blatantly and unambiguously violates Proposition 218, even though it make be pushing the envelope with a billing scheme that isn't clearly allowed or clearly forbidden by court precedents that are factually similar. If that is the case, you might find a lawyer willing to bring a class action lawsuit to test the validity of the billing system, but it would likely be a long and difficult case with an uncertain outcome that the water district is more likely to win than you are, although it still might be a technical violation. Given the small stakes you have in the question with your own relatively small water bill, and the high stakes that the water district has in justifying its billing system for all of its customers, it is hard to see how this would be an economic battle for you to fight.
A creative prosecutor could probably come up with a raft of charges. But you could start with the federal wiretapping statute, 18 USC 2511, and the anti-hacking statute, 18 USC 1030. Here is an indictment brought in 2012 under the anti-hacking statute against someone who distributed and used this kind of software. Depending on the facts and the jurisdiction, this may also constitute the tort of intrusion on privacy or seclusion, a tort recognized by the Restatement (Second) and actionable in many jurisdictions. The most common test is whether the invasion would be "offensive to a reasonable person." And no, contrary to the commenter's view, a "click to accept" license is not a get out of (literal) jail free card here. Courts interpret adhesion contracts liberally to favor the signer, and outrageous terms hidden in small print are not guaranteed to be enforceable, especially if the software is clearly designed to trick people into installing it. The license terms might even hurt you, by providing evidence of your intent to use the software for perving rather than its ostensible use. This is not an exhaustive list, and there may be additional state-level statutes that apply. Bottom line: yes, this is clearly illegal, and the courts will be reluctant to let you trick people into getting away with it.
It is the use of a "menace" which creates the crime, not the nature or validity of the demand. That's not correct. You've inadvertently missed the other element of the offence: that it's an "unwarranted demand". A person is guilty of blackmail if, with a view to gain for himself or another or with intent to cause loss to another, he makes any unwarranted demand with menaces; and for this purpose a demand with menaces is unwarranted unless the person making it does so in the belief— (a) that he has reasonable grounds for making the demand; and (b) that the use of the menaces is a proper means of reinforcing the demand. https://www.legislation.gov.uk/ukpga/1968/60/section/21 For example, I may have reasonable grounds under the Consumer Rights Act to demand a refund for a faulty good. It might be sensible to moderate one's language, e.g. "If I do not receive a satisfactory response from you within 30 days of the date of this letter, I intend to issue proceedings against you in the county court without further notice. This may increase your liability for costs." vs. "If I do not receive the money from you within 30 days of the date of this letter I'll take you to the f***ing cleaners, sunshine." But the language doesn't make the demand unwarranted.