Merge pull request #102 from alexwlchan/master

Fix blockquote formatting in many posts
StackExchange · Jul 7, 2015 · a9c4b6e · a9c4b6e
2 parents 8c78422 + b851241
commit a9c4b6e
Show file tree

Hide file tree

Showing 70 changed files with 185 additions and 236 deletions.
diff --git a/_posts/2008-05-05-now-licensed-under-creative-commons.markdown b/_posts/2008-05-05-now-licensed-under-creative-commons.markdown
@@ -20,7 +20,7 @@ The Creative Commons site defines [four main clauses](http://creativecommons.org
 
 
 
-<blockquote>
+>
 
 > 
 > ![Attribution](/images/wordpress/cc-attrib.png) **Attribution**
@@ -73,9 +73,9 @@ You let others copy, distribute, display, and perform only verbatim copies of yo
 > 
 > 
 You allow others to distribute derivative works only under a license identical to the license that governs your work.
-> 
-> 
-</blockquote>
+>
+>
+
 
 
 

diff --git a/_posts/2008-06-20-safe-html-and-xss.markdown b/_posts/2008-06-20-safe-html-and-xss.markdown
@@ -44,7 +44,7 @@ That's [cross-site-scripting (XSS)](http://en.wikipedia.org/wiki/Cross-site_scri
 
 
 <blockquote>
-In recent years XSS surpassed buffer overflows to become the most common of all publicly reported security vulnerabilities. [ed: [the last time I wrote about this](http://www.codinghorror.com/blog/archives/000841.html), in early 2007, buffer overflows were more common.] Likely at least 70% of websites are open to XSS attacks on their users. Site administrators rarely fix XSS problems and, when they do, the hole is likely to have been open for more than a month and a half. In general, cross-site scripting holes can be seen as vulnerabilities present in web pages which allow attackers to bypass security mechanisms. By finding clever ways of injecting malicious scripts into web pages, an attacker can gain elevated access privileges to sensitive page content, session cookies, and a variety of other objects.
+In recent years XSS surpassed buffer overflows to become the most common of all publicly reported security vulnerabilities. [ed: <a href="http://www.codinghorror.com/blog/archives/000841.html">the last time I wrote about this</a>, in early 2007, buffer overflows were more common.] Likely at least 70% of websites are open to XSS attacks on their users. Site administrators rarely fix XSS problems and, when they do, the hole is likely to have been open for more than a month and a half. In general, cross-site scripting holes can be seen as vulnerabilities present in web pages which allow attackers to bypass security mechanisms. By finding clever ways of injecting malicious scripts into web pages, an attacker can gain elevated access privileges to sensitive page content, session cookies, and a variety of other objects.
 </blockquote>
 
 

diff --git a/_posts/2008-06-21-a-strangely-familiar-error.markdown b/_posts/2008-06-21-a-strangely-familiar-error.markdown
@@ -29,7 +29,7 @@ Ah yes, [the elusive stack overflow](http://en.wikipedia.org/wiki/Stack_overflow
 
 
 <blockquote>
-In software, a stack overflow occurs when too much memory is used on the [call stack](http://en.wikipedia.org/wiki/Call_stack). In many programming languages the call stack contains a limited amount of memory, usually determined at the start of the program. The size of the call stack depends on many factors, including the programming language, machine architecture, multi-threading, and amount of available memory. When too much memory is used on the call stack the stack is said to overflow; typically resulting in a program crash. This class of software bug is usually caused by one of two types of programming errors: **infinite recursion**, or **very large stack variables**.
+In software, a stack overflow occurs when too much memory is used on the <a href="http://en.wikipedia.org/wiki/Call_stack">call stack</a>. In many programming languages the call stack contains a limited amount of memory, usually determined at the start of the program. The size of the call stack depends on many factors, including the programming language, machine architecture, multi-threading, and amount of available memory. When too much memory is used on the call stack the stack is said to overflow; typically resulting in a program crash. This class of software bug is usually caused by one of two types of programming errors: <strong>infinite recursion</strong>, or <strong>very large stack variables</strong>.
 </blockquote>
 
 

diff --git a/_posts/2008-06-25-three-markdown-gotcha.markdown b/_posts/2008-06-25-three-markdown-gotcha.markdown
@@ -76,7 +76,7 @@ I started to wonder if there were other edge conditions in advanced Markdown syn
 
 
 
-<blockquote>
+>
 **1) Markdown's single biggest flaw is its intra-word emphasis.**
 
 > 
@@ -215,10 +215,9 @@ I think this is a symptom of Markdown's being designed for blog posts.  You can
 > 
 In my mind, this last one is huge.  If we allowed Markdown within block-level HTML, we could write a non-lossy version of [html2text](http://www.aaronsw.com/2002/html2text/) and make my dream of Markdown as a transient editing format a reality.
 
-> 
-> 
-Oh, also?  The HTML parser is pretty broken, so what gets recognized as a complete block of HTML can sometimes be surprising.  But Showdown uses an older, even-more-broken algorithm than the latest Markdown.pl beta, so I probably shouldn't point fingers.
-</blockquote>
+>
+> Oh, also?  The HTML parser is pretty broken, so what gets recognized as a complete block of HTML can sometimes be surprising.  But Showdown uses an older, even-more-broken algorithm than the latest Markdown.pl beta, so I probably shouldn't point fingers.
+
 
 
 

diff --git a/_posts/2008-10-06-solving-the-fastest-gun-in-the-west-problem.markdown b/_posts/2008-10-06-solving-the-fastest-gun-in-the-west-problem.markdown
@@ -20,7 +20,7 @@ Some Stack Overflow users are concerned about what they call [the "Fastest Gun i
 
 
 
-<blockquote>
+>
 Each question's answers are sorted by descending score and then descending time of posting. **This means that if a person sits down and answers a question in a long, thorough way, going through every nook and cranny, once they post their answer, it will already be one of about seven different ones, some of which have already been upmodded.** This wouldn't be a problem if those answers were as thorough as the one this guy's posting, but they usually aren't. Some of them are downright wrong, some aren't even answers to the question asked because their poster didn't bother to read the question all the way through.
 
 > 
@@ -30,7 +30,7 @@ This causes a problem I like to call SO's Fastest Gun in the West Problem.
 > 
 > 
 I've come to a point where I'd rather just send a short, simple, correct explanation, than to go and do some proper research, write a whole blog post about it or even make sure the code I post even compiles, just so it will be noticed, as opposed to the incorrect ones.
-</blockquote>
+
 
 
 
@@ -42,7 +42,7 @@ A number of solutions were proposed, but I believe many of them were worse than
 
 
 
-<blockquote>
+>
 **I do NOT want to, in any way, discourage the quick and dirty answer.**
 
 > 
@@ -52,7 +52,7 @@ I've asked questions that have received an immediate answer with enough informat
 > 
 > 
 This is extraordinarily helpful - I know I can post something on here, day or night, and get an answer within minutes, often seconds, that will be better than searching through books, online, etc, even though it's a throw-away post that took someone 35 seconds, who may have only answered for the reputation. If it's at all helpful, I upvote it.
-</blockquote>
+
 
 
 

diff --git a/_posts/2008-10-12-a-question-about-questions.markdown b/_posts/2008-10-12-a-question-about-questions.markdown
@@ -20,47 +20,21 @@ tags:
 
 
 
-<blockquote>
-                **What kind of questions can I ask here?**
-            
-> 
-> 
-                Programming questions, of course! As long as your question is:
-> 
-> 
-            
-> 
-> 
-                
+> **What kind of questions can I ask here?**
+>
+> Programming questions, of course! As long as your question is:
+>
 >   * detailed and specific
-> 
-                
 >   * written clearly and simply
-> 
-                
 >   * of interest to at least one other programmer somewhere
-> 
-            
-            
-> 
-> 
-                ... it is welcome here. No question is too trivial or too "newbie". Oh yes, and it should be about **programming**. You know, with a computer.
-> 
-> 
-            
-> 
-> 
-                Do look around to see if your question has already been asked (and maybe even answered!) _before_ you ask. However, as long as you've looked, if you end up asking a question that has been asked before, that is OK and deliberately allowed. Other users will hopefully edit in links to related or similar questions to help future visitors find their way.
-            
-> 
-> 
-            
-> 
-> 
-                It's also perfectly fine to ask and answer your own programming question, but pretend you're on [Jeopardy](http://en.wikipedia.org/wiki/Jeopardy!): phrase it in the form of a question.
-> 
-> 
-</blockquote>
+>
+> ... it is welcome here. No question is too trivial or too "newbie". Oh yes, and it should be about **programming**. You know, with a computer.
+>
+>
+> Do look around to see if your question has already been asked (and maybe even answered!) _before_ you ask. However, as long as you've looked, if you end up asking a question that has been asked before, that is OK and deliberately allowed. Other users will hopefully edit in links to related or similar questions to help future visitors find their way.
+>
+> It's also perfectly fine to ask and answer your own programming question, but pretend you're on [Jeopardy](http://en.wikipedia.org/wiki/Jeopardy!): phrase it in the form of a question.
+
 
 
 

diff --git a/_posts/2008-10-13-tags-and-tags-or-tags.markdown b/_posts/2008-10-13-tags-and-tags-or-tags.markdown
@@ -36,13 +36,13 @@ This isn't exactly new; you could always do this manually in the URL by space de
 
 
 
-<blockquote>
+>
 Show me all the questions tagged _both_ "python" **AND** "django"
 
 > 
 > 
 [http://stackoverflow.com/questions/tagged/python django](http://stackoverflow.com/questions/tagged/python django)
-</blockquote>
+
 
 
 
@@ -62,13 +62,13 @@ But maybe that's too specific for your tastes. Now you use **the new or pseudo t
 
 
 
-<blockquote>
+>
 Show me all the questions tagged _either_ "python" **OR** "django"
 
 > 
 > 
 [http://stackoverflow.com/questions/tagged/python or django](http://stackoverflow.com/questions/tagged/python or django)
-</blockquote>
+
 
 
 
@@ -84,13 +84,13 @@ We also support **NOT** if you prefix the tag with a dash, like so:
 
 
 
-<blockquote>
+>
 Show me all the questions tagged "python" **BUT NOT** tagged "django"
 
 > 
 > 
 [http://stackoverflow.com/questions/tagged/python -django](http://stackoverflow.com/questions/tagged/python -django)
-</blockquote>
+
 
 
 

diff --git a/_posts/2008-10-18-stack-overflow-on-hanselminutes.markdown b/_posts/2008-10-18-stack-overflow-on-hanselminutes.markdown
@@ -19,7 +19,7 @@ Geoff, Jarrod and I recently [recorded an episode of Hanselminutes](http://www.h
 
 
 
-<blockquote>
+>
 
 > 
 > **StackOverflow uses ASP.NET MVC - Jeff Atwood and his technical team**
@@ -34,7 +34,7 @@ Geoff, Jarrod and I recently [recorded an episode of Hanselminutes](http://www.h
 > 
 > 
 [Listen or download](http://www.hanselminutes.com/default.aspx?showID=152)
-</blockquote>
+
 
 
 

diff --git a/_posts/2008-10-23-stack-overflow-openid-case-study.markdown b/_posts/2008-10-23-stack-overflow-openid-case-study.markdown
@@ -20,7 +20,7 @@ tags:
 
 
 
-<blockquote>
+>
 Stack Overflow, much like Wikipedia, lets anyone edit anything – but unlike Wikipedia, we require users to earn a certain number of votes from other users before the system trusts them (we call this "reputation"). The concept of identity and logins is an essential part of how our site works.
 
 > 
@@ -34,7 +34,7 @@ With OpenID, we didn't have to write any login code, nor do we have to store use
 > 
 > 
 We were encouraged to use OpenID because our audience is fairly technical, and OpenID is quite common among technical bloggers and frequent blog participants, our early adopters. Also, there's a rich ecosystem of third party OpenID providers, not to mention Yahoo, AOL, Google, Sun, and soon MySpace.
-</blockquote>
+
 
 
 

diff --git a/_posts/2008-11-01-sql-2008-full-text-search-problems.markdown b/_posts/2008-11-01-sql-2008-full-text-search-problems.markdown
@@ -19,7 +19,7 @@ You may have noticed that things have been less responsive than usual on stackov
 
 
 
-<blockquote>
+>
 **Before 2008, full text search wasn't inside the database - it wasn't subject to things like transactions.**  Heck, it was more like Lucene where it lived outside on its own.  Now, it's stored inside data files and it's subject to transactions.  From what im hearing, blocking and locking is a completely new issue in 2008 FTS.  There's a big overhead involved with making it subject to transactions.
 
 > 
@@ -29,7 +29,7 @@ In most environments, you don't see full text being used for transactions.  At S
 > 
 > 
 If you do a full text search on Revisions and you include a common keyword like, say, SQL, you're going to match tens of thousands of records.  When I look at the query plans for these, I'm seeing 50-100k reads.  Doing that inside a table that's also getting heavy inserts - boom, transactional disaster.
-</blockquote>
+
 
 
 

diff --git a/_posts/2008-11-25-stack-overflow-is-you.markdown b/_posts/2008-11-25-stack-overflow-is-you.markdown
@@ -27,7 +27,7 @@ Apparently this "question" is.. somewhat controversial; as of now it has [31 rev
 
 
 
-<blockquote>
+>
 These are written in the third person so as not to disrupt the style of the thing. But hey, as we all know, Jon Skeet can make 1 == 3 anyway, so it makes no difference.
 
 > 
@@ -48,7 +48,7 @@ These are written in the third person so as not to disrupt the style of the thin
 
 >   * Users don't mark Jon Skeet's answers as accepted. The universe accepts them out of a sense of truth and justice.
 
-</blockquote>
+
 
 
 

diff --git a/_posts/2008-12-27-new-uservoice-moderator.markdown b/_posts/2008-12-27-new-uservoice-moderator.markdown
@@ -32,9 +32,9 @@ I wasn't kidding when I said this in the [Stack Overflow FAQ](http://stackoverfl
 
 
 
-<blockquote>
-At the high end of this reputation spectrum there is little difference between users with high reputation and moderators. That is very much intentional. **We don't run Stack Overflow. The community does.** 
-</blockquote>
+>
+At the high end of this reputation spectrum there is little difference between users with high reputation and moderators. That is very much intentional. **We don't run Stack Overflow. The community does.**
+
 
 
 
@@ -46,7 +46,7 @@ These two guys have gone _far_ out of their way to help other users on UserVoice
 
 
 
-<blockquote>
+>
 _adjunct_ (adjective)
 
 > 
@@ -56,7 +56,7 @@ _adjunct_ (adjective)
 
 >   2. Attached to a faculty or staff in a temporary or auxiliary capacity: an adjunct professor of history.
 
-</blockquote>
+
 
 
 

diff --git a/_posts/2008-12-28-reverse-engineering-the-wmd-editor.markdown b/_posts/2008-12-28-reverse-engineering-the-wmd-editor.markdown
@@ -62,7 +62,7 @@ Chris adds the following comments:
 
 
 
-<blockquote>
+>
 1. How will we coordinate the changes? Do we want to have a forum where people can post links to their repositories? (My repository is writable by me only -- but Git being a distributed VCS, this is not a problem, people just clone their own.) Or do you prefer to have a central repository that everyone checks into? In this case, I'm happy to check things into it -- or you can import it from my repository.
 
 > 
@@ -72,7 +72,7 @@ Chris adds the following comments:
 > 
 > 
 I'll try to get more changes checked in periodically, but I still have a ton of projects to clear, so getting the ball rolling with other coders would probably be a good idea.
-</blockquote>
+
 
 
 

diff --git a/_posts/2008-12-31-i-move-to-close-this-question.markdown b/_posts/2008-12-31-i-move-to-close-this-question.markdown
@@ -29,9 +29,9 @@ I had a long email exchange with an avid Stack Overflow user, [Mike Stone](http:
 
 
 
-<blockquote>
+>
 Visit any online forum and you'll find lots of locked threads. Closing is equivalent to locking a thread. **Would you really argue that every online bulletin board should allow any topic whatsoever to be opened and discussed?** If so then maybe Stack Overflow is not the place for you, because that is definitely not the intent. Based on all the data I've seen, closing is working. So is voting. They complement each other!
-</blockquote>
+
 
 
 

diff --git a/_posts/2009-01-24-adventures-in-delclusionism.markdown b/_posts/2009-01-24-adventures-in-delclusionism.markdown
@@ -20,13 +20,11 @@ In Wikipedia, there are two opposing camps: [the inclusionists and the deletioni
 
 
 
-<blockquote>
-**Inclusionists** believe that there should be no constraints on the breadth of the encyclopedia - that Wikipedia should include any entry that any contributor wants to submit. An article on a small-town elementary school is no less worthy for inclusion than an article on Stanford University.
+> **Inclusionists** believe that there should be no constraints on the breadth of the encyclopedia - that Wikipedia should include any entry that any contributor wants to submit. An article on a small-town elementary school is no less worthy for inclusion than an article on Stanford University.
 
 > 
 > 
 **Deletionists** believe in weeding out entries that they view as trivial or otherwise inappropriate for a serious encyclopedia.
-</blockquote>
 
 
 
@@ -78,8 +76,7 @@ But let me share with you a thoughtful email I received from Christian Nunciato
 
 
 
-<blockquote>
-On to my question.  I realize users have the ability to delete their own questions, which does seem right and good on the surface of things, but I have to say, it's a shame when some of us put such time and consideration into submitting thoughtful and complete answers, only to have the questions removed from the site inexplicably.  I'm writing in reference specifically to this one:
+> On to my question.  I realize users have the ability to delete their own questions, which does seem right and good on the surface of things, but I have to say, it's a shame when some of us put such time and consideration into submitting thoughtful and complete answers, only to have the questions removed from the site inexplicably.  I'm writing in reference specifically to this one:
 
 > 
 > 
@@ -89,10 +86,9 @@ On to my question.  I realize users have the ability to delete their own questio
 > 
 ... which I thought was an excellent question, and one other site users might ultimately benefit from; it digs a bit into the arcana of the language, and it's interesting stuff for those looking to deepen their understanding.  For some reason, though, it looks like the OP chose to take it down, which is a shame, because I personally spent a good deal of time drafting a submission for it, one that was upvoted and appeared to fix the user's problem and then some.
 
-> 
-> 
-I'm not asking for anything, though -- I just wanted to share that it's mildly discouraging to have put such work into something, in an attempt to contribute to the community, only to have the product taken down inexplicably and without recourse.  While the knowledge of having written it stays with me, which is great, it doesn't get out into the world, and it'll also make me think twice about spending as much time next time -- something that, as site owners, you might want to be aware of.  
-</blockquote>
+>
+>
+I'm not asking for anything, though -- I just wanted to share that it's mildly discouraging to have put such work into something, in an attempt to contribute to the community, only to have the product taken down inexplicably and without recourse.  While the knowledge of having written it stays with me, which is great, it doesn't get out into the world, and it'll also make me think twice about spending as much time next time -- something that, as site owners, you might want to be aware of.
 
 
 

diff --git a/_posts/2009-01-25-new-stack-overflow-servers-ready.markdown b/_posts/2009-01-25-new-stack-overflow-servers-ready.markdown
@@ -182,9 +182,9 @@ I also did a quick run of [SQLIOSim](http://support.microsoft.com/kb/231619), wh
 
 
 
-<blockquote>
+>
 **SQLIOSim will generate sufficient IO requests to overwhelm almost any disk subsystem.** The long IO message from the simulator are normal. Although this does tell you that at some point the disks won't keep up.
-</blockquote>
+