kristianwindandClaude Opus 5
70d7398d5a
API-dokumentationen har fulgt med hele vejen — der er en prøve, der fejler, hvis en rute ikke står i openapi.yaml, og den fangede mig fire gange i går. Brugervejledningen har ikke fulgt med, og det er den, folk læser. Nyt: en side om beskeder — hvad der udløser en, hvorfor gentagne rettelser bliver slået sammen, push pr. apparat og mærket på ikonet. En om at åbne links i en anden browser, som mest af alt handler om, hvad en webside ikke kan: hverken se hvilke browsere der findes eller vælge mellem dem. Og en om tællingen af installationer, som ikke stod nogen steder overhovedet — en melding, der er slået til som udgangspunkt, har en pligt til at være skrevet ned, også når ingen har spurgt. Rettet: AI-siden beskrev to funktioner, hvor der nu er syv, og listen over hvad der sendes hvorhen var derfor forkert som en påstand om noget privat. Noter-siden manglede deling med en e-mailadresse og hvad `@Sofie` gør. Mail-siden manglede den anden vej ind i indbakken. Konfigurationen sagde stadig, at versionstjekket kun kunne se efter. Og tagbeskeden når nu frem. Den ER annonceringen — skrevet på produktets eget sprog til dem, der bruger det — og udgivelsen på GitHub blev fyldt med en autogenereret liste over commit-overskrifter i stedet, som er skrevet til dem, der læser koden. Nu står teksten øverst og listen under den. Linjen med linket til udgivelsen selv tages af: en side, der linker til sig selv, hjælper ingen. Dokumentationen bygges nu også på en PR. `mkdocs build --strict` fejler på et link til en side, der ikke findes, og at bygge først efter merge er at få det at vide på main. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2.6 KiB
Notifications
What other people did that you need to know about, and what the day has in it. Verdande tells you in three places at once, and they are the same thing said three ways: the bell in the header, a push to your devices, and the badge on the app's icon.
What causes one
| Somebody edited a note shared with you | Repeat edits fold into one line while it is unread |
| Somebody shared a note with you | Once, when it happens |
Somebody named you in a note with @ |
Instead of "edited a note" — one act, one message |
| Somebody gave you a task | Only on the change, and only to the person who got it |
| Somebody commented | |
| Today's plan, if you turned it on | In the morning, at the hour you chose |
| A new version is out | Administrators only, once per version |
Not your own actions: the server does not tell anybody what they just did themselves. And not everything that happens — a bell that rings at every change in a shared project is a bell people stop looking at.
Repeat edits are folded. A note is saved on every typing pause, so one person writing for five minutes would otherwise be twenty identical lines. While the message is unread, a further edit moves it back to the top and says who touched it last. Once you have read it, the next edit is a new thing to be told.
Push, and the badge
Settings → Beskeder turns on Web Push for the device you are sitting at, per device: the phone in your pocket and the laptop you have open are different answers, and a permission granted on one is not the other's.
The badge — the number on the icon in the Dock on a Mac, on the taskbar on a PC — needs the app to be installed (added to the Dock, or installed as an app in Chrome or Edge). Half the point of being told is being told while you are doing something else, and the icon is the only place the app can say anything then. It counts unread messages and goes down by itself as you read them. Firefox does not support it; nothing else changes there.
The sentence you see is written in your browser from what happened and who did it, so an English interface gets an English bell. The server's own wording is Danish and is used only for push, which has no dictionary to look a phrase up in.
Telling you about a new version
If the update check is on, administrators get one notification per version — never one a day about the same one — and it leads to Settings → Beskeder, where the button that restarts the instance to update it sits. With the check off, nothing is fetched and nothing is said.