But, even though the Linux the project created git specifically for their own workflow, and is in the running for the largest and most complicated decentralized software project ever known, they still operate git.kernel.org. They still have a central master repository server.

Just because git clone gets you a first class copy of the repository doesn't mean you don't need a source of truth or a centralized master to operate and coordinate the project. Control is not the totality of the benefits of centralization, and we should not confuse the structure of the tool with the best structure of a project that uses that tool.

What they care about:

- Does it do what I need it to

- Can I access it easily

- Is it easy to navigate

- Does it work or is it buggy

- Is it slow

- Does it abuse notifications

- Is it prompting me to log in all the time

- Are there too many ads

- Can I use it on any device I have

- Does it complain about updating constantly

I don't think any of those actually has to do with being a website. The problem is that web browsers and websites didn't get a not-stupid UI for phones faster than the phone vendors could funnel everyone into their walled garden. Remember "click here for mobile" and having to develop two web interfaces? And half the time functions would be missing on one side?

I grew up in central Michigan and thought the same about the sun until I spent a few years in southern Arizona. The sun there feels like a heat lamp in summer. The low humidity makes the atmosphere absorb less energy. Although it feels like it's about 5 C cooler than it actually is because sweat evaporates so quickly, but once it gets to 43 C you actually just feel vaguely ill just going outside. Standing in the sun is just not something you do. It's a very unique experience to lick your lips and have your tongue feel cold.

Of course, neither of those were as bad as Houston in August. It was 38 C and 98 % relative humidity. And, I will point out, it had not rained. That's just what it's like. You walk outside and your glasses instantly fog up and you feel like you desperately need to shower.

It's correct everywhere else. The road sign, the municipal tax parcel GIS, the post office, Apple Maps, MapQuest, OpenStreetMaps. All of them had the correct name, except Google Maps. So she reported it through Google Maps. And reported it. And reported it. Every few months she reports it again. She's asked friends to report it as well.

It's still wrong.

She bought her house in 2015.

Eh. It's sort of like saying FreeDOS is laughable because DOSBox exists. I think that's missing the point.

> [Z]ero-day specifically compares when the white hats (vendors, system owners) and the black hats learn about the existence of a vulnerability. If white hats learn that a vulnerability exists by being subject to an in-the-wild black hat exploit of it, then it's a true zero-day.

And, again, you need to be aware that the vulnerability is the flaw or defect in the software or system (e.g., buffer overrun), and the exploit is the specific methodology that takes advantage of it (e.g., worm, malicious web request from a botnet, etc.).

Some people differentiate between a zero day vulnerability and a zero day exploit. I don't really find that is common anymore, and essentially everyone using it means zero-day exploit.

Cancer is best understood as a family of tens of thousands of diseases. They're a whole range of different genetic changes that can happen which result in similar categories of symptoms and consequences. They can also be incredibly complex, such as being the result of hundreds of stacking genetic defects acquired over a lifetime. There can be a thousand varieties of one specific type of lung cancer, and they might all react differently. Some of our solutions might work on a lot of them, but others might only work on a handful. And we're at the beginning of figuring all this out.

CRISPR may eventually allow us to genetically profile a cancer and design highly targeted medications to cure them, but we don't know yet how well it will work. It may only work on a portion of them. It may have worse outcomes than chemotherapy or radiation. It's nice to think that we're going to find a magic solution to the entire problem, but things almost never work that way. I think we're going to be able to resolve a wide range of issues, but I don't think it will really cure cancer as a whole.

The vulnerability is the exposed weakness. Vulnerabilities get fixes, and they exist without anybody knowing about them. Vulnerabilities get CVEs assigned to them.

The exploit is the means of attack. It's the specific actions or calls that let you take advantage of a vulnerability. It could be a worm, or botnet scripts, or specifically crafted data[0]. A proof of concept is not an exploit itself, but it demonstrates that the vulnerability can be exploited.

An example of a vulnerability might be a gate where the gap between the door and the jam are too wide. The exploit is a coat hanger used to lift the inside latch from outside the gate. That results in unprivileged access.

And zero-day specifically compares when the white hats (vendors, system owners) and the black hats learn about the existence of a vulnerability. If white hats learn that a vulnerability exists by being subject to an in-the-wild black hat exploit of it, then it's a true zero-day.

[0]: https://xkcd.com/327/

I understand why it's poorly understood. It's a snappy term, and people assume it means "bad" and nothing else because that's all you can get from the context. However, since most people also don't know the difference between a vulnerability and an exploit, they won't understand the definition of a zero-day when they read it.

But I'm still going to complain if a security vulnerability research company is using the term incorrectly in their own press copy. It makes them look amateurish.

It's also very easy to use pdftk to embed or attach files in a PDF using the methods defined in the PDF standard. No renaming or special knowledge required of the audience.

That said, when they tried this in the past they did it by changing the sticker price to $65k+. So, color me skeptical.

The commercialization of the engines of culture continues.

The real problem is twofold. One is that EDS had historically been a diagnosis of exclusion, and a lot of the diagnostic tests were difficult. The second is that the disorders overwhelmingly affect women, and women tend to get ignored about chronic pain and fatigue.