[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.”
Some folks are inclined to distrust Google, but there are people here who really, really care about security.
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.
"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."
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.
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.