124816

It's not lazy framing, this is what "journalism" is now. Push your agenda as far as you can, misrepresenting as many facts as you like. At the very end of your story -- which >85% will never get to -- walk back your misdirections with a paragraph or two of facts, right next to your bolded "sign up" text. None of this is unintentional or accidental.

You're comparing water taken from the Floridian aquifer (lots of minerals like sulphur, which isn't known for tasting great) with Seattle (water from the mountains), SF (hetch hetchy), etc. I just want to suggest that maybe the taste of water is one of the things that cannot be naively mapped to a linearized space of red vs blue.

> wonder if the sync feature will be open source

According to [1] they don't plan to open source it due to "business considerations."

I'm not against people making a buck, but as far as I understand this isn't permitted by the AGPL, which logseq's current authors are bound to as much as anyone else. (Unless they have all past contributors grant them a secondary license.)

It's likely the sync protocol will be reimplemented for self-hosting, but I'd assume the mobile apps will hardcode the server address to encourage use of their paid sync service.

1: https://discuss.logseq.com/t/what-is-the-logseq-open-source-...

Usually beyond the range you normally cook at, but definitely achievable if you leave a pan unattended for a minute, or use it with insufficient coverage. Pet birds are extremely vulnerable, and there's plenty of stories of them dying due to nonstick cookware. I get little benefit from nonstick cookware, so for me the "canary in the kitchen" aspect was enough reason to eliminate it from the house.

There's such a thing as overregulation, but when industry fails to act in an upstanding manner they are playing chicken with regulators. Here's the result. The way to avoid this is create an industry body to develop a standard and 'regulate' themselves. It looks bad when you do that, then also flaunt the standard for greater profit/market position.

Phantom braking includes self-driving/cruise and ADAS, e.g. "What is phantom braking"

> Phantom braking is a term used to describe when an advanced driver assistance system (ADAS) – or a self-driving system – applies the brakes for no good reason

(AEB is part of ADAS)

> What behavior are you referring to?

Automatic Emergency Braking. You cannot turn off AEB persistently.

> I'm not aware of any feature that requires me to accelerate or brake to prevent the car from stopping itself

Before the car emergency brakes, it will warn you via "Forward Collision Warning"; the screen will show the object it thinks you're about to hit in red. You can set this to "Late" to reduce false positives -- but if you do, you'll have less time to take action yourself. So now I set it to Early.

After a FCW, you have a small amount of time to do something before the car will do something for you. The M3 manual describes AEB here:

https://www.tesla.com/ownersmanual/model3/en_us/GUID-8EA7EF1...

It also explains "Automatic Emergency Braking is always enabled when you start Model 3. To disable it for your current drive, touch Controls > Autopilot > Automatic Emergency Braking."

You cannot turn this behavior off persistently -- you need to open car settings and disable it every time you leave Park. My guess is that some jurisdictions mandate this behavior.

When this "feature" triggers you have a short window in which to do _something_ to tell the car that you are paying attention. Your options are either: accellerate or brake. If you do nothing the car may apply full brakes and bring you to a full stop, regardless what is behind you.

> Reports of “phantom braking” first surfaced last fall

This has been happening for much longer than that -- at least as early as Winter 2019, when I unintentionally brake checked a Prius after merging while going over 101 @ Rengstorf.

There can be other causes besides noise exposure, like TMJ/teeth grinding which can affect the nerves.

> IIRC only triggering the "audible ring" leaves a trace on the phone (a notification + the obvious sound), to check if someone used FMP for tracking one has to dive deep into the Google Activity Logs.

Not true, a notification is shown whenever the device is located.

Though if someone can "sneak a 2nd Google Account" onto your phone they can probably install something more nefarious and less observable.

> If there was a serious security vulnerability in one version of the software, would users be stuck waiting six months (or possibly forever) to get a patch?

They'd probably have to release security fixes for each of the currently active major versions. (Which is probably all of them.) Having the carriers be responsible for pushing security fixes would hardly make it a quick update though.

> This is not a good thing, in my opinion.

This is extremely common, and not at all unique to Ruby. For example, providing defaults for parameters is perhaps the most common and simplest form of this.

Whenever a library is used by wildly different clients, there is a good chance the API it chooses will be better suited to one or the other. The same Net::HTTP is presumably used for the simplest of uses, maybe 5 line download scripts, and the most complex of cases, perhaps forwarding http requests with all headers intact.

In general I go by "minimal, but complete"; but for widely used libraries that have clients of very different complexities, it makes sense to provide a simple API for convenience. I'd rather not be specifying the client headers, user agent, supported encodings, etc, etc each time I want to fetch a file over http.

Except 240 in base 10 in 1040 in base 6. (When moving to a lower base the number will always 'look' higher.)

> one dies within 24 hours

Is it really correct to interpret that as "dies in exactly 24 hours"?

Edit: My solution, which assumes that after tasting wine it could take any time between 0 and 24h to die; and that it could vary between tastings:

Given N slaves, you can test 2^N wines in a single iteration, as so:

  - A set of size N has 2**N distinct sub-sets.
  - Have each distinct sub-set taste a different wine.
  - After 24h, everyone who drank the poisoned wine will be dead, and,
    provided you took notes about which set consumed which wine, you
    can look up which wine they drank.
  - (Note also, you leave one wine untasted; if nobody dies, it is the
     poisoned one.)

