repo: gemini-site
action: commit
revision: 
path_from: 
revision_from: d09866aeb5ed69a6a36b193700a178ae27a48a96:
path_to: 
revision_to: 

commit d09866aeb5ed69a6a36b193700a178ae27a48a96
Author: Solderpunk 
Date:   Sat Nov 23 19:47:58 2019 +0000

    Discuss implications for retrocomputing.

diff --git a/docs/faq.txt b/docs/faq.txt

--- a/docs/faq.txt
+++ b/docs/faq.txt
@@ -227,3 +227,21 @@ crucially on thousands of lines of complicated code written by other
 people in order to provide a functioning IP stack, DNS resolver and
 filesystem.  Using a TLS library to provide a trustworthy
 implementation of cryptography is little different.
+
+## 2.6 Why don't you care about retrocomputing support?
+
+Gopher is so simple that computers from the 80s or 90s can easily
+implement the protocol, and for some people this is one of the great
+virtues of Gopher.  The TLS requirement of Gemini limits it to more
+modern machines.
+
+Old machines are awesome, and keeping them running, online and useful
+for as long as possible is an awesome thing to do.  But it also makes
+no sense for the vast majority of internet users to sacrifice any and
+all privacy protection to facilitate this.  Remember, though, that
+Gemini does not aim to replace Gopher, so the retro-compatible
+internet is not directly endangered by it.  In fact, people serving
+content via Gopher right now are strongly encouraged to start also
+serving that same content via Gemini simultaneously.  Retrocomputing
+fans can continue to access the content via Gopher, while modern
+computer users who wish to can switch to Gemini and reap some beneits.

-----END OF PAGE-----