content/about/uses.gmi

@@ -44,7 +44,6 @@ My main computer is a 2013 HP Elitebook 840 G1. It has a dual-core Intel i5-4300
 * RustScan (don't use it on max settings without permission)
 * q, a DNS client that supports DoH, DoH3, DoQ, and ODoH.
 * rnp, a ping tool that supports TCP and QUIC "pings" to estimate handshake latency.
-* subfinder, Project Discovery's subdomain enumeration tool
 * both curl and xh for HTTP testing.
 * kinvolk's wrk2 fork and bombardier for HTTP load-testing
 * ssh-auditor

content/about/uses.md

@@ -80,7 +80,7 @@ Firefox
 : Default browser for most web pages. Trades some security for convenience. My setup is fingerprintable AF.
 
 Chromium
-: Used for web apps, security-sensitive work, and for certain specific web development tasks (Firefox is more than enough for most development tasks). Distribution packages of Chromium typically weaken many of its exploit mitigations (e.g. CFI), so I use [Thorium](https://github.com/Alex313031/Thorium) for now.
+: Used for web apps, security-sensitive work, and for certain specific web development tasks (Firefox is more than enough for most development tasks). Distribution packages of Chromium typically weaken many of its exploit mitigations (e.g. CFI), so I use [Thorium](https://github.com/Alex313031/Thorium) for now. Eventually, I might switch to [Hexavalent](https://github.com/Hexavalent-Browser/Hexavalent) once it's ready.
 
 Tor Browser
 : For anonymity (Safest level, or in Whonix at "Safer").
@@ -118,14 +118,11 @@ Every administrator needs some tools to test their servers.
 [RustScan](https://rustscan.github.io/RustScan/)
 : A port-scanner that can scan all 65 thousand ports in _seconds_. It optionally integrates with nmap. Don't use it on someone else's server without permission; this thing is brutal.
 
-[rnp](https://github.com/r12f/rnp)
-: A "layer-4 ping tool" that can measure the round-trip time of a plain TCP or QUIC connection, rather than using ICMP. Can also do light port-scanning.
-
 [q (DNS client)](https://github.com/natesales/q)
 : A DNS client that supports DNS-over-TLS, DNS-over-HTTPS, DNS-over-HTTP/3, DNS-over-QUIC, and Oblivious DNS-over-HTTPS. It sports a wide variety of options that aren't present in other `dig` replacements.
 
-[subfinder](https://github.com/projectdiscovery/subfinder)
-: Project Discovery's subdomain enumeration tool
+[rnp](https://github.com/r12f/rnp)
+: A "layer-4 ping tool" that can measure the round-trip time of a plain TCP or QUIC connection, rather than using ICMP.
 
 [cURL](https://curl.se/) OR [xh](https://github.com/ducaale/xh)
 : cURL supports a wide variety of features, protocols, TLS libraries, etc. `xh` is more focused on HTTP. I like to use both; when I don't need the features of cURL, I use xh for its simple color output and HTTPie-like syntax. Plus, it's nice to be able to test a server with two different HTTP+TLS implementations.

content/notes/ui-toolkits-accessibility-gap.md

@@ -1,20 +0,0 @@
----
-title: "UI toolkits and the accessibility gap"
-date: 2023-02-16T19:01:11-08:00
-replyURI: "https://www.warp.dev/blog/why-is-building-a-ui-in-rust-so-hard"
-replyTitle: "Why is building a UI in Rust so hard?"
-replyType: "BlogPosting"
-syndicatedCopies:
-    - title: 'The Fediverse'
-      url: 'https://pleroma.envs.net/notice/ASl0lOGNcl5GNJL6Jc'
-    - title: 'Lobsters'
-      url: 'https://lobste.rs/s/coy6gt/why_is_building_ui_rust_so_hard#c_f6rvfi'
----
-How does Warp stack against other toolkits when it comes to accessibility and system integration?
-
-In my system settings I set colors, default fonts (with fallback and hinting settings), animation preferences (reduce/eliminate animations), disable overlay scrollbars, set buttons to include text where possible, enable dark mode, configure keyboard shortcuts, and sometimes enable a screen reader. Windows users can enable High Contrast Mode to force their preferred palettes. To what degree will this toolkit respect these settings?
-
-On Linux: the only options I know of with decent system integration, accessibility, and some presence outside the Freedesktop.org ecosystem are are Qt, GTK, and the Web. Flutter falls flat, with outstanding WCAG level A blockers like functional keyboard navigation and basic levels of customization (e.g. disabling animation); relevant issues typically get de-prioritized. This is despite its massive funding and development efforts, so I'm not optimistic about other contenders.
-
-[AccessKit](https://github.com/AccessKit/accesskit) looks like a start for cross-platform interoperability between accessibility APIs. Until it's ready, support for each platform's accessibility APIs and screen readers will need to be implemented and tested. It's a monumental task. I worry that **releasing yet another inaccessible toolkit will merely increase the disability gap.**
-