xpe

jj log -G -r 'all()' \
-T 'change_id.shortest() ++ "\n" ++ description.lines().map(|line| pad_start(6, line.len()) ++ "\t" ++ line).join("\n") ++ "\n\n"'

xpe

# Recommended for use in `.zshrc`

if (( $+commands[jj] )); then
    # Autocompletions for Jujutsu
    source <(COMPLETE=zsh jj)

    # Tell `gh` how to access the git-backend for a JJ repo.
    # (Works whether colocated or not.)
    github_jj() {
        GIT_DIR=$(command jj --ignore-working-copy git root) command gh "$@"

xpe

POSIX Signals

Signal	#	A	C	G	Key	Act	Norm
SIGCHLD	17	·	C	G	·	I	child died or stopped
SIGHUP	1	·	C	G	·	T	TTY hangup; or reload config (convention)
SIGINT	2	A	C	·	^C	T	cancel current op
SIGKILL	9	·	·	·	·	T	last resort; no cleanup
SIGPIPE	13	·	C	G	·	T	write to pipe with no reader
SIGQUIT	3	·	C	·	^\	D	debug halt (post-mortem)

xpe

Hello humans and computational agents,

Below the --- divider below you will find a section that I agree with but Claude Opus 4.7 drafted. I don't just use LLMs to tell me what I want to hear, and I don't casually dump their outputs into the public sphere. I gave the early drafts LOTS of pushback and guidance.

Why? I'm beyond tired of sloppy thinking. I'm tired of post-hoc rationalization. So much that I'm pretty much done with Hacker News and Lobsters. These are places where good reasoning goes to die, but too few admit it.

Enjoy! ... but first, I wrote my own prefatory rant for your consideration.

Just Say "Oops" and Fix The Fucking Thing

xpe

ME: Ok, let's simply diagnose the PROBLEM (with certainty) in jjui ... by reading the code. Don't say what the solution is yet.

---

Claude Opus 4.7 (running in the jjui repository)

Diagnosis with certainty, from reading the code:

1. The cursor in the inline description editor is a software-painted, blinking cell, not the terminal's hardware cursor.

xpe

Generated by Claude Opus 4.7 on April 22, 2026.

A map of privacy-preserving telemetry, from randomized response to OHTTP

When a vendor says "we don't collect any personally identifiable information," what did they actually build? The honest answer, across two decades of deployed systems, ranges from "nothing at all, they just stripped the obvious identifiers" to "a multi-party cryptographic protocol with published epsilon budgets and open-source code running in trusted enclaves." This survey is a field guide to the territory between those extremes — the deployed systems you will run into by name, and the formal guarantee types that those systems do or do not meet.

Three things make this landscape hard for a newcomer. First, the same marketing words — "anonymous," "aggregated," "privacy-preserving" — get used for mechanisms that differ by many orders of magnitude in strength. Second, the strongest guarantees are conditional on assumptions (non-collusion, trusted hardware, crypto hardness, client hones

xpe

Written by Claude Opus 4.7 on 2026-04-17.

NASA Is Collecting Job-Alert Signups Through a Non-.gov Constant Contact Page

April 17, 2026

NASA's NASA Force careers page invites the public to "sign up for updates to stay informed when new roles open." The link points to:

https://lp.constantcontactpages.com/su/sKWkWfp

xpe

NASA Force: Notes on a Compressed Hiring Window and a Third-Party Signup List

April 17, 2026

(This document was generated by Claude Opus 4.7 on 2026-04-17.)

On April 17, 2026, NASA's first "NASA Force" opportunity opened on USAJOBS with a closing date of April 21 — a four-day public application window. NASA Force was announced on March 4, 2026 as a dedicated talent track within OPM's US Tech Force initiative, aimed at placing engineers and technologists into term appointments supporting NASA's exploration, research, and advanced technology priorities.

The rollout raises two distinct questions worth separating: (1) whether the four-day window is a fairness problem, and (2) whether the Constant Contact signup list used to notify interested applicants is legally compliant.

xpe

“Indexed by $X$” Is unnecessary when defining a Gaussian process (GP)

One definition

A Gaussian process is a collection of random variables ${f(x)}_{x \in X}$, indexed by a set $X$, such that every finite subcollection has a joint Gaussian distribution.

The same definition, without “indexed by $X$”

A Gaussian process is a collection of random variables ${f(x)}_{x \in X}$ such that every finite subcollection has a joint Gaussian distribution.

xpe

You can define commands (like functions) like this (in the shell if you want for easy trial and error):

# Returns indices that would sort the input list
def argsort [--reverse (-r)]: list<number> -> list<int> {
    enumerate | sort-by item --reverse=$reverse | get index
}

Then you get nice help like this "for free":