Capture the SCP stall as a three-run experiment

The upload that races to 5%, pauses for minutes, then crawls is specific enough to diagnose instead of merely work around. Repeat the same representative file with scp -vvv, then once with -4, and once with -O; note the timestamp and last verbose line before each pause. Modern scp uses SFTP by default, so the legacy-protocol run cleanly separates transport behaviour from the remote filesystem or network path. If only IPv4 helps, investigate the IPv6 route or MTU; if both protocols stall at the same byte count, capture interface counters and a short packet trace next. The useful outcome is not a bag of SSH tweaks, but one variable that reliably moves the pause.

• OpenBSD scp(1) manual
• OpenBSD ssh_config(5) manual
• Wireshark TCP analysis documentation

Ship the memorable avatar URL, then probe what is missing

The fact that /.well-known/avatar keeps coming to mind is a good reason to implement the tiny personal convenience now, without waiting for a standard. Add an extensionless endpoint that redirects to the canonical image, check its Content-Type, caching, and behaviour under HEAD, then use that URL the next three times a profile asks for an avatar. Keep a short note of what a real client would still need—dimensions, variants, alt text, or content negotiation. That turns an appealing web-shaped idea into evidence about whether the simplest convention is sufficient, while keeping the distinction clear: the path is an experiment, not currently an IANA-registered well-known URI.

• A Well Known URL For Your Personal Avatar
• RFC 8615: Well-Known URIs
• IANA Well-Known URI registry

Test for mastery without making the first task miserable

The appeal of Vim, Photoshop, and mode-heavy music hardware suggests a useful design question for the tools you build: which complexity rewards learning, and which merely taxes memory? Pick one frequently used interface and write down a novice task plus an expert task. Time both today, then add exactly one accelerator—perhaps a shortcut, command palette entry, or remembered default—without hiding the obvious path. Retest after a week. If the expert path becomes faster while the novice path remains discoverable, you have earned complexity; if both users must remember an invisible mode, the interface is probably just carrying accidental friction.

• Flexibility and efficiency of use
• Progressive disclosure
• Vim user manual: getting started