herring

The rhetoric around debt is a total red herring and totally orthogonal to the use of credit cards.

Or, in other words, your post above is a strawman / red herring (though a frequently encountered one).

This is a red herring: this idea that the user will already have a cached copy of CDN-hosted jQuery is bogus.

That would make me wonder if it was an intentional red herring to engender more trust and reduce suspicion around her eventual death.

You focused on a red herring (though it was my fault to put it there, and I've deleted it, thank you).

Splitting groups into 'female' and 'male' is a red herring.

And consumptive/rivalrous use is a red herring.

>This is a red herring: this idea that the user will already have a cached copy of CDN-hosted jQuery is bogus.

And, again, the Completeness Theorem, which you mentioned as supporting your counterexample, is a complete red herring and doesn't have to do anything with any of that.

I'm not aware of things like this getting shut down except in cases where its brought up as a bit of a red herring to distract from another debate.

(I am going to assume we are still talking about the article.) First of all, trespass is a red herring in this case.

(I think my other post about trespass being a red herring in this case is by far the more important point, but figured I would follow up on trespassing as well.

Really though, the software argument is a red herring, because it's impossible to "steal" software.

The "it must be some computer whiz breaking our database!" plot was a major red herring, but the characters believed it, because computer security was under closer scrutiny.

People's "entitlement" is a complete red herring.

"I'm not ending with a red herring, I'm saying you're creating a huge integration hassle with the rest of the web application world." How so?