dadrian

You look across unrelated events that you scored similarly. In aggregate, across all things you predict as having an 8% chance to happen, 8% should actually happen.

This is awesome. I remember back in 2006 I bought every copy of MechAssault that my local Game Stop had and hoped that one was the correct revision such that it was compatible with the Krayzie Ndure softmod exploit, and used it to install Xbox Media Center (XBMC). It's from that setup that I learned how computer networking works. I credit basically my entire career with reading about softmods at the back of a Popular Science magazine.

Anyway, it's awesome that you'll eventually be able to softmod an Xbox without a specific game once the mods are integrated with this exploit. Good work!

I have 3. For about 14 years, I had 1.

Oh, that's easy. It's because Assange committed crimes that Greenwald did not.

Good for them. I am however, confused by the list of accomplishments, one of which is "wrote tests". I think this goes to show that audience matters---that list looks a lot better as items on a resume at an undergrad career fair than it looks to college admissions or even looks on a resume of someone a few years out of school.

Slack's not down, you've been fired.

It is publicly available data from Chrome's non-URL keyed metrics system. https://transparencyreport.google.com/https/overview?hl=en

If there's any vendor in the sponsor list with an ulterior motive, it's Vanta.

If an a16z repo gets enough stars, will they invest in themselves?

How long until Jen Easterly is a partner at a16z? Seems like she's on a never-ending speaking tour, rather than leading an agency.

What do you think the government does to TLS?

It is already in use in WebEx.

Off the top of my head...

- Soft-white LEDs

- Data-over-headphone-jack

- ZK-SNARKs

- Tor

- Energy-harvesting power monitors

- TCP congestion control

These all had government funding or were invented in government labs.

The peer review system is not designed to catch fraud, it's designed to catch scientific or experimental errors.

Giving up on science is such a vast overgeneralization. You could take your statement and replace "manipulated research", "scientific institutions" and "established scientific truth" with just about any negative article in any domain. You could just as easily make this statement about startups (Theranos, Juicero), or government, or religion, or suburbs, or cities...

With an XOR, if you can control bits on one of the inputs, you can deterministically change one of the bits on the outputs. That is not the case with an HKDF.

That's backwards. Profitability at scale is about the _only_ way for a cloud provider to be profitable. There's a reason you don't see a bunch of small cloud providers, the economics only work at scale.

You raise money to pay for costs of running the business. If you couldn't raise money, then only people who are already extremely rich would be able to start a business of any size, let alone one that requires deploying physical hardware in multiple regions. Good luck getting even four regions for less than $1M. The world would be far worse off if all tech businesses had to be bootstrapped.

That being said, there's certainly many businesses that raised too much money based on bullshit, had the founders take money off the top, and then have to drastically change to become sustainable, especially in the ZIRP era. But I don't see that happening here.

If you are interviewing for a senior-ish position in some specific domain, and it has a take-home, and it recommends a time limit, and you blow past that time limit because you aren't familiar with the domain, then either:

- You aren't familiar with the domain and its working as intended, you're just bad at time management.

- You're not even familiar enough with the domain to know you're doing a bad job.

- You learned the whole domain and it was a good use of time.

In any case, slogging through a take-home you're not qualified for should warrant an introspection on your part. It should still warrant a response from the company if you submit it, and it sounds like certain companies have a ghosting problem. But it's not surprising that people who spend 10 hours on something that should take 2 hours are perhaps not coming up with good solutions and not qualified for the job they're interviewing for.

If there's one thing prohibition is known for, it's lack of crime! Wait...

Those billionaires don't have it in cash, either.

> We will continue to mark HTTP as insecure.

Chrome remembers certificate click-throughs for 2 weeks. That being said, there's definitely a bunch of room for improvement with local networks that we haven't quite sorted out yet.

Believe it or not, the title began as a placeholder title before I realized it was a Google-ism for shutting things down.

In (50%) of Beta, Chrome attempts HTTPS and silently falls back to HTTP on all HTTP links. We're still poking around with opt-outs, currently if you allow insecure content via Page Info / Site Controls, we stop upgrades.

I wonder if Bard can write a show tune about how you regret what you built, but you're taking the money anyway.

Almost nothing on this list is actually positive for security, and most of the applications provided are not actually substitutes. Good luck replacing Discord with Signal.

You can mitigate things that go wrong quicker if the default lifetimes are shorter.

I migrated to Github Container Registry in less time than it took to read this blog.

Systems of Engineering Management (Larson) - Best practical advice for dealing with software engineering teams

Leading at the Speed of Growth (Catlin & Matthews) - Despite the title making me want to vomit, it has a bunch of practical advice about problems you'll encounter at various "stages" of a company, and how to identify what stage you're in.

The First 90 Days (Watkins) - Useful if you ever take on a leadership role where the current state of the organization could be described as a "shitshow".

Good Strategy / Bad Strategy (Rumelt) - Learn the difference between goals and strategy and plans.

Sorry, what? Do you expect that no company can think about what to write before they post it, or that any post about anything internal must cover all internal issues? Posts must be either all roses or a no-thought laundry list of everything bad?