From e973849a7c008098a45c9aa1d0d9befc11791b7d Mon Sep 17 00:00:00 2001
From: Howard Abrams <howard@howardabrams.com>
Date: Mon, 21 May 2012 13:02:22 -0700
Subject: [PATCH] Added a little blurb on how to reproduce this at home.

---
 web/templates/twitter.html | 11 ++++++++---
 1 file changed, 8 insertions(+), 3 deletions(-)

diff --git a/web/templates/twitter.html b/web/templates/twitter.html
index 818d4ba..5a4311d 100644
--- a/web/templates/twitter.html
+++ b/web/templates/twitter.html
@@ -13,9 +13,14 @@
 });</code></pre>
   <p>
     <b>Note:</b> I realize that this is obvious, but keep in mind that
-  your JavaScript calls can not go directly to
-  <code>http://api.twitter.com</code>, but can only access the host
-  (and port) from whence they came.
+    your JavaScript calls can not go directly to
+    <code>http://api.twitter.com</code>, but can only access the host
+    (and port) from whence they came.
+  </p>
+  <p>
+    In order to try this demo at home, I have a
+    <a href="http://www.nodejs.org">Node.js</a>
+    server that acts a proxy.
   </p>
 </div>
 <div id="twitter-panel"></div>