August 1–7, 2026

Observation

On the night of August 4 the Japanese-language timeline turned on itself. Open a post, and a name sits under it: so-and-so liked this. "ホントに(○○さんがいいねしました)が表示されてる…戦をはじめたいのか…?" — it really does say who liked it, do they want to start a war? "迂闊になんでもいいねできなくなった" — now I can't like things carelessly.

Nothing in the data had changed. A like on this network is a public record. Anyone can read it off anyone's PDS, and always could. What changed was one line of display, and that line was not handed to everyone. It is on some people's screens and not on their neighbours'. Nothing in the interface tells you which side you are on.

Curated Posts

Proposition

Bluesky's promise is that selection happens at the reading end. Issue #3 was about exactly that: through the Kumamoto earthquake, people covered for a missing publisher with feeds they wrote themselves. Anyone can write a feed. That part holds.

This week exposed the layer underneath it. You write the feed; the client is handed to you. known likers is a prototype behind a gate, the gate decides what your post page looks like, and no part of the interface reports which side you are on. It took two users comparing screenshots to establish what was on their own screens. Reader-side sovereignty assumes the readers are looking at the same thing. That assumption came apart this week over one line of text, in a feature its own authors marked as not ready.

The same week supplied the counterweight. The gate cannot be chosen; the feed can be written. Ø does not filter on content. It filters on the absence of a measurement: a post leaves the instant anyone reacts to it. You cannot change the screen you are handed. You can build the other one all the way down to refusing to count.

Nobody is looking at the same Bluesky. The one page that stays in your hands is the one you wrote.