BLUESKY ／ ATPROTO ／ FROM JAPAN
Four pieces on the blue sky
Bluesky is the largest bird in a sky called the Atmosphere. It is not the only one. Photos, blogs, git, weather stations and Lego all fly there too.
Almost all of it is written in English. Read only Japanese and the sky looks like it holds one bird. These four pieces map the other side of that wall, from the Japanese side.
All four are now in English. They were written in Japanese first, which shows: the vantage point is a Japanese reader looking at a mostly English ecosystem. The numbers were counted here and can be reproduced.
THE FOUR
Where a post is stored, and what it passes through before it reaches a screen. Four roles instead of one company, and an account you can carry away whole. Written so a twelve-year-old can read it. Six pairs of promise and reality, stated plainly.
Services running outside Bluesky, sorted by genre: clients, photo, longform, audio, tools, and the groups building their own stack (Blacksky, Eurosky, Gander). Every entry carries a link and a verified year of first appearance.
Bluesky does not reach ordinary users in Japan, and the cause is not bad explanation. Not switching is the correct calculation. Then a count: how many Japanese institutions actually claim a handle. Includes the correction after the first count was wrong.
Things that were proposed once and never built, pulled from 442 forum topics. What is missing is not ideas or permission. It is the second person. Four ways a proposal dies, and where to go if you want to be the second. Three new ideas, CC0.
IF YOU READ ONE
It is addressed to you. The inventory was pulled from discourse.atprotocol.community, which is written in English, by people who are mostly not in Japan. Every stalled proposal in it is waiting for a second implementer.
The finding, in one line: a record format written by one person is that person's private notation. It becomes shared infrastructure at n=2. The two community lexicons that shipped, standard.site and badges, both started with three people at one table. The ones that stalled started with one.
The most common way a proposal dies is not rejection. It is praise. Someone replies "this is great and makes total sense," and that is the end of it. Agreement takes the place of adoption.
ABOUT
Nighthaven (@moja.blue). A linguist by trade, not an atproto developer. Which is why it is written for people who are not one either.
The numbers were counted by hand and the method is stated on each page. Anyone can reproduce them. One count was wrong, was corrected after a reader pointed it out, and the correction is left in the text rather than quietly patched.
The three new ideas in 04 are CC0. No permission, no credit, no notice required.