cbr

See https://news.ycombinator.com/item?id=13108404

> What's puzzling is that they also bumped up the historical Zestimates

There are two things a "historical estimate" could mean:

1) What did Zillow say the value was on day X?

2) What does Zillow now think the value was on day X?

You and others seem to be thinking of (1), but I think Zillow actually is doing (2). Since the goal is to figure out what the house is worth and how its value has changed, I think (2) is actually the right metric here.

"The corps, an agency within the federal government, decided to build Olmsted with an experimental “in the wet” construction method: Hollow sections of the dam are built on the bank, skidded down to the river, towed into position and lowered into the water, where they are filled with concrete. Traditionally, a project like this would have used a coffer dam — a small temporary dam that keeps water out of the site while construction goes on in the dry.

The “in the wet” method was supposed to save time and money and minimize delays, but it did the opposite. By the time the corps realized its folly, it was too late to alter course. The novel construction process and inadequate congressional funding, among other things, have dragged the project past the quarter-century mark."

http://globalprioritiesproject.org/ kind of tries to do this

(referencing http://news.mcdonalds.com/corporate/news-stories/2013/mcdona... )

There's also the VA administration's VistA [1], open-sourced through regular FOIA requests, and written in MUMPS. [2]

[1] https://en.wikipedia.org/wiki/VistA

[2] https://en.wikipedia.org/wiki/MUMPS

JS isn't allowed in email.

(JS crypto also has issues.)

"Pareto efficiency" is a very strong claim, and it's invalidated by any single individual doing worse.

The biggest problem here is not the support cost, but that offering this kind of information gives people insight into how the algorithm works so they can better game it.

In search, email, etc there's continual competition between people trying to trick the span detection algorithm and people trying to extend the algorithm to counter them. Secrecy is a critical tool on both sides of this fight. Force transparency on the algorithm maintainers and it's output will get much worse.

Keeping the algorithm secret has downsides, but is worth it (for society at large) on balance.

(Disclosure: I work for Google, on unrelated things, and don't know anything Google-specific here.)

taneq was saying that Google Maps now shows very few street names, but your link doesn't talk about street names, and is about city names instead.

(Disclosure: I work for Google, on unrelated stuff.)

With most of these "meal replacement" products (soylent, meal squares, etc) the goal is to have 100% RDA per calorie. This means that you don't have to "make up" for them with other meals by adding some nutrient or cutting back on sugar.

It's also not a gift if it's compensation for doing work.

Web fonts are a poorly performing part of the web.

There are two fixes for this:

* Pages can send the Strict-Transport-Security header to tell the client that future visits to them should be HTTPS-only

* Pages that send that header can also ask to be included in a list that ships with the browser to handle the first-time visitor case: https://hstspreload.appspot.com/

In that situation there are three safe and legal answers:

* Replace the wiring with grounded cable. Expensive.

* Replace the outlet with a GFCI and label it "no equipment ground". Gives most of the safety benefits of a proper ground, and is up to code. Not that expensive.

* Use a cheater plug [1] and connect the external ground tab to a pipe or something else grounded.

What you're asking for is basically a cheater plug plus an ordinary power strip, sold as one integrated unit. Better to keep them separate so that people know what they're dealing with. Also, what the poster upthread was describing didn't have a grounding tab, so there was no way to hook it up safely.

(The landlord isn't required to set up grounded outlets out of a general principle that you only need to bring things up to code when you're modifying it, and that something that was legal at the time it was installed stays so. Your unit could legally have knob-and-tube wiring if it's old enough!)

[1] https://en.wikipedia.org/wiki/Cheater_plug

They're describing a power strip that has a 2-prong wall connector and offers three 3-prong outlets. This is dangerous, because equipment with 3-prong plugs needs to be grounded, and this power strip misleads you into thinking you've done that.

    I HATE touchpads, as the cursor tends to shoot off into
    space when I accidentally touch it with the heel of my
    hand when typing.

Have you used a macbook touchpad? I hated this about touchpads, got a macbook from work in ~2010, and have never had this happen to me in 6+ years of using mine.

I had thought people we're pretty excited about the new Pixel phone? Like http://www.theverge.com/2016/10/18/13304090/google-pixel-pho... etc.

Or am I just in a bubble as a Google employee, where I hear disproportionately good responses to our stuff?

The spec has been moving along: http://wicg.github.io/ContentPerformancePolicy/

Right now there are a lot of things that specs let you do that will make your page slow, like running a lot of js in the scroll event handler, or just including too much js overall. If you read the current proposal [1] the idea is that the site could make promises not to do various kinds of slow things, and the browser could enforce that.

[1] http://wicg.github.io/ContentPerformancePolicy/

That's what made it jump out to me too! But the key thing is that one number is in linear units and the other is in square units. So for any linear unit you choose (mm, in, km, furlongs, ...) an equilateral triangle with perimeter sqrt(432) units will have area sqrt(432) square units.

    So you dirty the system where its supposed to be
    installed, a server, with gcc, make and friends?

That's the way nginx is traditionally installed, and we're shipping an nginx plugin.

    State so on your documentation/page before telling the
    user curl | bash

The first thing the install script does is check if you're on a supported system, and if not it exits. Since the vast majority of people running the script are on supported systems, this seems better than putting a lot of warnings up front.

    Your script does not support transactional
    installations, as it is it can break at any point
    in the script leave the target system broken/dirty

By default the script only builds ngx_pagespeed, and doesn't install it. If you ask it to handle the install, it call's nginx's "make install", which again is the standard way you install nginx.

    An equilateral triangle whose area and perimeter are
    equal has the area of exactly the square root of 432.

Let's say we have an equilateral triangle with a perimeter of 3x units. Then each side is x units, and the area is sqrt(3) * x^2 / 4 square units. So we set:

            3x = sqrt(3) * x^2 / 4
             3 = sqrt(3) * x / 4
   3*4/sqrt(3) = x
    12/sqrt(3) = x

Then the area is:

    sqrt(3) * (12/sqrt(3))^2 / 4
    sqrt(3) * 144 / 12
    sqrt(3) * 12
    sqrt(3) * sqrt(144)
    sqrt(432)

Fun!

Good for them! A recall is the responsible option at this point, and I hope other manufacturers do the same.

Hi! I maintain a "curl | bash" installer script [1][2].

    such as only working on specific variants of Ubuntu,
    with specific packages installed in specific version,
    and/or RedHat

Our installer is capable of automatically installing dependencies on current versions of Debian, Ubuntu, and CentOS. If you're running something else it prints out "This doesn't appear to be a deb-based distro or an rpm-based one. Not going to be able to install dependencies. Please install dependencies manually and rerun with --no-deps-check.", which seems pretty reasonable to me?

    submit this data to that platform as an
    debian/{control,etc} to make a .deb or specfile for
    .rpm or PKGBUILD or whatever, and use the platforms
    _build tools_ to generate a platform specific package
    - be a package mantainer if you have to

Building a binary package for ngx_pagespeed isn't really practical. It needs to depend on nginx, but nginx doesn't have an ABI, so it needs to be built from source alongside your existing nginx or as part of a new nginx install. Getting into the distributions, so that they can build the ngx_pagespeed module at the same time as they build their main nginx would work, and is somewhere I would like to be eventually, but requires a lot of coordination with distros.

    Another side effect of telling your users to curl | bash,
    is I wont ever use your software. You didnt make the
    effort to do the right thing with packaging, why would
    you have done any better for whatever it is youre trying
    to do with your shit software?

I do think what we've done in this case is "the right thing" in terms of how we should be spending our development time. Our installation page does still offer manual install instructions, however, for people who would rather not run a script.

[1] https://developers.google.com/speed/pagespeed/module/build_n...

[2] https://ngxpagespeed.com/install

Yes, Southwest asking Google not to include their fares in results seems likely to me.

(This thread started with me arguing that "it costs money to be there" was not the reason Southwest flight prices aren't in Google.)

Even then, though, I'd still be very surprised if Google would respond to an offer of seat availability data from Southwest with "sorry, we won't let people search it unless you pay us".

Are you trying to draw a distinction between "prices" and "fares", or just "will likely" vs "will"?

Are you finding the same specific flights have different prices on the two services, or are you finding that Hipmunk is able to find flights that Google doesn't?

(Disclaimer: I work for Google, on an unrelated project.)

I'd be very surprised if Google Flights wanted Southwest to pay for inclusion. It already lists Southwest flights with a note "Prices are not available for: Southwest. Flights with unknown prices are at the end of the list." Instead it really sounds like it's Southwest not wanting it to be easy for people to comparison shop.

(Disclaimer: I work for Google, on an unrelated project.)