anchor.diff:          aside
             ul
               li There's a lot of these, not hard finding options to talk about.
  -            li 4,500 so far in 2015, 711 9+ out of 10.
  +            li 700 so far in this year, start of February(!), 59 rated 9+ out of 10.
               li 9+ generally means terrible consequences, easy to attack, widely relevant, not a special case
  -
  -      section(data-bespoke-state='topic-slide')
  -        h4 Nothing is really secure, but
  -        h2.full-slide Don't Panic
  -        h3.conclusions
  -          ul
  -            li Be ready to update
  -            li Fear user input
  -            li Value best practices
  -            li Keep errors secret
  -            li Isolate your components
  -            li Avoid complexity
  -        aside
  -          ul
  -            li If nothing else, watch for security notices, be ready to update <em>fast</em>
  -            li Be very cautious around user input. Lots of risk that's easily missed.
  -            li Pay attention to software development best practices, especially testing etc
  -            li Consider the real cost of features. Turn off or limit unnecessary features where possible
  -            li Isolate your components from one another, and the world
   
         section(data-bespoke-state='topic-slide') 
           h1.title Your Web Stack Would Betray You In An Instant
  
positive.code:             li Upside to this
  
        section
          h2 Things that will be loudly publically insecure:
  
          ul.stack
            li.lowlight Your Code
  
negative.code:             li Terminates a chunk of code prematurely
              
        section
          h2 Arbitrary Code Execution<br/>with YAML
          pre
            code.language-yaml.
              --- !ruby/hash:NamedRouteCollection
  