user4108: Consider the post Can the human chin have developed to protect against combat strangles?. I haven't read the post because it is too long and I don't feel like giving time to read it. There are two ways I can think of reacting to such long post

Comment that the post is very long and many users might be too lazy to read and it would therefore be strategic to shorten the post as much as possible
Vote to close as being too long


user25568: I think it is good that yet SE site doesn't restrict anyone  (not sure; just upto the highest amount I've used) to certain number of word for questioning or answering. But at the same time there should exist a manual guideline or manual-instructions to keep the question not too lengthy. 
If the word count is constrained; there would appear following problems:- 

Among the word count; certain portion will be eaten up by codes (commands), hyperlink. 
wordcount eaten up by hyperlinks; is indefinite. Especially Google book results sometimes could be very big. 
If elaboration is required on a rare yet urgent basis; we would face froblem. As well borderline amount, inflexible word count could decrease spontaniety in writing first and then trimming into smaller and user friendly form. 
there is place of doubt on "how much is too-much";  (because photos, graphs, calculations etc sometimes may eat up good amount of space); certainly the amount same as a research paper, a book or a dictionary; would be too much. 

But these problems would affect mostly on the answering; not much on questioning . 
However; We need to keep question size within reasonable range because: 

if the question is very specific (As fit to SE Model) ; it would not take too-much place or too-many words. In reverse; a question used too much words that doesn't indicate these made the question clear. 

showing too much information or knowledge is usually not required in question. That is better as an answer. Self answering is allowed on SE. Once I saw a question on extinction (I could not find it anymore... may be it is deleted) where the question contained huge images for each fossil-animal-taxa; though that is not part of question. Giving additional information in helpful in answering, but usually troublesome in questioning.
The example cited here by OP; is like a research paper... not like a single question; but rather like multiple question at a time. A question containing many question at a time;  becomes unsuitable to this format even if each of them could be understand clearly.


So from these points we could set some guideline that the question should be within a readable range. Any bot will not essentially block typing; yet they have to tell/ indicate why the clear question  is not possible to ask in a very confined place. If it is seen that the question is clear , specific yet took fail to indicate any reason to consume big volumes, it may be put on hold
. 

4108: <p>Consider the post <a href="https://biology.stackexchange.com/questions/54534/can-the-human-chin-have-developed-to-protect-against-combat-strangles">Can the human chin have developed to protect against combat strangles?</a>. I haven't read the post because it is too long and I don't feel like giving time to read it. There are two ways I can think of reacting to such long post</p>

<ol>
<li><p>Comment that the post is very long and many users might be too lazy to read and it would therefore be strategic to shorten the post as much as possible</p></li>
<li><p>Vote to close as being too long</p></li>
</ol>
 25568: <p>I think it is good that yet SE site doesn't restrict anyone  (not sure; just upto the highest amount I've used) to certain number of word for questioning or answering. But at the same time there should exist a manual guideline or manual-instructions to keep the question not too lengthy. </p>

<p><em>If the word count is constrained; there would appear following problems</em>:- </p>

<ol>
<li><p>Among the word count; certain portion will be eaten up by codes (commands), hyperlink. </p></li>
<li><p>wordcount eaten up by hyperlinks; is indefinite. Especially Google book results sometimes could be very big. </p></li>
<li><p>If elaboration is required on a rare yet urgent basis; we would face froblem. As well borderline amount, inflexible word count could decrease spontaniety in writing first and then trimming into smaller and user friendly form. </p></li>
<li><p>there is place of doubt on "how much is too-much";  (because photos, graphs, calculations etc sometimes may eat up good amount of space); certainly the amount same as a research paper, a book or a dictionary; would be too much. </p></li>
</ol>

<p><em>But these problems would affect mostly on the answering; not much on questioning .</em> </p>

<p>However; We need to keep question size within reasonable range because: </p>

<ol>
<li><p>if the question is very <em>specific</em> (As fit to SE Model) ; it would not take too-much place or too-many words. In reverse; a question used too much words that doesn't indicate these made the question clear. </p>

<ol start="2">
<li><p>showing too much information or knowledge is usually not required in question. That is better as an answer. Self answering is allowed on SE. Once I saw a question on extinction (I could not find it anymore... may be it is deleted) where the question contained huge images for each fossil-animal-taxa; though that is not part of question. Giving additional information in helpful in answering, but usually troublesome in questioning.</p></li>
<li><p>The <a href="https://biology.stackexchange.com/questions/54534/can-the-human-chin-have-developed-to-protect-against-combat-strangles">example</a> cited here by OP; is like a research paper... not like a single question; but rather like multiple question at a time. A question containing many question at a time;  becomes unsuitable to this format even if each of them could be understand clearly.</p></li>
</ol></li>
</ol>

<p>So from these points we could set some guideline that the question should be within a readable range. Any bot will not essentially block typing; yet they have to tell/ indicate why the clear question  is not possible to ask in a very confined place. If it is seen that the question is clear , specific yet took fail to indicate any reason to consume big volumes, it may be put on hold
. </p>
