💾 Archived View for dj-chase.com › documents › gemini-and-web › intro.html captured on 2023-04-19 at 22:39:24.
⬅️ Previous capture (2023-03-20)
-=-=-=-=-=-=-
<!DOCTYPE html>
<html>
<head>
<meta charset="UTF-8">
<title>
Equally Serving Gemini & The Web
</title>
<meta name="generator" content="//dj-chase.com/Make.py">
<link rel="stylesheet" href="../../style.css">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
</head>
<body>
<!-- whitespace to right of nav -->
<div>
<span> </span>
</div>
<nav>
<a href="/" aria-label="home">⌂ <span>›</span></a> <a href="/documents/">documents <span>›</span></a> <a href="/documents/gemini-and-web/">gemini-and-web <span>›</span></a> <a href="/documents/gemini-and-web/intro.gmi">intro.gmi</a>
</nav>
<header>
<h1>
Equally Serving Gemini & The Web
</h1>
</header>
<main>
<p>
I’ll be writing a series of posts detailing issues I have while setting up my server and site to serve Gemini and HTTPS without sacrificing the quality of either one. It will be fairly technical, but I’ll try to make it somewhat understandable for nontechnical* people without boring hackers.
</p>
<p>
For those unaware, <a href="//gemini.circumlunar.space/">Gemini</a> is a newish internet protocol (the bit before the domain in a URL) that aims to be simpler, more accessible, and less obtrusive than the web. As such, it lacks many of the features and semantics of HTTPS & HTML (the web’s protocol and document format, respectively), which makes it challenging to serve the same content without sacrificing the user’s experience on at least one protocol.
</p>
<p>
* nontechnical to approximately the same degree as most of my friends. This is probably a biased sample.
</p><!-- html code generated by txt2tags 3.3 (http://txt2tags.org) -->
<footer>
<p>
Questions or comments? <a href="mailto:DJ%20Chase%20%3Cu9000@posteo.mx%3E">Email me</a>.
</p>
<p>
© DJ Chase 2022-06-10. Licensed under the Academic Free License (AFL 3.0).
</p>
</footer><!-- cmdline: txt2tags -->
</main>
</body>
</html>