calfuris

You are entirely unaffected by this, because you registered a 2nd-level domain. The problem is for the people who registered 3rd-level domains (john.smith.name). If you're wondering why anyone would do that, it's because it was originally the only option if you wanted a .name domain.

That is exactly the point of the comment you're responding to. "Why do you assume that [OEMs pay much less than retail]?" Well, $200 Windows laptops exist, and $140 of that going to a Windows license is not a credible idea.

It puts a floor on the player's skill. That's not the same as being easier. There are game states that are certainly winnable without hard mode rules but do not allow the player to force a win in hard mode.

I needed directions to a family member's house after she moved. Clicked on her address from the text message, and Google tried to send me to a real estate agent's office instead.

Out of sync with each other, or are they drifting together in lockstep? In the latter case, yes, that's the most likely explanation.

A problem in NP can have a (positive) solution verified in polynomial time. That's it. Requiring more than polynomial time to solve isn't part of the definition, and in fact it's an open question whether any problems in NP require more than polynomial time to solve.

Every single problem in P is in NP. What is believed but unproven is that some problems in NP are not in P.

Hard mode forces most people to play smarter than they usually would. I'm not sure if that's the same as being easier. Hard mode is certainly harder for a skilled player, because that player could play normal mode as if it were hard mode but without having to worry about avoiding hard mode traps like _IGHT or SHA_E--if they encounter such a scenario they can just play known-bad words that check several possible solutions at once (e.g. FIRES for _IGHT to check FIGHT/RIGHT/EIGHT/SIGHT).

I don't see the contradiction, unless you believe that the grandparent comment was written by an LLM.

The inclusion of a timestamp in v7 makes collisions impossible unless the generating systems think that the time is the same down to the millisecond, which makes the temporal distance quite relevant.

A "review of media reports" is not going to capture any incidents that the media didn't report on. That doesn't strike me as likely to capture every incident, or even a majority of incidents.

Florida got rid of that department in 2002.

"Ghoti" is an artificial example that doesn't actually work if you account for the way positioning affects pronunciation. Pull up a list of words that start with "gh": none of them (unless "ghoti" itself is on the list) start with an /f/ sound. You'll find the same for words ending in "ti" and the /ʃ/ sound.

I recommend asking people how "ough" is pronounced instead. Cough, bough, though, thought, through, thorough, hiccough--enough!

> What are you talking about re: space shuttle and tens of millions?

GP was almost certainly referring to "They Write the Right Stuff," an old article that is pretty well known in spaces like this. It discusses a process that (a) works extremely well (the engine control software was ~420 kLoC with a total of 17 bugs found in a window of 11 versions) and (b) is extremely expensive (the on-board shuttle software group had a budget of ~35 million per year in mid-90s dollars).

The Natrol liquid isn't usually too hard to track down. They advertise it as 1 mg or 2.5 mg, but it's the same stuff, the bottle just direct you to take 4 or 10 mL respectively.

It's not actually optimal. Each check should account for all previous feedback, but it may be optimal to make a known-incorrect guess and trade the chance of winning with that guess for additional information.

For example, if your first guess on wordle is BOUND and you learn that the word is _OUND, you know the answer is one of FOUND, HOUND, MOUND, POUND, ROUND, SOUND, WOUND. Satisfying all previous feedback leaves you checking those one at a time and losing with probability 2/7. Or you could give up the 1-in-7 chance of winning in 2 and trade it for certainly winning in either 3 or 4: HARMS checks four of those options, and WHOOP identifies the remaining three.

I don't see wires as a problem. Wireless accessories are slightly more convenient when you're moving the computer around, which is why my work laptop has a wired keyboard plugged into the dock and a wireless mouse with the receiver plugged into the laptop directly, but that's not a concern with my desktop so I go wired there.

Why would I want to worry about a battery even every other month when I could just not worry about it ever?

If a malicious actor found a gay person in such a job, they could easily extort them with the threat of getting them fired! So obviously you had to fire gay people, lest they get extorted by someone threatening to expose them and thus get them fired.

I don't know exactly where to draw the line on "the vast majority," but surely it must be higher than the bar for a simple majority, which is "more than half." If you want to describe something in the lead but under the 50% mark, the word you're looking for is "plurality."

In the end, identifying where you can usefully take action to reduce the chances of something similar happen in the future is far more useful than assigning blame.

The Moon's gravity isn't just pulling on the water, it's pulling on the Earth as a whole. It's pulling more on the Earth as a whole than on the water on the far side. In the Earth's frame of reference, that looks like it is pushing the water on the far side away a little bit.

By this standard, the US has not been at war since WWII. This is an absurd result, so I conclude that the standard is wrong. Official declarations of war have become decoupled from actually being at war.

I do it for the purpose of preserving the battery for myself down the line. I'll go for a full charge if I expect to need it, but 80% is usually more than enough so why put unnecessary wear on the battery?

I'd rephrase the sell as "now people who are used to doing the wrong thing and risking vulnerabilities can do the right thing without any extra effort," with a footnote about the difference in types allowing libraries to force the change.

My favorite math professor said "your homework is as many of the odd-numbered problems as you feel like you need to do to understand the material" and set a five minute quiz at the start of each lecture which counted as the homework grade. I can't speak for the other students, but I did more homework in his classes than any of the other math classes I took.

Even in that case I'd be hesitant to open a CSV file in excel. The problem is that it will automatically apply whatever transformation it thinks is appropriate the moment you open the file. Have a digit string that isn't semantically a number? Too bad, it's a number now, and we're gonna go ahead and round it. You didn't really need _all_ of the digits of that insurance policy number, did you?

They did finally add options to turn off the common offenders, but I have a deeply ingrained distrust at this point.

If something was caused by pilot error, there's nothing you can really do except shrug and hope it doesn't happen again. It's an intuitively appealing explanation, and usually wrong. The aviation community has spent decades rejecting that instinct and looking for contributing factors that can be addressed. Those other factors are almost always present, and improvements can then be made. The net result of this process is that aviation has become incredibly safe, which would not have happened if people were content to say "eh, it was probably pilot error."

All else being equal, two access methods are strictly less secure than a single access method. But is all else equal? I suspect that there are quite a few people who are willing to use a long, complicated password occasionally but who won't put up with that for passwords that are used frequently. If those people use better passwords when they can use a PIN to make routine access easy, that's a win.

No, the statement was that ".net and .com are still pulling 80% of their weight when it comes to cybercrime." I read that as saying that .net and .com domains show up in cybercrime 80% as often as would be expected if all TLDs were equally likely to be used for cybercrime.

The vast majority of possible explanations for anything are wrong, so "correct unless disproven" is not a sensible default. Your evidence that it's right is ... ?