You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
h5p-author route 4: the source as a JSON block or file, and the build page's plain address; no link carries the source #208
0.10.1's route 4 has the model write the build page's link with the source in it as readable JSON (#206, #207). In ChatGPT on a free account (the owner, 2026-11-15) it broke:
ChatGPT's model escaped what it did not need to ({ as %7B, " as %22), but after the title it wrote spaces raw: "question":"What happens during evaporation?". A Markdown link holds no raw space, so ChatGPT showed the whole address as text, and the link it made stopped at the first space, after "What". The page got 283 characters of the source.
The address in angle brackets, […](<…>), which lets a link hold spaces in standard Markdown, rendered in ChatGPT as [Build and play it](: its renderer drops the <…> part.
So a link that carries the source depends on the model escaping every character of a long text, and ChatGPT's does not. The owner's call: no link carries the source. Route 4 hands over:
the whole source in one json code block, which the chat's copy button copies exactly;
the build page's plain address, https://missing-elements.github.io/h5p/build/, with the steps: paste the source into its box in place of the sample's, then Build. A source that names files: the page asks for them;
where a code tool runs, the source as a .source.json file too, which the page opens under Or open a file, and the line offering the build archive.
Outside a chat the source goes to that file instead of a code block. Routes 1 to 3, which build in the chat, are not part of this.
Activity