Update ThingsToKnow.rst

ThingsToKnow.rst

@@ -1,6 +1,7 @@
 Things to know (best practices and "issues") READ IT !!!
 ========================================================
 
+* Obviously, never expose a socket speaking the uwsgi protocol to the public network unless you know what you are doing. That channel allows for dynamic loading of application (read: arbitrary execution of code)
 * The ``http`` and ``http-socket`` options are entirely different beasts.
   The first one spawns an additional process forwarding requests to a series of workers (think about it as a form of shield, at the same level of apache or nginx), while the second one sets workers to natively speak the http protocol.
   TL/DR: if you plan to expose uWSGI directly to the public, use ``--http``, if you want to proxy it behind a webserver speaking http with backends, use ``--http-socket``.