- Ya
- 28 Agosti 2026, 01:01 UTC
- Mwandishi
- Kamo
- Ahadi ya
- aeb7f2c
Two things the /kb page reported to anyone holding VIEW_KB_ARTICLES. The corpus. The audience chips an author ticks in the composer — Members, Team Members, Public — were never enforced for a human reader; KBService served every active article in the org. That is fixed server-side (kbservice 30f2bf9): a member who is not a team member now gets public + member articles, a team member gets all three tiers, and only published ones. This side follows it. The rail. The stat tiles read Everything / Published / In review / Drafts / Archived / Mine / Pinned / Gone quiet, for everybody. Those last four are a report on how the organization's editorial work is going, and reading it took nothing but the right to read an article. railFilters() now returns what the reader can act on. A maintainer keeps all eight tiles. Anyone else gets Everything and Pinned, plus Mine only if they can create an article to own one. The workflow tiles are removed rather than zeroed — the server sends a reader published articles only, so each would sit at 0, and a tile that always reads 0 is still a statement about what exists made to somebody who was not shown it. Published goes too: it would be an exact copy of Everything beside it. "Needs attention" is maintainer-only for the same reason — every row in it is a maintenance instruction. Who counts as a maintainer comes from the overview, not from re-reading the session's rights here. The server already had to answer it to filter the list; answering it twice, in two vocabularies, is how a rail ends up offering a tile the server only ever fills with nothing. It defaults to the reader's shape when absent, so a cached bundle against an un-rolled service errs narrow. clampFilter covers the case the stored preference creates: the rail selection is remembered per member, so a demoted maintainer would return to a DRAFT tile that no longer exists, an empty list, and nothing lit to explain it. The composer now says when an article has been addressed to nobody. Three chips off is left to mean exactly that on the server rather than being widened behind the author's back, so this is the only place they will ever be told. The two audience strings that described the old behaviour were renamed, not edited — translate.ts only queues a key that is missing or still equal to English. A 404 on an article now reads as "Article not found" rather than "Failed to load". Hidden and missing are deliberately the same answer, and "failed" would send a member to support over a system working exactly as intended.