Build 4
9 September 2026 TestFlightOne feature, and it belongs to somebody else. Michiel Nieuwenhuizen, who writes whichbachcantata.be, has kindly given permission for his writing to travel with the app — so three cantatas in five now carry a paragraph about the work, credited and linked back to the essay it came from.
-
Commentary on a cantata, by whichbachcantata.be
It sits above your own notes: two or three sentences on the work, with the essay it was taken from named underneath and a link through to read the rest on his site. Editing it keeps your version and the original underneath, the same way a catalogue correction does — the credit changes tense rather than disappearing.
105 cantatas have none, and that is the rule working rather than a gap to fill. The site's essays are written per cantata day, not per cantata, so a paragraph is attributed to a work only when it names exactly one of that day's own cantatas. The rest compare two works or discuss the feast and name none. Splitting a comparison in half would file text about one cantata under another's name — the same judgement the streaming-link matcher makes about a plausible wrong answer.
-
About names the source too
Each paragraph already said where it came from. The About screen now says the app carries someone else's writing at all, with a link to the site — which a reader would otherwise have to infer from whichever cantata they happened to open.
The permission is the whole licence, so the app is built to honour it
exactly: no paragraph can appear without its source and link — the build
fails if one does — and removing the text again is a single flag,
--no-commentary, one rebuild and one release. The check that
used to keep this text out of a shipping build has reversed rather
than been deleted: it now fails when the commentary is missing,
because the source files are read from a working copy the app's repository
does not contain, and a build made without them would look perfectly
healthy while the section silently vanished from 159 works.