- I'm sorry. I simply can't do what you ask. I would go ahead and try to answer all of your objections in one post -- but since you want me to do it in a hurry -- which I can't do -- I'll go back and try to answer one "fatal flaw" at a time.
As I predicted: lame excuses and an insistence that we stay the course of the current unproductive waste of time.
First the excuse is that I've set you some unreasonably onerous task. "Oh, poor poor me! Even though this list has been put in front of me every day for nine months, I just can't possibly answer it all! It's oh, so much work, and you're so terrible for making me do it. I'd rather just keep pursuing this unproductive course for another five years or more."
Now the excuse is that I'm rushing you after nine months. "An hour!? I only have an
hour to answer all the questions? Oh, poor poor me! That's unreasonable and more than I could ever cope with." And so forth. (Often the excuse is, "Jay's just a big meanie, he doesn't coddle me like I expect, and he uses vigorous language to attack my proof. Oh, poor poor me! I have to deal with such distasteful critics, even though I keep inexorably coming back for more.") What's so unreasonable about expecting your next post to be what we've all asked for? All you have to do is
not post about other things until you've taken an hour to do as I've asked. It's not that you're being rushed. It's that you are
not being allowed to direct the debate like your own little play. Heck, you threw a hissy fit when jsfisher didn't answer you within a few hours. I'm allowing you to respond in your own good time,
but within the constraints I've imposed and without the threat of distraction. Whatever answers you think you need to give to people today can wait. I've waited nine months, and I'm first in line.
The sort of whining in your recent posts doesn't substitute for the mature discussion we hope for and the answers we need. Your approach to avoiding responsibility is to make this look like some impossible task so you can convince people you don't have to do it. As I said, the weakest point of an opponent's argument -- in his own estimation -- is the part he defends most irrationally. Here you are pulling out all the stops to avoid discussing all of your argument at once at the fundamental broad-strokes level. Hence that's what I suggest you recognize as its weakest point: taken as a whole, it's a house of cards with no strength or substance.
It's pretty silly of you to try this tactic. Clearly it's not working. But more importantly, most of the requirements I've set for the task are aimed at making it
easier for you to complete. And it's not like I've kept secret the reasons for the rules. There's no subterfuge. My thesis is that you know your argument can't survive if seen in breadth, which is why you participate in discussions only at depth. I've contrived a test for that thesis. And you're proving it correct.
You've relied hitherto on ambiguity. You say, "I'm doing this for reasonable reason X," but your critics note that the same behavior would also follow from
unreasonable reason Y. "The rules of effective debate say we should focus on the small sub-issues until they are resolved." Is that the real reason for your posture? Or is it that you want to distract away from the glaring high-level problems? Normally when we point out that your proof is a house of cards, you respond by saying that they're the
best cards, and all the experts from Hoyle confirm that there's nothing wrong with the individual cards.
Thus we construct an experiment to generate data that helps us burn through ambiguity and discriminate between X and Y. Your reluctance to participate confirms that you don't believe the ambiguity will resolve in your favor, which is frankly all we need to know.
When a professional mathematician believes he has discovered an important proof, he is expected to submit it in a paper to a respectable journal. As part of that submission, he is expected to summarize the proof in a single paragraph, the paper's abstract. This is true for proofs or arguments in any scholarly field, whether primary arguments or rebuttals and rejoinders. The abstract is not the proof. The details of the proof and the evidence in favor for it are naturally to be found within the paper itself. The proof does not succeed via its summary,
but it can fail because of it. If the broad-strokes outline of the proof is deficient at the high level of the abstract, no amount of detail can save it.
Similarly when a case is brought before the law, the complaint document outlines the allegations and describes in broad terms what evidence supports the claim. The document is not the case. The allusions to evidence are not the evidence itself. The actual argument takes place at trial. As above, a case does not prevail on the complaint,
but it can fail because of it. And when it fails at that stage, it is to say that no amount of evidence presented at trial can salvage the flaws at that level. Passing muster at the complaint stage or the preliminary hearing stage justifies moving on to trial.
What's happening here is similar. You've presented your case. The errors in it have been identified. Since each of these is individually fatal to your case, you owe your critics an abstract or summary brief to assure them that you have answers for
all of them. Because if there are any you can't answer, there's no point to proceeding to "trial." Regardless of what interesting topics would arise in discussion, the proof
per se would be dead.
So let's visit those requirements and see whether they're really as imposing and unfair as you want everyone to believe.
You don't have to provide in-depth answers. Or more specifically, you are
forbidden from providing in-depth answers. You don't get to add dialectics, quotatons, side-trips, or any of the things that would take you time and require effort in the form of research, collation, and commentary. This is so you can't use the excuse that this is too much work. Similarly the one-hour and/or two-sentence limit is intended to guide you in understanding what size answers are satisfactory at this point. The answers I'm looking for are the ones you can reasonably compose in an hour, or express in a couple sentences. The detail comes later. I'm not looking for another kind of answer at this point, so your
desire to write a different kind of answer is irrelevant.
You don't get to spread the answers out. That would result in the depth-first argument that is your usual mode of evasion, which is expressly what we're trying to avoid. As soon as you post the answer to Fatal Flaw 1, you know full well it will be discussed and debated. You naturally wanting to hold up your side of that discussion becomes the excuse for why we never get to Fatal Flaws 2-12. This rule keeps you from playing the shell game that's been so effective for you until now; you have to turn over all the shells at once. Nothing to fear unless you're running a crooked shell game. Are you running a crooked shell game?
You don't get to just repeat the original claim. The list of fatal flaws presumes your critics know your argument. The list is a response to it. Restating the claim doesn't address the response. You're constantly "resetting" the argument every time you switch sub-sub-sub-issues, so we never get anywhere. This time we intend to get somewhere; the state of the argument after your response has to be farther ahead than before it. Answers that start, "My claim is..." would probably be immediately rejected.
So can you explain why this is unreasonable?
After several years, the evidence shows your notion of "effective debate" doesn't work anywhere with anyone. At best it's years of stalemate watching you play your typical games. At worst people can tell immediately that you're not serious. So since your method demonstrably sucks, what's wrong with trying my version of effective debate? Mine attempts to determine quickly whether failure is inevitable or whether there's enough to proceed to a laborious detailed examination. It worries me that you're not interested in doing that. It worries me that you just want to keep playing the shell game.