sjbach

Transit encryption requires that both sides are game. Google always supports it, but the server on the other side may not.

The NPR chart may also be misleading; it's unclear from the notes. There was ~60% inflation between 1992 and 2011.

A salient bit:

  [Eric] Grosse echoed comments from other Google officials, saying that the company
  resists government surveillance and has never weakened its encryption systems to
  make snooping easier — as some companies reportedly have, according to the Snowden
  documents detailed by the Times and the Guardian on Thursday.

  “This is a just a point of personal honor,” Grosse said. “It will not happen here.”

Re: maps, you can revert to "classic" by clicking on the gear.

If you're asking about NSLs to Google, you can see the ranges on this page: http://www.google.com/transparencyreport/userdatarequests/US...

These aren't aggregated into the counts shown in the table you linked. http://www.google.com/transparencyreport/userdatarequests/co...

Warning: article written by Jonah Lehrer. It's probably still a good read, but that spoils it for me.

Yes, there are 20% projects.

I'm not sure if I can assuage your anger, but the Transparency Report is upfront that there are reasons not all requests for user data are disclosed. The data isn't purported to be comprehensive, though we'd like it to be as comprehensive as possible.

http://www.google.com/transparencyreport/userdatarequests/fa... http://www.google.com/transparencyreport/userdatarequests/le...

See:

http://www.google.com/transparencyreport/traffic/faq/#do_the...

http://www.google.com/transparencyreport/traffic/faq/#how_do...

Here's the Google Transparency Report page that features ongoing developments involving this disruption:

http://www.google.com/transparencyreport/traffic/disruptions...

(This page is distinct from the time series graph linked in another comment.)

"Other" is as compared to search warrants and subpoenas, i.e. it's describing the vehicle of the request rather than the reason for the request. It's defined, loosely, in a tooltip: "Includes court orders issued under ECPA by a judge and other court-issued legal process."

Google's blog post: http://googleblog.blogspot.com/2013/01/transparency-report-w...

Khan Academy has a pretty good series of introductory videos:

http://www.khanacademy.org/math/statistics

That punishes users of Google search who want to find these titles.

The data is fairly close to realtime, with caveats. The time series chart widget is a little dodgy, though, so it's sometimes difficult to see things on the margin. We're working on putting something better in place.

The casual negativity in the headline is really too bad. I kind-of enjoyed the video, even though I'd been primed not to.

How about a way to retrieve comments or post ID for a given story URL? I often save articles and read them days or weeks later, and it would be nice if there were a simple way to find the associated HN discussion without risking upvote/story submission using the bookmarklet.

> Now try the question again, in what function or macro is the highlighted line located in? Was it easier to answer this time?

No? In either case, if it were me I'd highlight the previous close-paren (whether it's on its own line or not) to see what form it associates with. I'd do the same thing with a close-brace in C++ or an end token in Ruby. Long code blocks are a problem of every language, not just Lisp.

I'm a current ITAer working on QPX -- by lines of code, QPX is probably actually split pretty evenly between C++ and Lisp. But accounting for verbosity of C++, the logic is heavily on the Lisp side. I think anyone on my team would consider himself to be a Lisp developer before anything else.

Not so. Most of QPX and RES is Lisp.

Oh, and also a version for Emacs: http://www.emacswiki.org/emacs/LustyExplorer

I wrote a snappy Ruby-based Vim plugin called LustyExplorer which does fuzzy/flex matching for opening files and switching buffers: http://www.vim.org/scripts/script.php?script_id=1890