0.9.6 — one optical frame

A second profile went up beside the feed, and in the process it turned out the first one was too big. Not in the code — in the eye. Every icon had the same box size, and that had been taken as settling the matter.

It does not settle it. The drawings come from different sources with different proportions: the feed is a square, the f a narrow column descending below the baseline, the butterfly lies wide. The eye compares the extent of the ink, not the size of the box, so a column filling the box top to bottom reads as larger than a square that leaves a margin.

Every drawing now gets the same optical frame: its outline reduced to seventeen units on the longer side and centred in a field of twenty-four. The factors are computed from the path outlines rather than eyeballed, and they sit in the code with a comment — because replacing a drawing means recomputing them with it, or one icon starts standing out again.

The longer side decides the scale, not the height. Were height to decide, the butterfly — wider than it is tall — would spill sideways out of the row, and we would be back at the same problem turned ninety degrees.

Profiles are now one component rather than one per service, and their order belongs to the engine rather than to configuration. Instances should look the same regardless of the order in which they added their accounts — that is not a content decision and there is no reason to hand it over.