content/about/uses.gmi

@@ -8,14 +8,14 @@ My main computer is a 2013 HP Elitebook 840 G1. It has a dual-core Intel i5-4300
 
 * OS: Fedora 36
 * Wayland compositor: Sway
-* Shell: zsh (interactive), dash (non-interactive/shell-scripts)
+* Shell: zsh
 * Terminal Emulator: Foot. Sometimes gnome-terminal when I'm using a screen reader.
 
 ## Basic utilities:
 
 * `$EDITOR`: Neovim
 * Browser: Firefox for most pages, Chromium for apps, NetSurf when I'm low on battery.
-* Coreutils alternatives: ripgrep, sd (better multiline regexes than sed), fd
+* Coreutils alternatives: ripgrep, sd (better multiline regexes than sed)
 * Music player: mpd, along with my mpd scripts
 * Video player: three builds of mpv, two with a PGO run on different types of video (anime and live-action-with-filmgrain). Often paired with yt-dlp and mpv_sponsorblock
 * Image viewer: mpv (one less program to keep track of), swayimg. Both support AVIF and JPEG-XL now.
@@ -57,7 +57,6 @@ My main computer is a 2013 HP Elitebook 840 G1. It has a dual-core Intel i5-4300
 * wormhole-william
 * rdrview
 * Efficient Compression Tool (better than Zopfli/ZopfliPNG)
-* zpaqfranz
 * scc
 * Pandoc
 * ghq, a VCS repository manager in the style of $GOPATH
@@ -67,17 +66,10 @@ My main computer is a 2013 HP Elitebook 840 G1. It has a dual-core Intel i5-4300
 => https://github.com/fhanau/Efficient-Compression-Tool Efficient Compression Tool
 => https://github.com/boyter/scc scc
 
-## Services
-
-* Migadu: email provider
-* deSEC: managed DNS name servers
-* Namecheap: domain registrar (not endorsed)
-* Digital Ocean: VPS (not endorsed)
-
 ## What I don't use
 
 These are tools that I don't use, or avoid using.
 
-* system monitoring TUIs: I usually just run the command to view the resource I need to know about
+* system monitoring TUIs: I just run the command to view the resource I need to know about
 * File managers: I prefer using the shell with fzf-based tab-completion that also features preview windows
 

content/about/uses.md

@@ -26,9 +26,6 @@ Sway
 Zsh
 : Login shell. POSIX-compatible and mostly Bash-compatible. Custom static build to skip checking system files and improve startup performance.
 
-DASH
-: Minimal POSIX-compatible shell that I use for non-interactive purposes (e.g. shell scripts). When statically-linked, its startup time is negligible even on the most underpowered hardware. This is really important to me, since many of my most-used commands are shell-script wrappers that I expect to run in a few milliseconds.
-
 Foot
 : Primary terminal emulator. Sometimes I use gnome-terminal when I'm using a screen reader.
 
@@ -40,14 +37,11 @@ Neovim
 : My `$EDITOR` of choice. Supports tree-sitter, uses lua configuration, and has a client for the Language Server Protocol (I only use the gopls, rust-analyzer, and ccls language servers)
 
 ripgrep
