2 Commits

Include renames

Author	SHA1	Message	Date
Ilker ManapandClaude Opus 5.5	11231d8c2b	The portal in English and Turkish: a catalogue per language, a switcher at the foot of every page, landing.language, Turkish numbers and dates ... Every template and handler message in internal/web goes through a JSON catalogue under internal/web/locales/<code>/, with English as the fallback. The language is the person's choice (a cookie set by /_lang/{code}), else Accept-Language, else landing.language. Tests refuse a key some language lacks, a translation with other arguments than English, and template text left in English. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>	2026-10-05 00:12:53 +02:00
Ilker ManapandClaude Opus 5	8d35faf6f8	Give the landing page somewhere to send people ... The page explained the API, said keys come from an operator, and left the reader there. Someone who reaches the address without a key had no route to getting one, which is where onboarding stopped. `landing.contact` is that route, because the gateway cannot guess who to ask. An address becomes a mailto link, an http(s) URL stays a link, and anything else — a channel, a queue, a person — is shown as text. Other schemes are never linked: this string comes from configuration, configuration is not always written by whoever runs the gateway, and a javascript: href on a page served to every visitor is a short path to a stored XSS. Escaping the text does not make a scheme safe. Unconfigured, it now says something rather than nothing, and the page explains that a key arrives as a one-time link so the reader knows what to expect before it lands. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-09-16 09:22:42 +02:00