hunter2_

Back already. But seeing "reason: overflow" in the response made me wonder if it was related to the recent php vulnerability, but probably just a coincidence.

Ethernet drop for the freezer shouldn't get installed until this question has an answer.

Wait, it has its own cellular modem? Nevermind, then.

Not unlike how in the trades, a tee is T-shaped, a wye is Y-shaped, a delta is Δ-shaped. Spelled-out letters aren't always geometric metaphors, but it's a thing.

Then you've got the first syllable of Ω (omega) being a homophone of Ohm, for what that's worth. From there we have ℧ (mho) for conductance... It's all quite clever. But I digress; I'll get back to emceeing and deejaying, cueing these elpees after a quick pee, okay?

> you'd still have to pay your electricity bill.

I should only have to pay 1/3 of what it adds to my bill, given that it's 1/3 as efficient as a heat pump. And that coefficient is to be adjusted as outside temp changes (assuming air source heat pump; water source would have a stable COP).

Easier said than done, but if you water-cool the GPU just upstream of your domestic water heater, it wouldn't be a bad thing. Perhaps using coolant and a counterflow heat exchanger, rather than the potable water, but the point stands. Would just need a secondary tank as a buffer (able to soak up heat from the GPU at all times, even when there's no demand for hot water) which then flushes in when demand exists.

"repeated use" seems to be doing the mitigation work here, though it does seem unusual that someone offended by the repetition would be unoffended by a one-off.

What is the "good" when considering the lack of aggressive truncation/overflow concerns here?

While that might be the case, best to normalize that: Title Normalizers are Crap.

So long as the "getting" doesn't consist of circumventing something that is ostensibly a security mechanism, such as a URL that had never been presented to you by the server but is fairly easily guessed.

In a place where recording audio requires consent from all parties, I don't think it matters whether "all the processing is on-device" given that the law was probably written with tape recorders in mind. If I buy a device that can record audio, and place it in my home where unsuspecting guests are recorded by it, whether that recording is transmitted to the manufacturer or stays within my home seems irrelevant.

On the one hand, I wouldn't expect too many variations here (the vast majority of devices probably use 48 kHz and 24-bit output, a few use 44.1 kHz and/or 16-bit, etc.) but just like DPR and all the other properties with a very small set of popular values in practice, you only need a bit or two from each measurement to eventually have a high quality fingerprint.

This is a huge stretch, but if this problem exists in not only the PC versions of Chrome/Firefox but also the Android/iOS versions, then theoretically the app store reviewers could flag the browsers for facilitating this behavior against app store guidelines. In practice, apps of such caliber as popular browsers might be a bit above such reviewers' pay grade, so to speak.

Does anyone else get tripped up by the word "avoid" being positioned to apply to each item in the series, but then logically it must only apply to some (the first and second out of 3) items?

{ avoid meanings, avoid affiliations, avoid fitting }

My solution is generally to repeat the word for each item that needs it, but I can see how the repetitiveness isn't great either.

No, I've never seen Google Photos reflected in any Google Drive interface (web, OS integration, etc.) which on the one hand makes sense (think of Google Photos more like a database-driven black box app than a hierarchical filesystem) but on the other hand Google Drive does show gdocs, gsheets, etc. (which is also sort of a black box app, as the "files" seen in GDrive are merely lightweight stubs).

Only in storage quota views do Photos and Drive (and Gmail, etc.) commingle.