Makefile

@@ -119,9 +119,9 @@ deploy-onion:
 # we only deploy html to the staging site
 .PHONY: deploy-staging
 deploy-staging:
-	@$(MAKE) DOMAIN=staging.seirdy.one USER=deploy@seirdy.one OUTPUT_DIR=public_staging .prepare-deploy
+	@$(MAKE) HUGO_FLAGS='' DOMAIN=staging.seirdy.one USER=deploy@seirdy.one OUTPUT_DIR=public_staging .prepare-deploy
-	@$(MAKE) DOMAIN=staging.seirdy.one USER=deploy@seirdy.one OUTPUT_DIR=public_staging compress
+	@$(MAKE) HUGO_FLAGS='' DOMAIN=staging.seirdy.one USER=deploy@seirdy.one OUTPUT_DIR=public_staging compress
-	@$(MAKE) DOMAIN=staging.seirdy.one USER=deploy@seirdy.one OUTPUT_DIR=public_staging deploy-html
+	@$(MAKE) HUGO_FLAGS='' DOMAIN=staging.seirdy.one USER=deploy@seirdy.one OUTPUT_DIR=public_staging deploy-html
 
 .PHONY: lint-and-deploy-staging
 lint-and-deploy-staging:

archetypes/default.md

@@ -1,5 +1,5 @@
 ---
-title: "{{ .Name | humanize }}"
+title: "{{ replace .Name "-" " " | title }}"
 date: {{ .Date }}
 draft: true
 ---

archetypes/reply.md

@@ -1,10 +0,0 @@
----
-title: "{{ .Name | humanize }}"
-date: {{ .Date }}
-replyURI: ""
-replyTitle: ""
-replyType: ""
-replyAuthor: ""
-replyAuthorURI: ""
----
-

assets/css/main.css

