diff --git a/website/page/home.php b/website/page/home.php
index df294484..9a468c98 100644
--- a/website/page/home.php
+++ b/website/page/home.php
@@ -11,6 +11,33 @@ offers many more features. It is available for
 <a href="?page=mobile">mobile application</a>.
 </p>
 
+<h4>25th January 2015</h4>
+<p>
+IITC 0.20.1 has been released. This is an important release that changes how the COMM tabs work,
+to avoid IITC making excessive requests in some cases, possibly leading to intel bans.
+</p>
+<p>
+This has, unfortunately, required the removal of the full/compact/public COMM tabs, instead IITC has an 'all' tab,
+just like the standard intel site. Also, the 'alerts' tab from the standard site has been added to IITC.
+See <a href="https://plus.google.com/105383756361375410867/posts/b9ihAer4Fxm">this post</a>
+for details about why this was needed.
+</p>
+<p>
+Also, other various tweaks and bugfixes.
+</p>
+<p>
+I'm sure many people will miss the public COMM tab. The best way for this to return is for Niantic to change the COMM tabs of the standard intel site, so it's supported server-side. My suggestion for Niantic is to remove the 'all' tab, instead having:
+</p>
+<ul>
+<li>'system' - the 'captured a portal/deployed a resonator/created a link/etc' messages (internally, the SYSTEM_BROADCAST type) only</li>
+<li>'public' - the cross-faction public user chat only - everything in the specificed range, and all public @mentions from any range</li>
+<li>'faction' - pretty much as it is now - your faction user chat messages, plus all faction @mentions from any range</li>
+<li>'alerts' - as it is now - the 'your portal is under attack' messages (internally, the SYSTEM_NARROWCAST type), plus @mentions at any range</li>
+</ul>
+<p>
+These changes should also be made to the app as well as the intel site.
+</p>
+
 <h4>10th January 2015</h4>
 <p>
 IITC 0.20.0 released. This is a critical update to fix loading of portals/links/fields after a protocol change by Niantic.
diff --git a/website/page/news.php b/website/page/news.php
index 356f3191..b8a43fbe 100644
--- a/website/page/news.php
+++ b/website/page/news.php
@@ -1,5 +1,32 @@
 <h2>News</h2>
 
+<h4>25th January 2015</h4>
+<p>
+IITC 0.20.1 has been released. This is an important release that changes how the COMM tabs work,
+to avoid IITC making excessive requests in some cases, possibly leading to intel bans.
+</p>
+<p>
+This has, unfortunately, required the removal of the full/compact/public COMM tabs, instead IITC has an 'all' tab,
+just like the standard intel site. Also, the 'alerts' tab from the standard site has been added to IITC.
+See <a href="https://plus.google.com/105383756361375410867/posts/b9ihAer4Fxm">this post</a>
+for details about why this was needed.
+</p>
+<p>
+Also, other various tweaks and bugfixes.
+</p>
+<p>
+I'm sure many people will miss the public COMM tab. The best way for this to return is for Niantic to change the COMM tabs of the standard intel site, so it's supported server-side. My suggestion for Niantic is to remove the 'all' tab, instead having:
+</p>
+<ul>
+<li>'system' - the 'captured a portal/deployed a resonator/created a link/etc' messages (internally, the SYSTEM_BROADCAST type) only</li>
+<li>'public' - the cross-faction public user chat only - everything in the specificed range, and all public @mentions from any range</li>
+<li>'faction' - pretty much as it is now - your faction user chat messages, plus all faction @mentions from any range</li>
+<li>'alerts' - as it is now - the 'your portal is under attack' messages (internally, the SYSTEM_NARROWCAST type), plus @mentions at any range</li>
+</ul>
+<p>
+These changes should also be made to the app as well as the intel site.
+</p>
+
 <h4>10th January 2015</h4>
 <p>
 IITC 0.20.0 released. This is a critical update to fix loading of portals/links/fields after a protocol change by Niantic.