timdierks

MP3 audio is usually encoded at rates in the hundreds of kilobits per second (topping out at about 320 kbps). You can get pretty good audio quality at 128 kbps, and adequate voice mono quality at 64 kbps. Thus, 64 to 320 thousand bits per second per stream depending on desired quality.

2 Gbps is 2 billion bits per second. (Thus, 2000 Mbps). Even if you lost half of the available port bandwidth to link overhead, etc., you could host somewhere between three thousand and fifteen thousand simultaneous MP3 streams with that much bandwidth.

Roger G. Johnston worked in security at Los Alamos and Argonne National Laboratories and collected this set of maxims (funny but painfully true) in 2009.

This is the right math if he's stuck there for 5 years, but his opportunity cost is lower if he can exit the role earlier if the company isn't trending towards the exit he wants.

Nest cameras work over WiFi (as far as I know). Presumably you can defeat them with a spark gap or a microwave you've jimmied to run with the door open. Vulnerabilities against technical hackers sending hand-crafted artisanal Bluetooth packets are laughably irrelevant.

Let's say an human with height 170cm and hip width of 85cm (these are between the averages men & women) gives a rectangular area of about 1.4 m^2; the head and legs aren't as wide as the hips, but this doesn't include the arms, so let's take it as a guess of the weight-bearing area for a prone or supine human. This area times 5 psi is more than 5,000 kg (more than 11,000 lbs). So yes, I think it would kill someone.

Jack Handey is an actual person, the writer of the one-liners GP refers to: https://en.wikipedia.org/wiki/Jack_Handey (I'm not sure if he recorded the voiceover performance or not). Al Franken is a different actual person who also worked on Saturday Night Live and who is now a US Senator.

@mar1, I've forwarded your interest in finding a job to our security recruiting lead. We don't have a relevant office in the desired location, but happy to discuss. Feel free to reach out, my email is dierks@google.com.

Red Plenty (by Francis Spufford), a novel about economic planning in the USSR, is an excellent read and characterizes the information problems at the core of the failure of central planning.

"70 cents [in revenue was enough to] put me on the Mac App Store Charts". No different from "100,000 downloads made me #1 on the list".

Strongly disagree. Mom and pop businesses get owned all the time and close as a result (see Krebs On Security for cites). The economics of online attacks mean that even smallish targets are not obscure enough to be safe.

Disclosure: I work on security at Google.

Did you mean for this to be somewhere else?

Nope, real-world solutions to monitor air ducts and other spaces that need to be open but which shouldn't have people in them.

See also https://news.ycombinator.com/item?id=13375535. I work on Cloud KMS, happy to answer questions.

While I understand the rationale for the meme (I, too, was a Google Reader user), I think you will find that Google's ongoing support for Cloud APIs is robust. Any potential cloud platform customer has to decide if they want to depend on a service or control everything themselves; there are tradeoffs either way.

Cloud KMS doesn't implement an open standard (there aren't a number of good open standards in the space, KMIP is probably the only candidate I'm familiar with), but use of the current functionality shouldn't be very hard to port to some other API. (Although, given the dependency on keys, etc., this may not apply to moving any reposed data, that's fundamentally more challenging.)

[repeated disclaimer: I work on the product]

I work on Cloud KMS at Google, AMA.

What would you have it do? Solving the general dataflow problem so you identify out-of-bounds array accesses at compile-time is impossible (equivalent to the halting problem), so would it really be worth investing in identifying in finding them in simpler cases, particularly since simple cases are much less likely to make it to deployment anyway?

And if you don't find the problem before runtime, what's a better strategy than panicking here?

You can share folders; also, check out Team Drive. https://techcrunch.com/2016/11/21/google-opens-up-its-new-pr...

Why would you think StackOverflow doesn't care about ad revenue? They both run ads and want to make money by helping recruiters reach logged in users.

In utf8, these characters are all encoded as two bytes. So this encoding makes the byte count twice as long, it's no more efficient (in bytes) than hex encoding.

Charge-only Mini USB connectors are a different question. They're possible to build, but non-compliant. Charge-only USB C cables are part of the standard. The difference is that you can only blame cable confusion problems on the standard in the latter case.

This is pretty, but it's all statistical outliers; every highlighted spot is a small city where random fluctuations above a low baseline are most likely to generate seemingly-impressive spikes in query volume.

Interesting because the value of intangibles like software is a huge distortion on accounting "book value" under GAAP: more than half of US company spending is on building intangible assets which have zero book value on their balance sheets. Furthermore, the distinction between buying software and SaaS models have material accounting impact.

It's $300/year from what I can see. Not free, but if you think it's a valuable part of your design, a small cost, unless you just don't have a viable business in the first place.

It does happen at sunrise roughly 18 days before and after the winter solstice. (Dec 3 and Jan 10)

The linked article treats revenue as value, which is obvious BS.

The value of Lucas to Disney is much higher than the $4B price tag either Lucas or UFC yielded, but a lot of that stems from Disney's amazing ability to execute on it. UFC seems more capable of standing alone as a business.

Doesn't really change anything. If you make it so the police won't stop you for a broken tail light, will you keep it so they can stop you for driving with an expired inspection sticker? If so, you have to accept that the consequence may be death for a person who refuses to pull over because their inspection was expired because they had a broken tail light.

If your passwords are going to be available to user mode processes without a privileged interactive password prompt, they're going to be available. This is how it's designed and is necessary for the current user experience (that apps you are running have access to your key chain secrets for unlocked key chains).

Crippling tools to make it look like the passwords are hidden or further secured is just security theater.

You elided the relevant sentence:

> In cases where you really want to disable autofill, our suggestion at this point is to utilize the autocomplete attribute to give valid, semantic meaning to your fields. If we encounter an autocomplete attribute that we don't recognize, we won't try and fill it.

They're saying that they don't autofill when they see autocomplete values which Chrome doesn't recognize, so if you don't want autofill, they suggest you just put in a description of what this field is, which won't be recognized. The functionality is the same as if you put in autocomplete="foobarbazquux", but it's better-described.

It's not for the developer to decide any more than the browser. It's up to the user.

Direct PDF: https://research.google.com/pubs/archive/44860.pdf

Usenix URL: https://www.usenix.org/publications/login/spring2016/osborn