@@ -1,5 +1,4 @@
-/* CSS that adds the bare minimum for a simple, accessible,
+/* CSS that adds the bare minimum for a simple layout.
- * touch-friendly layout.
  * Nothing here exists purely for aesthetics; everything addresses a
  * specific a11y, compatibility, or critical
  * usability need.
@@ -14,7 +13,7 @@
  * don't actually use those for styling.
  *
  * To keep myself from caring about minute details, I limited myself to
- * only defining spacing in increments of .25em. Pixels are 1px or
+ * only defining spacing in increments of .125em. Pixels are 1px or
  * multiples of 3px. This also improves compression. No more "finding
  * the perfect value".
  *
@@ -82,6 +81,18 @@ html {
 		max-width: 35em;
 	}
 
+	/* Compensate for misalignment and wasted space caused by padding
+	 * and margin adjustments in nav children made to meet SC 2.5.5 */
+	footer > nav,
+	header > nav,
+	dt > a,
+	h2 + a {
+		margin-left: -.25em;
+	}
+	header > nav {
+		margin-bottom: -.75em;
+	}
+
 	summary {
 		/* The tappable region of a <summary> extends across the page.
 		 * we need to tell users that the full space is interactive.
@@ -100,79 +111,35 @@ html {
 		margin: .5em 0;
 	}
 
-	/* Make superscripts a bit easier to tap. */
-	sup > a {
-		margin-left: .25em;
-		padding-bottom: .25em;
-	}
-
 	/* SC 2.5.5, Google a11y: Increase tap target size a bit
 	 * - Summary is a tappable button
 	 * - standalone links in lists are usually parts of collections of
 	 *   links that should be easy to fat-finger
 	 * - links that directly follow h2 without being contained in a
 	 *   paragraph are section permalinks. */
-
+	dt,
-	input,
 	dt > a,
 	summary,
 	h2 + a,
-	li > a {
-		padding: .75em .25em;
-	}
-	/* Compensate for misalignment and wasted space caused by padding
-	 * and margin adjustments in nav children made to meet SC 2.5.5 
-	 * Also prevent overlapping outlines on focus */
-
-	/* We've increased the padding for dt > a, but dt without a link
-	 * should take up as much space. */
-	dt {
-		margin: .75em 0;
-	}
-
-	dt > a {
-		margin: -.75em 0 -.75em -.25em;
-		display: inline-block;
-	}
-
-	header > nav {
-		margin-bottom: -1em;
-	}
-
-	h2 + a {
-		margin: -.75em -.25em;
-	}
-
-	footer > nav,
-	header > nav,
-	/* List items with direct hyperlink children should only have one hyperlink. */
 	li > a,
-	h2 + a,
-	nav ol a {
-		margin-left: -.25em;
-		display: inline-block;
-	}
-
 	nav li,
-	ol li > a {
+	li details li,
-		margin: .25em;
+	input {
+		padding: .875em .25em;
 	}
 
-	div[itemprop="comment"] dd > a {
+	/* Make superscripts a bit easier to tap. */
-		display: inline-block;
+	sup > a {
-		margin-left: -.25em;
+		padding-bottom: .25em;
-		padding: .75em .25em;
 	}
 
-	/* Increase backlink tap target size */
+	nav li ol {
-	a[role="doc-backlink"] {
+		/* Don't duplicate bottom space: the last list item in the nested
-		padding: 0 1.75em 1.5em .25em;
+		 * list and the list item that is the entire nested list will both
-	}
+		 * have bottom padding */
-
+		margin-bottom: -1em;
-	/* Make room for those big backlink buttons so they don't overlap
+		/* Prevent nested lists from overlapping */
-	 * with links on the following endnote */
+		padding-top: 1em;
-	section[role="doc-endnotes"] li {
-		margin-bottom: 1.75em;
 	}
 }
 
@@ -184,7 +151,7 @@ dd,
 ol,
 ul {
 	margin: 0;
-	padding-left: 1.5em;
+	padding-left: 1.625em;
 }
 
 ol ol,
@@ -209,7 +176,7 @@ nav ul {
  * pixels between tap targets. */
 nav ul li {
 	display: inline-block;
-	margin-right: .5em;
+	margin-right: .375em;
 }
 
 /* narrow screens: reduce margin for blockquotes a lot, using
@@ -253,8 +220,8 @@ kbd {
 
 /* <ins> should not be mistaken for hyperlinks. */
 ins {
-	font-style: italic;
 	text-decoration: none;
+	font-style: italic;
 }
 
 /* narrow screens: remove unused figure margins
@@ -325,7 +292,7 @@ pre {
 	border: 1px solid #999;
 
 	/* borders shouldn't touch text */
-	padding: 0 .25em;
+	padding: 0 0.125em;
 }
 
 /* center standalone images; same justification as

content/posts/search-engines-with-own-indexes.gmi

@@ -88,11 +88,11 @@ These engines pass most of the tests listed in the "methodology" section. All of
 => https://www.alexandria.org/ Alexandria
 => https://github.com/alexandria-org/alexandria Alexandria engine source code
 
-* Yep: an ambitious engine from Ahrefs, an SEO/backlink-finder company, that "shares ad profit with creators and protects your privacy". Most engines show results that include keywords from or related to the query; Yep also shows results linked by pages containing the query. In other words, not all results contain relevant keywords. This makes it excellent for less precise searches and discovery of "related sites", especially with its index of *hundreds of billions of pages.* It's far worse at finding very specific information or recent events for now, but it will probably improve.
+* Fairsearch: an ambitious engine from Ahrefs, an SEO/backlink-finder company, that "shares ad profit with creators and protects your privacy". Most engines show results that include keywords from or related to the query; Fairsearch also shows results linked by pages containing the query. In other words, not all results contain relevant keywords. This makes it excellent for less precise searches and discovery of "related sites", especially with its index of *hundreds of billions of pages.* It's far worse at finding very specific information or recent events for now, but it will probably improve: while this version is live, it's not officially launched yet. When it officially launches, *it will be under a different name*. I expect Fairsearch to graduate from this section as result relevancy improves.
 
-=> https://yep.com/ Yep
+=> https://fairsearch.com/ Fairsearch
 
-Yep supports Open Graph and some JSON-LD at the moment. A look through the source code for Alexandria and Gigablast didn't seem to reveal the use of any structured data
+FairSearch supports Open Graph and some JSON-LD at the moment. A look through the source code for Alexandria and Gigablast didn't seem to reveal the use of any structured data
 
 
 ### Smaller indexes, hit-and-miss

content/posts/search-engines-with-own-indexes.md

@@ -108,9 +108,9 @@ These engines pass most of the tests listed in the "methodology" section. All of
 
 - [Alexandria](https://www.alexandria.org/): A pretty new "non-profit, ad free" engine, with [freely-licensed code](https://github.com/alexandria-org/alexandria). Surprisingly good at finding recent pages. Its index is built from the Common Crawl; it isn't as big as Gigablast or Right Dao but its ranking is great.
 
-- [Yep](https://yep.com/): an ambitious engine from Ahrefs, an SEO/backlink-finder company, that "shares ad profit with creators and protects your privacy". Most engines show results that include keywords from or related to the query; Yep also shows results linked by pages containing the query. In other words, not all results contain relevant keywords. This makes it excellent for less precise searches and discovery of "related sites", especially with its index of _hundreds of billions of pages._ It's far worse at finding very specific information or recent events for now, but it will probably improve.
+- [Fairsearch](https://fairsearch.com/): an ambitious engine from Ahrefs, an SEO/backlink-finder company, that "shares ad profit with creators and protects your privacy". Most engines show results that include keywords from or related to the query; Fairsearch also shows results linked by pages containing the query. In other words, not all results contain relevant keywords. This makes it excellent for less precise searches and discovery of "related sites", especially with its index of _hundreds of billions of pages._ It's far worse at finding very specific information or recent events for now, but it will probably improve: while this version is live, it's not officially launched yet. When it officially launches, **it will be under a different name**. I expect Fairsearch to graduate from this section as result relevancy improves.
 
-Yep supports Open Graph and some JSON-LD at the moment. A look through the source code for Alexandria and Gigablast didn't seem to reveal the use of any structured data.
+FairSearch supports Open Graph and some JSON-LD at the moment. A look through the source code for Alexandria and Gigablast didn't seem to reveal the use of any structured data.
 
 ### Smaller indexes, hit-and-<wbr />miss {#smaller-indexes-hit-and-miss}
 

layouts/shortcodes/indieweb-author.html

@@ -22,7 +22,7 @@
 	(btw this is all made of <span> cuz it is supposed to be inline)
 --><span itemprop="author copyrightHolder" itemscope="" itemtype="https://schema.org/Person" itemid="https://seirdy.one/#seirdy" class="h-card p-author author vcard">
 	<a itemprop="url" href="https://seirdy.one/" rel="author me home cc:attributionURL" class="u-url u-uid url" property="cc:attributionName">
-		{{ partial "indieweb-icon.html" }}
+		{{ partial "indieweb-icon.html" -}}
 		<span itemprop="name" class="p-name fn n">
 			<span itemprop="givenName" class="p-given-name given-name">Rohan</span>&#160;<span itemprop="familyName" class="p-family-name family-name">Kumar</span></span></a>
 </span>

scripts/bin/hugo-new-note

@@ -1,58 +0,0 @@
-#!/usr/bin/env dash
-
-set -e -u
-
-# the name of this program
-progname="$(basename "${0}")"
-
-help_text="Usage: ${progname} [OPTION...] FILENAME
-
-Compose a new note
-
-Options:
-  -h            Print this help and exit
-  -r            Whether this note should be a reply
-"
-
-usage() {
-	printf '%s' "${help_text}"
-}
-
-# when the user passess bad args, send a msg to stderr and exit
-# usage: bad_option <option> <reason>
-bad_option() {
-	echo "${progname}: option ${1}: ${2}" >&2
-	usage >&2
-	exit 1
-}
-
-reply='0'
-
-while getopts "hr" flags; do
-	case ${flags} in
-		h)
-			usage
-			exit 0
-			;;
-		r)
-			reply='1'
-			shift
-			;;
-		*)
-			bad_option "${flags}" 'invalid option'
-			exit 1
-			;;
-	esac
-done
-
-filename="notes/$1.md"
-
-if [ "$reply" = '1' ]; then
-	hugo new --kind reply "$filename"
-else
-	hugo new "$filename"
-fi
-
-"${EDITOR-nvim}" "content/$filename"
-
-# vi:ft=sh

scripts/xhtmlize-single-file.sh

@@ -32,7 +32,6 @@ sed 7d "$html_file" | xmllint --format --encode UTF-8 --noent - -o "$tmp_file"
 		| sd '<pre(?: tabindex="0")?>\n\t*<code ' '<pre tabindex="0"><code ' \
 		| sd '(?:\n)?</code>\n(?:[\t\s]*)?</pre>' '</code></pre>' \
 		| sd '</span>.span itemprop="familyName"' '</span> <span itemprop="familyName"' \
-		| sd '(<img itemprop="image" class="u-photo photo"[^>]*/>)<span' '$1 <span' \
 		| sd '([a-z])<(data|time)' '$1 <$2'
 } >>"$xhtml_file"