-: grep alternative that supports multiline regexes, PCRE2, and searching compressed files. Often faster, too.
+: grep alternative that supports multiline regexes, PCRE2, and searching compressed files. Much faster as well.
 
 [sd](https://github.com/chmln/sd)
 : For better and faster multi-line regex manipulation than `sed`.
 
-[fd](https://github.com/sharkdp/fd)
-: Better parallel execution than `find -exec`. I still use `find` in many situations, though.
-
 mpd
 : My music player daemon, paired with [my mpd scripts](https://sr.ht/~seirdy/mpd-scripts/) and [mpd-mpris](https://github.com/natsukagami/mpd-mpris).
 
@@ -162,9 +156,6 @@ z.lua
 [Efficient Compression Tool](https://github.com/fhanau/Efficient-Compression-Tool)
 : The last word in optimizing gzip or PNG size. Runs circles around Zopfli, ZopfliPNG, oxipng, etc. I use it in combination with `brotli` to compress all static text and PNGs on this site.
 
-[zpaqfranz](https://github.com/fcorbelli/zpaqfranz)
-: I use this for my long-term backups. `zpaq` is a journaling archiver, which allows me to compress backup deltas without having to use a journaling filesystem. `zpaqfranz` adds several features related to integrity-checking. The compression ratios are ridiculously good, even without the journaling; it beats every other realistic option, especially when combined with pre-processing offered by [lrzip-next](https://github.com/pete4abw/lrzip-next).
-
 [scc](https://github.com/boyter/scc)
 : Super fast SLOC alternative that shows statistics on code complexity by language.
 
@@ -267,10 +258,10 @@ All my server daemons are statically-linked binaries, which makes sandboxing eas
 
 
 Nginx
-: Specifically, [nginx-quic](https://quic.nginx.org/) with the [headers_more](https://github.com/openresty/headers-more-nginx-module) and [ngx_brotli](https://github.com/google/ngx_brotli) modules. Statically linked against zlib-ng, BoringSSL, PCRE2 (non-JIT), and musl libc; patched for dynamic TLS records, basic OCSP support, larger buffers for dynamic zlib compression (necessary for zlib-ng), and static HPACK compression. I recommend most people use Caddy instead of Nginx. The only benefits of Nginx are certain modules providing application-server capabilities, the ability to re-load all configs with zero downtime, and better performance on limited hardware (although most sites won't need to handle more than a few hundred requests per second, which Caddy can handle perfectly well).
+: Specifically, [nginx-quic](https://quic.nginx.org/) with the [headers_more](https://github.com/openresty/headers-more-nginx-module) and [ngx_brotli](https://github.com/google/ngx_brotli) modules. Statically linked against zlib-ng, BoringSSL, and musl libc; patched for dynamic TLS records, basic OCSP support, and static HPACK compression.
 
 [certbot-ocsp-fetcher](https://github.com/tomwassenberg/certbot-ocsp-fetcher)
-: Shell script to manage the OCSP cache for Nginx, since Nginx's own implementation shouldn't be used without running a trusted resolver (and is completely non-existent if you build with BoringSSL).
+: Shell script to manage the OCSP cache for Nginx, since Nginx's own implementation is lacking (and completely non-existent if you build with BoringSSL)
 
 [nginx-rotate-session-ticket-keys](https://github.com/GrapheneOS/nginx-rotate-session-ticket-keys)
 : Shell script to manage TLS session tickets, since Nginx's own implementation is really flawed. This replaces its default stateful session cache and also allows 0-RTT (also known as "early data") for idempotent requests. I patched it to use my statically-linked build of BoringSSL (I already had it sitting around after building it for Nginx).
@@ -287,29 +278,12 @@ Agate
 [Conduit](https://conduit.rs/)
 : Faster and more lightweight Matrix server in a single binary.
 
-Services
---------
-
-I generally try to limit my dependence on services, preferring to run software myself. I do make a few compromises.
-
-[Migadu](https://www.migadu.com)
-: Managed email hosting for seirdy.one. Running my own mail server and keeping my IP approved by all the entrenched players isn't worth the effort, especially if I ever choose to run something like a Tor exit node in the future. Migadu also offers an API, which I use to generate and list email aliases on the fly. My only gripes are that they still support TLS 1.1 and 1.0 for some reason, and that they don't yet support any open IMAP extensions that allow 2FA.
-
-[deSEC](https://desec.io/)
-: Managed DNS name servers. I could run something like PowerDNS or TrustDNS myself, but I'd need to use separate IPs (and ideally a separate server or two) for redundancy. I wanna keep seirdy.one cheap to host, and deSEC was free. It offered DNSSEC along with nice record types like SSHFP, HTTPS/SVCB, and OPENPGPKEY. OPENPGPKEY and SSHFP are especially useful, since keys distribution should have multiple distribution mechanisms with different sources of trust when manual verification isn't ideal.
-
-[Namecheap](https://www.namecheap.com/)
-: Domain registrar. I do not endorse Namecheap. I initially picked it since it ticked the right boxes: Whois privacy, domain locking, DNSSEC, custom name servers, decent support, and good prices. Porkbun and Gandi are other options that tick these boxes.
-
-[Digital Ocean](https://www.digitalocean.com)
-: My VPS provider. I do not endorse Digital Ocean for most peoples' needs. It's far pricier than equivalent options, and is only worth that price if you need top-tier support and a very good SLA. That being said, it does offer a lot of free credits ($100 if you sign up with someone's referral code; another $100 if you're a student); I started using Digital Ocean for the free credits. Scaleway and BuyVM are much better options if you want to go cheap. If I ever manage to get my hands on a home internet connection with excellent uptime, I might switch to self-hosting.
-
 What I don't use
 ----------------
 
 These are tools that I don't use, or avoid using.
 
-* System monitoring TUIs: I usually just run the appropriate command to view the resource I need to know about.
+* System monitoring TUIs: I just run the appropriate command to view the resource I need to know about.
 * File managers: I prefer using the shell with fzf-based tab-completion that also features preview windows.
 * Docker. I use Podman for disposable pet development environments, but I never use containers to run things on the server (except as a temporary learning exercise).
 

content/notes/re-blindness-awareness-month-ama.md

@@ -1,13 +0,0 @@
----
-title: "Re: blindness awareness month AMA"
-date: 2022-10-07T11:35:57-07:00
-replyURI: "https://mspsocial.net/@bright_helpings/109104639750302917"
-replyTitle: "October is Blindness Awareness Month, AMA"
-replyType: "SocialMediaPosting"
-replyAuthor: "Erik"
-replyAuthorURI: "https://cosmolinguist.dreamwidth.org"
----
-The most common and major accessibility (<abbr title="accessibility">a11y</abbr>) issues tend to be documented and well-known among <abbr>a11y</abbr> practitioners; however, "smaller" or "niche" issues (for lack of a better term) tend to go unnoticed. For instance, I recently learned that over-use of soft-hyphens can trip up the speech synthesis of the NVDA screen reader, and styling superscripts/subscripts a certain way can stop screen readers from announcing them. I also learned about how performance issues can cause delays in screen readers, making content exposed to screen readers fall out-of-sync with the actual page. We won't learn about this in accessibility tutorials or W3C documentation! The only way to discover these issues is to use many screen readers for a long time.
-
-What are some accessibility hazards---or even mild annoyances---you experience, that you _don't_ think most <abbr>a11y</abbr> practitioners learn about? Is there a common annoyance you wouldn't normally bring up because it seems "too minor"?
-