Site updated at 2018-02-09 09:53:11 UTC

blog/index.html

@@ -67,6 +67,34 @@
     <div class="grid-wrapper">
       <div class="grid grid-center">
         <div class="grid__item two-thirds lap-one-whole palm-one-whole">
+  <article class="listing">
+    <header>
+  <h1 class="beta">
+    <a href="/blog/2018/02/09/disabling-disqus/">Disabling Disqus comments</a>
+  </h1>
+  <div class="meta clearfix">
+    <time datetime="2018-02-09T01:00:00+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> February 9, 2018</time>
+    <span class="byline author vcard"><i class='icon-user'></i> Paulus Schoutsen</span>
+    <span><i class='icon-time'></i> 1 minute reading time</span>
+    <span>
+    <i class="icon-tags"></i>
+    <ul class="tags unstyled">
+        <li>Community</li>
+    </ul>
+  </span>
+      <a class='comments'
+         href="/blog/2018/02/09/disabling-disqus/#post-comments"
+         >Comments</a>
+  </div>
+</header>
+  <div class="entry-content clearfix">
+    <p>Last week, starting with the release of <a href="https://home-assistant.io/blog/2018/01/27/release-62/">Home Assistant 0.62</a>, we switched to using our <a href="https://community.home-assistant.io">community forums</a> for comments on our blog posts. By doing so, people are able to use their existing Home Assistant community accounts to comment on our blog posts and engage with one another. It has been easier for our users to stay in the loop with one less channel to keep track off.</p>
+<p>Previously, we were using the free version of Disqus to power comments on our blog. After the switch, to preserve the old comments, we decided to keep Disqus active on the older blog post pages. However, today we decided to turn them off.</p>
+<p>Today Disqus changed their advertisement strategy and turned on irrelevant graphical advertisement above and below the comment thread (<a href="https://twitter.com/balloob/status/961677501725421568">screenshot</a>). On a phone, it took so much screen real estate that it filled the whole page with an advertisement for weight loss milk. Previously, Disqus had advertisements in an unobtrusive way: showing suggested content a visitor might also be interesed in.</p>
+<p>Today we have switched all blog posts to the new commenting system and are no longer serving Disqus comments. We are exploring ways to restore the old comments.</p>
+  </div>
+  </article>
+  <hr>
   <article class="listing">
     <header>
   <h1 class="beta">
@@ -591,40 +619,6 @@ For Custom UI users: your custom UI will need to be updated before it can work w
   </div>
   </article>
   <hr>
-  <article class="listing">
-    <header>
-  <h1 class="beta">
-    <a href="/blog/2017/11/12/tor/">Secure remote access to Home Assistant using Tor</a>
-  </h1>
-  <div class="meta clearfix">
-    <time datetime="2017-11-12T08:00:00+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> November 12, 2017</time>
-    <span class="byline author vcard"><i class='icon-user'></i> Franck Nijhof & Fabian Affolter</span>
-    <span><i class='icon-time'></i> five minutes reading time</span>
-    <span>
-    <i class="icon-tags"></i>
-    <ul class="tags unstyled">
-        <li>How-To</li>
-    </ul>
-  </span>
-      <a class='comments'
-         href="/blog/2017/11/12/tor/#post-comments"
-         >Comments</a>
-  </div>
-</header>
-  <div class="entry-content clearfix">
-    <p>Routers and gateways provided by broadband internet providers are very often limited regarding features and configuration possibilities. Most of these limitations affect the opportunities that allow users to set up port-forwarding, DMZ, and DHCP reservations since the suppliers figured that average user does not want (or should not) deal with these. Making your Home Assistant instance available remotely (and securely), in this case, becomes more difficult. Are you one of those unlucky ones?</p>
-<p>There are a couple of options available to achieve a remote (and secure) accessible Home Assistant instance. However, almost all of them require you to: open one or more ports on your router, expose a public IP address, and require you to reserve a fixed IP in your DHCP server (or set up a static IP address). Examples of these are:</p>
-<ul>
-  <li>Combination of <a href="/components/duckdns/">DuckDNS</a> (or similar), <a href="/docs/ecosystem/certificates/lets_encrypt/">Let’s Encrypt</a> (SSL), DHCP reservation, and forwarding a port to your device running Home Assistant.</li>
-  <li>Setup a VPN, which often requires more hardware and software. Additionally, it also requires port-forwarding, DHCP reservation and most likely <a href="/components/duckdns/">DuckDNS</a> (or similar).</li>
-  <li><a href="/blog/2017/11/02/secure-shell-tunnel/">SSH tunnel-ing</a>. Which still requires port-forwarding, DHCP reservation and most likely (yeah, you’ve guessed it) <a href="/components/duckdns/">DuckDNS</a> (or similar).</li>
-</ul>
-<p>There is, however, another option available that most people do not realize: <a href="https://www.torproject.org">Tor</a>. <a href="https://www.torproject.org">Tor</a> offers a capability that they refer to as <a href="https://www.torproject.org/docs/hidden-services.html.en">Tor’s Hidden Services</a>, which allows you to securely access your Home Assistant installation <em>without</em> the need for all these things. No need to forward and open ports, no need to expose your public IP, no DNS entry, no need for SSL certificates, and you do not have to assign a fixed IP to the device running your Home Assistant.</p>
-<p>The most amazing part? It is super easy to set up!</p>
-      <a class="btn pull-right" href="/blog/2017/11/12/tor/#read-more">Read on &rarr;</a>
-  </div>
-  </article>
-  <hr>
   <div class="pagination">
       <a class="btn pull-left" href="/blog/posts/2">&larr; Older</a>
   </div>