Most Superuser questions can be comprehensively answered within the confines of 30K characters, however there are the occasional comprehensive answers that could benefit from additional comprehensive info that are unable to because of the 30K character limit.
- I've come up against the limit several times while writing in-depth, comprehensive answers on Superuser, and when I do, I've had to get creative with how to edit small things to decrease the content below the 30K limit.
In some of my most comphrensive answers, markdown alone makes up a significant portion of the content to the tune of thousands of characters since I make heavy use of markdown and man page links - for example:
- In this answer, I've had to remove content when making updates to it since it sits at 29,999 characters
- In this answer, I had to limit the content to only one of four complex, applicable scenarios (Automate Windows Setup, Configuration Set, Distribution Share, Deployment Share), resulting in solely covering the first, and not the latter three, because I was at 29,956 characters
- In this answer, I was unable to include the content of a Windows-formatted
openssl.cnf
since the answer was already at 29,596 characters without it (since the answer wholly relied on this specific customizedopenssl.cnf
, it made sense to include the contents within the answer, even though it'll always be available on my GitHub)
A solution could be to exclude markdown and weblink addresses from the character limit, only applying the limit to the rendered output.
- The intent seems to be to restrict the rendered output, which isn't the issue, it's the thousands of markdown characters in comprehensive, in-depth answers markdown is heavily used within because it makes the content far easier to digest and sift through
It's always seemed like Superuser and Stack Overflow are meant to be an authority on how to do what is asked, and both are professionally referenced by IT professionals and universities/colleges the world over, with a very large swathe of those sites' users being IT professionals.
I've provided three specific answer examples to avoid generalized statements:
(if issues are seen in those, by all means, but blanket, generalized statements really don't apply)
- The answers linked to aren't on overly broad questions:
- Folks are always welcome to their opinion, but the users who've viewed those questions didn't flag the questions as overly broad/vote to close (18K on the first, 6K each on the second and third ones) - the consensus by Superuser users is those questions are not overly broad
- Folks are always welcome to their opinion, but the users who've viewed those questions didn't flag the questions as overly broad/vote to close (18K on the first, 6K each on the second and third ones) - the consensus by Superuser users is those questions are not overly broad
- My answers are always focused, always written in an outline format with bullets restricted to a couple sentences at most, and always take weeks to write and format with markdown when it comes to comprehensive, in-depth answers north of ~15K characters
- On highly complex answers, such as the one about LTI/ZTI Windows installs (it took over a month to write and format), Microsoft has never provided a step-by-step writeup of all that's required to link to; this gets even worse in regards to Deployment Shares, where the end user is largely left up to their own devices to figure out how to fully use MDT and correctly configure the Task Sequence (an example of one I created to demonstrate the complexity)
- Microsoft provides no full, step-by-step writeup of how to fully configure an LTI/ZTI, or Deployment Share and its Task Sequence, that I've ever been able to find while scouring Microsoft Learn (used to be Microsoft Docs)
<h1>
,<pre><code>
,<ul><li>
, etc.https://stackexchange.com
->//stackexchange.com
. In your first linked example you have 38 links, thats 38x5 = 190 extra characters.