That fact does not change the point of the individual to which you replied. Regardless of whether the clauses in the EULA are 100% legal, some mixture or 100% illegal, the entire EULA is a "one sided rule-book dictated completely by one side". You, the person held to the EULA's rules, do not get to negotiate on the individual points. You simply have a "take it or go away" set of options.
You're talking about contracts of adhesion and they are overwhelmingly common for B2C agreements. Most red-lining of contracts only happens in high-value B2B transactions where the sums of money involved are enough that it makes sense to bring lawyers into the loop.
If the product has any serious audience / traction, it becomes profitable to scan its EULA for illegal clauses, and sue the company for damages (and maybe extra punishment for breaking the law).
The fact that 100% of its users, except the litigant, skimmed through the EULA and did not notice anything does not relieve the company from the responsibility.
when you already pay for the device and a contract, then surprise now that you have skin and flesh in the game, you HAVE TO agree to this EULA or your property is a brick and we keep your money.
that is defined as extortion, but labled as onboarding.
> is this one of these things where Meta doesn't want the responsibility for this
Very likely, given the legal liability they are already facing from the "addictive" court cases that are turning against them. Moving the liability for "age verification" away means they will not also be facing a huge number of court cases accusing them of showing an underage person adult age content provided they followed the law's proscribed "ask the OS for the user's age" requirements.
Also, note that only a few months ago Zuckerberg was in court testifying that the single best place to perform "age verification" was in the operating system of a device. Now, like mushrooms after a long rain, at roughly the same time up pop bills in nearly every statehouse, Congress, even Brazil, that all read nearly identically and that all are so broad as to require "the OS in anything with a CPU do age verification". The nearly identical text in each highly implies a single lobbying entity is behind all of them (it would be quite the coincidence that 50 state houses, plus Congress and Brazil, all write nearly identical bills independently). And the connection back to Zuck's court testimony of "age verification is best done in the OS" highly implies that the single lobbying entity is Meta, or funded by Meta to obtain this outcome.
For jet fuel? The article does not say, but if they are correct in predicting shortages in six weeks, then the stockpile (if any) is not terribly large.
> Isn't the entire US national strategic oil reserve only enough for like 1 month of US usage?
In any case, whatever it is, crude oil is not yet jet fuel. The crude has to be refined to output jet fuel (and other oil byproducts), and some amount of gulf refinery capacity is also offline due to one or both of damage or inability to export via sea through the strait.
"Don't be evil" was dropped after the DoubleClick acquisition completed their internal takeover of the old "Don't be evil" Google (Google purportedly purchased DoubleClick, in reality they 'did' purchase them, but then the old DoubleClick advertisers slowly took over old Google from the inside out).
What is called "Google" today is actually the old, fully evil, advertising firm "DoubleClick" pretending to be "Google" to make use of the goodwill the "Google" brand name used to have attached to it.
Couldn't be more simplistic. Of course a three trillion dollar Google would behave differently than a 2008 Google with or without DoubleClick.
Even today, I would argue an average sample of Googlers will likely think slightly differently about these things than an average sample of Facebook employees; but of course both will have to respond to influence from the external world: i.e. customer, society, govt.
The problem is that when the lobbyists are pitching these builds to the local town councils, the "create X jobs" part of the marketing is very carefully worded to heavily imply "X long term jobs will be created" while also not actually directly saying "X long term jobs will be created". They want the council members thinking X long term jobs, but want to avoid legal liability for lying later when the reality of X was 99% temporary jobs lasting 6-12 months and 1% long term jobs for the community.
And few council members seem to have been snookered enough yet that they know to ask the marketing lobbyist the pointed question: "How many of those X jobs are long term and will persist after construction and build-out is completed?".
> plus they get to point the finger at someone else for age issues.
This is the real benefit to Meta/FB/etc. that many seem to overlook. Meta/FB/etc. are already staring down a lot of court cases related to "addicting youngsters" to their product (and potentially a lot [i.e. billions of dollars] of payout for settlements or penalties in cases that side against them).
But, if they can get the government to mandate that the operating system is responsible for verifying a user's age, they get to avoid liability (i.e., more billions of dollars) for serving anything from their properties to an underage user if the OS tells them that the user is "old enough" for whatever they served. So long as Meta follows the law and asks the OS "is this user old enough" and if the OS replies "old enough" then the liability for mistakes in the age identification shifts to the OS provider and away from Meta/etc.
The part that is odd here is why Microsoft, Apple and Google (the "OS providers" truly being targeted) are not massively lobbying against this due to the legal liability risk that Meta is trying to shift over to them.
This is likely because of Zuck's testimony in the very recent court case where he testified exactly that the "best place" to do "age verification" was in the operating system.
This was but a few weeks before all these, largely very identical sounding bills, suddenly started appearing in state houses across the USA.
Try again, but have curl provide a user agent string from one of the real browsers. You'll likely find that the request goes through.
reply