diff --git a/index.xhtml b/index.xhtml
index 5f2ae26..f8e33f4 100644
--- a/index.xhtml
+++ b/index.xhtml
@@ -411,6 +411,57 @@
 			</ul>
 		</section>
 	</section>
+	<section>
+		<h2>Debates</h2>
+		<p>
+			There are several debates within the <strong>small-net</strong> communities:
+		</p>
+		<section>
+			<h3>Encryption</h3>
+			<ul>
+				<li>should encryption of communications be mandatory</li>
+				<li>should encryption of communications be optional</li>
+				<li>should encryption of communications be prohibited</li>
+			</ul>
+		</section>
+		<section>
+			<h3>Media</h3>
+			<ul>
+				<li>should it be text only (for some definition of "text")</li>
+				<li>should audio be supported</li>
+				<li>should embedded audio be supported</li>
+				<li>should images be supported</li>
+				<li>should embedded images be supported</li>
+				<li>should video be supported</li>
+				<li>should embedded videos be supported</li>
+			</ul>
+		</section>
+		<section>
+			<h3>Old Computers</h3>
+			<ul>
+				<li>should the default "text" format of a small-net protocol only support the features that the vintage VT05 computer-terminal had — i.e., no blinking, no bolding, no underlining, no reverse text, but also <strong>no lower-case letters</strong></li>
+				<li>should the default "text" format of a small-net protocol only support the features of the ASCII data format</li>
+				<li>should the default "text" format of a small-net protocol only support the features that are renderable on most of the popular modern computer-terminal-emulators</li>
+				<li>should we embrace the "best" of old computers without being restricted by (all) their limitations</li>
+			</ul>
+		</section>
+		<section>
+			<h3>Rich Formatting</h3>
+			<ul>
+				<li>is 'bolding' a type of punctuation or styling</li>
+				<li>is 'italicizing' a type of punctuation or styling</li>
+				<li>is 'underlining' a type of punctuation or styling</li>
+			</ul>
+		</section>
+		<section>
+			<h3>The Web</h3>
+			<ul>
+				<li>should a small-net protocol be intentionally incompatible with the Web — except maybe over bridge-proxies</li>
+				<li>should a small-net protocol be at least minimally compatible with the Web — to make it so people have a "gentle" path to using any small-net</li>
+				<li>should a small-net HTML make use of Web-components</li>
+			</ul>
+		</section>
+	</section>
 </article>
 </main>
 </body>