wintermeyer/vutuv

Motivation We have the space there and it gives us a way to see everything at one glance as well as a possibility to jump to each one. Current UI Proposed UI

TL;DR: Some power users find vutuv's web chat GUI cumbersome and would rather read and write direct messages from a native app (phone or desktop). This issue is an open invitation to discuss how we could offer that. We want to collect ideas, and everything is on the table, including changing or replacing the current DM system itself. No decision has been made; this is a request for comments. 🗣️ This is a discussion/RFC, not a finished plan. Please poke holes, add options we missed, argue for replacing things wholesale, or tell us an idea is bad. The goal is to find the approach that makes the most sense. The problem vutuv ("DM" = direct message) has an internal, web-based 1:1 chat. It works, but heavy users don't enjoy living inside a browser tab for messaging. They'd prefer a real native client: a fast mobile/desktop app with push notifications, the way they already use other messengers. The original spark for this issue was: "Could a user be reachable internally as username@v

TL;DR Ship a complete Spanish (es) interface: Gettext catalogs, both email bodies per mail, and the places that still hardcode en/de. How: docs/architecture/i18n.md has the surfaces, the traps and the step-by-step checklist. Follow it; this issue only names what is specific to Spanish. Scale: 3,933 UI messages plus 69 error messages, 28 mails × 2 bodies, 2 help pages, 253 country names. Spanish-specific Numbers: Spanish groups thousands with . and takes , as the decimal mark, like German. delimited_count/1 currently splits de against everything else. Register: formal usted, matching the German Sie. Endonym for @language_names: Español. Done when choosing Spanish shows the UI, flashes, error pages and every transactional mail in Spanish, with Spanish number and date conventions rather than the English fallback. An AI agent wrote this text in my name. I know that is problematic.

TL;DR Ship a complete French (fr) interface: Gettext catalogs, both email bodies per mail, and the places that still hardcode en/de. How: docs/architecture/i18n.md has the surfaces, the traps and the step-by-step checklist. Follow it; this issue only names what is specific to French. Scale: 3,933 UI messages plus 69 error messages, 28 mails × 2 bodies, 2 help pages, 253 country names. French-specific Numbers: French groups thousands with a narrow no-break space (U+202F) and takes , as the decimal mark, so it fits neither existing branch. delimited_count/1 currently splits de against everything else. Register: formal vous, matching the German Sie. Endonym for @language_names: Français. Done when choosing French shows the UI, flashes, error pages and every transactional mail in French, with French number and date conventions rather than the English fallback. An AI agent wrote this text in my name. I know that is problematic.