Maurice
44c92052a3
Every page was read against the code on dev. What changed: - Pages that described 4.2 behaviour: satellite view on the vector maps, the mobile journal timeline, Collab with its fifth tab, the Review badge, clustered pins on the share page, the Leaflet preset list, the strict guard on fe80::/10, the invite link tools and their scopes, the Public API scope rules, the permission count in the plugin SDK. - Features of this release that no page mentioned: videos in a journal entry, receipts on an expense, the Google transit backend, routing counters, the rating on a place, the navigation menu, car stops, the manual school holiday catalogue and its MCP tools, the Dawarich panel in the Atlas, the release notes modal, plugin frames going fullscreen, the corridor call into the search provider hook. - Statements that sent an admin the wrong way: DEFAULT_LANGUAGE is not in the Helm ConfigMap, env.PORT cannot be changed on the chart alone, the rotation script does not cover the document sync credentials, event handlers cannot broadcast, there is no per user MFA reset in the admin panel, the demo user can edit, an unparsable APP_URL stops the server. - Updating gets a section for 4.3.0: the TREK Places API as the new default, the new variables, the Overpass timeout, SSO sessions on an OIDC only instance, the migration that puts booked nights on the drive.
4.1 KiB
Collab Chat
Chat with your group in real time, without leaving the trip planner.
Where to find it
Open the trip planner and select the Collab tab. If the Chat sub-feature is enabled, a Chat panel appears — on desktop as the left column, on mobile as the first tab in the tab bar.
The Collab addon must be enabled by an admin and the Chat sub-feature must be turned on. See Real-Time-Collaboration.
Sending messages
Type in the input field at the bottom and press Enter (or click the send button) to post. Hold Shift + Enter to insert a line break without sending.
Messages load in pages of 100. A Load older messages button appears at the top of the chat when older messages are available.
Images
A message can carry up to four images. Click the image button in the composer, paste them from the clipboard, or drop them onto the composer. JPEG, PNG, GIF and WebP are accepted, up to 10 MB each; TREK checks the file type and the extension, and anything else is refused with Only JPEG, PNG, GIF and WebP images up to 10 MB are allowed. Each picked image shows as a thumbnail above the input with an × to drop it again, and a message can consist of images alone, with no text. Sending an image needs the file_upload permission on top of collab_edit.
Emoji
Click the smiley-face button in the composer to open the emoji picker. The picker has three categories:
- Smileys — facial expressions and gestures
- Reactions — hearts, fire, thumbs, and similar
- Travel — planes, maps, food, cameras, and destinations
Emoji are rendered via Twemoji for consistent appearance across platforms.
Reactions
Right-click a message on desktop (or double-tap on mobile) to open the quick-reaction menu. Eight quick reactions are available: ❤️ 😂 👍 😮 😢 🔥 👏 🎉. Click any reaction to toggle it on or off. Reactions from all users aggregate beneath the message; hover a reaction badge to see who reacted.
Replies
Hover a message to reveal the action buttons. Click Reply to quote that message. A preview of the quoted text appears above your new message in the composer; click the × to cancel the reply. The quoted text is displayed inline inside your bubble when sent.
URL link previews
When a message contains a URL, TREK automatically fetches an Open Graph preview (title, description, and thumbnail image) and displays it below the message text. Only the first URL in a message generates a preview.
The fetch runs on the server, so it is kept on a short leash: only trip members can request one, the target must be a public HTTP(S) address (addresses on your own network are refused), a preview is remembered for ten minutes, and a member can trigger sixty new fetches a minute. A preview that is refused or runs past the budget is simply not shown — the message itself is unaffected.
Message styling
Your own messages appear right-aligned with a blue bubble. Other members' messages appear left-aligned with a gray bubble. The username is shown above the first message in a group of consecutive messages from the same person; the avatar is shown beside the last message in that group. Timestamps appear below the last message in each group.
Messages that consist of only 1–3 emoji are displayed larger without a bubble.
Deleting messages
Hover your own message to reveal the delete button (trash icon). The delete button is only visible when you have the collab_edit permission. Deleting replaces the bubble with an italicised notice — showing your username, "deleted a message", and a timestamp — visible to all members.
Read-only viewers
Users without the collab_edit permission can read all messages but the composer is disabled — they cannot send, react, or delete messages. The reply button is visible to all users, but completing a reply still requires collab_edit (the send button is hidden for read-only users).