For our first iteration, we have each set taste multiple wines, like so:

  - The set with five slaves will taste a single wine.
  - Sets with four slaves will taste 2 wines.
  - Sets with three slaves will taste 4 wines.
  - Sets with two slaves will taste 8 wines.
  - Sets with one slave will taste 16 wines.
  - We leave 32 wines untouched.

Of course, in general: a set with N slaves will taste 2^(5 - N) wines.

After 24 hours, all slaves who drank poisoned wine will be dead, and we will have the following possible states:

  - One slave is dead. We know the 16 wines he drank, and we have 4
    slaves left. As shown above, we can easily determine which of
    the 16 wines is poisoned in a single iteration.
  - N slaves are dead. We know which 2**(5-N) wines they drank, and
    we have 5-N slaves left. So we can easily determine which of
    the 2**(5-N) wines is poisoned in a single iteration.

Note that N = 0 is a valid case above.

So, we need to calculate how many wines we can test in this manner. Going through each set:

  - 5 choose 1 * 16 = 80
  - 5 choose 2 * 8 = 80
  - 5 choose 3 * 4 = 40
  - 5 choose 4 * 2 = 10
  - The one wine that all slaves drink the first time.
  - The 32 wines none of them drink the second time.

The sum is 243. Garçon!!! Fetch three more barrels!

Especially since they're using the primes to encode N = 26 independent variables within a single number. On any modern CPU, you already have 32 (or more) independent variables in each number, they just happen to be called bits. And you can test them and set them in much simpler and faster ways than integer multiplication and mod.

> you see ads on top of and around television using Google TV

No you don't.

We currently have large excesses of power at nighttime, (production cannot be scaled down and back up in a 24hr period) so the effect could be mitigated by that.

More like "If you shout loudly in your apartment, expect others to hear you."

Also, there are really good free alternatives: googletest/gmock supports Windows, linux, and (I think) Mac.

The interesting feature appears to be 'Test "untestable" code such as statics, globals and non-virtual methods.'

I'm not sure how/if this could be done within vanilla C++, though maybe you could write a GCC/clang plugin to allow hooking of everything.

> Imagine if your car had a safety mode that could watch out for potential accidents and prevent them even with a human driver.

Well, if my car would do that I'd certainly drive to the bar more often. I'd want the fully autonomous "drive me home, Jeeves" system though.

I think it's more likely that someone high enough up though it was "cool", decided how "cool" they thought it was (1M? 10M? 50M?) and then approved the project.

> The software needs to be tied to the hardware because the carriers are completely incompetent at software

AFAIK, the real reason is that there is no standardized design for phones, whereas most desktop/laptop/servers look basically the same to the OS.

"Sony is expected to launch a line of Google TV-powered Bravia HDTVs sometime this month"

Sounds like you won't need an extra box if you have a new tv. As far as the remote -- I'm guessing they're going for "one remote to rule them all," with GTV driving all the other boxes you might have.

I thought this thing was her attempt to do so.

Has exooglers working on it I think, does that count? :)

> It just strikes me as a very broken interviewing system when you have developers interviewing sysadmins.

Sounds like your recruiter messed up.

Did you ever see the full quote of the "change your name" stuff?

> Mr. Schmidt is surely right, though, that the questions go far beyond Google. "I don't believe society understands what happens when everything is available, knowable and recorded by everyone all the time," he says. He predicts, apparently seriously, that every young person one day will be entitled automatically to change his or her name on reaching adulthood in order to disown youthful hijinks stored on their friends' social media sites.

Which makes sense to me. Hell, I wish I could delete some videos and/or photos of me on various sites.

Lately Schmidt has been making statements like this though; they are reasonable when complete, but some reporters snip out five words (or, just paraphrase or interpret) and create a news storm. CEOs are supposed to be good at avoiding that sort of thing.

> equivalent HIPPA act for ALL data personally identifiable

We ought to start with getting the same level of laws for voip, IM, and email that phone and mail have. "All PII" is too vague, but those seem like a slam dunk.

> made an educated guess

Grandparent deleted their post, but, assuming they just said "they correlated across IP" -- it's actually easy to guess, since the snoop would be able to detect and ignore a NAT IP -- it would be accessing thousands of accounts.

AFAIK Google's SRE's are more fancy sysadmins than performance engineers. Sysadmins often have the keys to the kingdom, though one would hope a sysadmin on project X only has the keys to project X.

Yep, GA used to have the occasional problem with that, though I've been told some of it was due to a bug in the browser (Firefox's) code that decided what to put in the "Waiting for xyz..." spot -- if that's what you're referring to.

(Something about that bar not being updated until the first byte of the stream was read -- so if a static.foo.com was hanging connections, it would get stuck blaming whatever loaded right before it.)

GA now has asynchronous tracking though, which solves this pretty nicely. Though I'm not a JS guy, my understanding of it is that instead of sourcing the script and then issuing the tracking calls, you put some instructions into a global variable, and then source the script. Nothing blocks on the script's loading, so even if GA is down the rest of the page is supposed to load correctly. Once the GA script loads, it looks at the global and runs the tracking commands.

I think drosenthal is talking about sampling the number of hits you send to analytics. GA's tracking api supports this:

http://code.google.com/apis/analytics/docs/gaJS/gaJSApiBasic...