3,616 karma · joined August 15, 2008
But the OP says this driver's car was model year 2020, which makes it HW3. All versions of FSD for HW3 (including 14.1 lite, the latest version, which came out after this incident) will stop in the lane with hazards on: https://x.com/JonBbC_TechGeek/status/2086347029018501183
It's available on Amazon in doses as low as 100mcg: https://www.amazon.com/dp/B08MJL2GTC Are you saying this because you believe the correct dose is on the order of double-digit mcg, or because you're under the impression that the lowest available dose is single-digit mg?
I find it bizarre that they felt the need to specify "Asian". What does that have to do with anything?
And it doesn't violate the PostgreSQL license to license the rewrite more restrictively. That's part of what makes MIT-style licenses less restrictive than the GPL or AGPL: they allow for more-restrictive relicensing.
There's even a billboard 979 miles away in Arizona: https://stock.adobe.com/images/eloy-az-nov-23-2024-buc-ee-s-...
[0] https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/COR...
User visits A.com, types in their username and password, and a cookie is set in their browser. The browser will send that cookie back to A.com with all subsequent requests, and A.com's server will use it to enable access to the user's account.
Now the user visits B.com, which makes a request to A.com/private_user_data. The user's cookie is sent with this request, so A.com will respond with (and B.com will receive) the user's private data without the user consenting to this at all (not even in a "misguided" way).
Is it? I can't find a trademark registration on the USPTO site.
function foo() {
return function() { };
}
console.log(foo() === foo()); // This must log `false` in a compliant implementation>We won’t give notice when legally prohibited under the terms of the request.
The post states that his lawyer has reviewed the subpoena, but doesn't mention whether or not it contained a non-disclosure order. That's an important detail to address if the claim is that Google acted against its own policy.
Running 100,000 `SELECT 1` queries:
PostgreSQL (localhost): 2.84 seconds
PostgreSQL (Unix socket): 1.93 seconds
SQLite (in-memory): 0.07 seconds
SQLite (tempfile): 0.06 seconds
(https://gist.github.com/leifkb/b940b8cdd8e0432cc58670bbc0c33...) Running 100,000 `SELECT 1` queries:
PostgreSQL (localhost): 2.71 seconds
SQLite (in-memory): 0.07 seconds
SQLite (tempfile): 0.07 seconds
(https://gist.github.com/leifkb/d8778422d450d9a3f103ed43258cc...) Running 100,000 `SELECT 1` queries:
PostgreSQL (localhost): 2.77 seconds
SQLite (in-memory): 0.07 seconds
(https://gist.github.com/leifkb/1ad16a741fd061216f074aedf1eca...)That defense didn't do too well in another case: https://www.courthousenews.com/third-circuit-backs-new-jerse...
Apparently that's not a joke anymore?!
Note that my link is dated 2023, whereas Wikipedia says that Microsoft Edit was first released in 2025: https://en.wikipedia.org/wiki/MS-DOS_Editor