25 Commits

Include renames

Author	SHA1	Message	Date
devsyncwrldandClaude Opus 5	a41a944742	feat(chat): @everyone mention ... Rides the existing `<@id>` token: `everyone` already matches the parser's `[a-zA-Z0-9_-]+`, so the markdown pre-processor, the inline renderer and the badge pick it up with no second syntax. User ids are snowflakes, so the literal `everyone` cannot collide with one. Gated on a new MENTION_EVERYONE permission rather than being open to all — otherwise a role can never take it away. Granted to @everyone by default: on a small instance the ping is a convenience, not a weapon, and an owner who disagrees can deny it and grant it to a role instead. Two things that would each have made the gate a no-op: - DEFAULT_EVERYONE_PERMISSIONS only applies at space creation, so spaces that predate the bit would have had every @everyone mention silently stripped. A boot-time backfill ORs the bit into @everyone roles only (`id = space_id`), leaving other roles alone so a later denial is not overruled on the next restart. Verified against a copy of the production database: three roles moved by exactly 2^15, non-@everyone roles untouched, second pass a no-op. - Enforcement covers edit as well as create; without that, posting a plain message and editing it is the way around the permission. A message that lacks the permission is not rejected — losing what someone wrote over one token is worse than posting it. The token is demoted to the literal `@everyone` text they typed: the message reads the same and rings nobody. Code spans and fences never ping. People paste payloads and snippets into chat, and a paste should not ring everyone's client. The same rule decides the row highlight and the notification sound, so the three cannot disagree. Verified: web build, server typecheck, 504 web tests, 804 server tests. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-02 22:10:56 -03:00
devsyncwrldandClaude Opus 5	699855849d	feat(i18n): translate the five systems users actually see ... Ordered by what the group hits, not by string count. - Chat system messages ("X added Y to the group") and their sidebar preview twin. These are content, not chrome, so they sat in English in the middle of conversations. - Login, register and the invite landing page — the first screen anyone invited to the instance sees. - Voice — controls, connection info, the mobile join sheet, settings tab. - Mobile screens. - Settings navigation across space, user and instance, plus Discovery and join requests. Three call sites build strings outside a component and so read the locale directly rather than through the hook: the sidebar preview formatter, the connection-info track labels, and MobileShell's screen map — which holds plain functions that are *called*, not rendered, where a hook would run under whichever component invoked the map. Each says so at the definition; all three re-render often enough that a language switch shows through promptly. Adds a test for a mistake made three times in this series: a file with an exported component plus a private sub-component, where only the exported one got the hook. tsc catches it, but only after a full build and without naming the component. The test names it, and also flags the inverse — a hook placed below an early return, which tsc accepts and React breaks at runtime (this project shipped that once, as error #310). Verified by mutation: removing a hook makes it fail and print the component. Dictionary is at 856 keys, en and pt-BR at exact parity. Verified: web build (tsc + vite), 492 web tests. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-02 21:13:54 -03:00
devsyncwrldandClaude Opus 5	94f5da4013	feat(i18n): translate five more systems, and unify the permission labels ... - Space settings > Overview — identity, icon, banner, transfer, delete - Space settings > Members and Bans - Space settings > Roles, including the whole permission table - Category settings — rename, privacy, overrides, delete - Instance settings > General — name, discovery, GIF search The permission labels were duplicated: the roles panel carried one English list and the channel/category override editors carried another. Both now read a single `perm.*` set, so renaming a permission lands in all three at once instead of one and a half. This removes the `channel.perm.*` keys added two commits ago rather than adding a third copy beside them. Same pattern as before for anything chosen outside the render: the roles panel's permission groups and the category's override definitions hold keys and resolve them where they render. The category delete dialog emphasises the category name, so its sentence is split around the placeholder rather than interpolated. Dictionary is at 723 keys, en and pt-BR at exact parity. Verified: web build (tsc + vite), 490 web tests. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-02 20:49:25 -03:00
devsyncwrldandClaude Opus 5	4fd6ac890c	feat(i18n): translate five more systems ... - Settings > Voice: video — preview, permission states, camera picker. This closes the Voice & Video tab; input, output and video are all done. - Create channel / category / space - Group DMs — new DM, add friends, group settings, leave - Join a space — discovery, invite code, and both federated auth phases - Delete account, transfer ownership, and the top-level error screen Three patterns worth noting. Strings that are chosen in a helper or held in state (the camera's hard-blocked copy, its preview errors, the space visibility options, the invite failure reasons) now travel as translation keys and are resolved where they render, so switching language re-labels what is already on screen. Sentences that wrap an emphasised literal — the host name when joining, the space and member names when transferring — are split around their placeholder instead of interpolated, leaving word order to the translation. And `CreateChannel` mapped over `(t) =>` for the channel type, which shadowed the translator; the loop variable is now `channelType`. The error boundary in main.tsx is a class component, so it reads the locale once per render via `translate` rather than the hook — correct here anyway, since an error screen has no reason to re-render on a language switch. Two GroupDmSettings tests located the name input by its aria-label, which this change translates. They now use the `data-group-dm-name-input` attribute the input already carries, matching how the rest of that file locates elements — and no longer break when copy changes. Dictionary is at 595 keys, en and pt-BR at exact parity. Verified: web build (tsc + vite), 490 web tests. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-02 20:38:54 -03:00
devsyncwrldandClaude Opus 5	115c81cba3	feat(i18n): translate five more systems, and check for updates more often ... Update cadence: the desktop app checked once ten seconds after launch and then every four hours. A release published while the app sits open went unnoticed until the next poll — which is exactly what happened with 1.4.0. It now polls every 30 minutes and also checks when the window regains focus, throttled to one check per five minutes so alt-tabbing does not hammer the feed. `lastCheckAt` is stamped from the `checking-for-update` event rather than by the callers, so a manual check from the settings panel counts too. The focus listener is on `app`, not on mainWindow, because the window is destroyed and recreated when closed to tray. Translations, five whole systems: - Settings > Desktop (autostart, updates, instance) - Settings > Voice: output device, which completes that tab - Settings > Keybinds, including the action names and conflict prompt - Settings > Account, the largest — profile, password, detached-instance notice, danger zone - Explore spaces Two sentences wrap a literal that must not be translated (the `input` group name, the `user@instance` example). Those are split around a placeholder rather than interpolated as text, so a translation keeps control of the word order on both sides of it. Keybind action labels gained a `labelKey` alongside the English `label`, which stays for non-React callers. Verified: web build (tsc + vite), desktop typecheck, 490 web tests. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-02 13:38:28 -03:00
devsyncwrldandClaude Opus 5	860f02b2c1	feat(channels): rename channels, and quieter defaults for sound and streams ... Four owner requests in one pass. Rename: the PATCH /api/channels/:id route already accepted a name and a topic, and the API client already exposed it — the only thing missing was a way to reach it. The channel settings Overview tab now edits both, gated on MANAGE_CHANNELS like the server is, with Save/Discard appearing only when the form is dirty. The server's lowercase-and-hyphenate rule moved to @backspace/shared so the field can show what a name will actually become instead of letting it change shape on save; one copy of the rule, used by both sides. Stream volume: someone else's screen share now starts at 50 instead of 100 (DEFAULT_STREAM_VOLUME). The publisher boosts system audio before sending, so the old default arrived far too loud for a viewer who never touched the slider. Only the default moves — the slider still covers the full range and a value the user set is still persisted. Sound effects: SFX_BASE_VOLUME 0.8 -> 0.4, halving every cue. The .ogg files were left alone; they already peak below full scale, so the harshness was level, not recorded distortion. Every SFX playback path goes through getSfxVolume(), so this is the single knob. Translations: channel settings (including the override editor's permission labels), the friends page end to end — tabs, lists, requests, the add tab and discovery cards — the invite modal including its per-invite failure reasons, and the group-DM member actions. Failure reasons are carried as translation keys rather than finished text, so results already on screen re-label when the language changes. Verified: web build (tsc + vite), server typecheck, 490 web tests, 804 server tests. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-02 11:59:25 -03:00
devsyncwrldandClaude Opus 5	7f08384372	feat(expressions): pickers and upload for emojis and stickers ... Completes the feature: the tables existed but nothing could be put in them. Space settings gain an Emojis & Stickers panel behind MANAGE_SPACE, with a 512KB ceiling — both are fetched on every message that uses them, so weight matters more than fidelity. The suggested name is pre-normalised so the common case needs no typing, and a name collision reports itself distinctly from an upload failure: the corrective action is different. Custom emojis join the emoji picker as their own category. They have no native character, so selecting one inserts :name: — the same text the renderer resolves back to an image, which also means copying a message yields something that still reads. Stickers get a picker tab that only appears inside a space, since that is where they exist, and send immediately on click: a sticker is the whole message, so parking it in the composer to await Enter would make no sense. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-01 18:25:10 -03:00
devsyncwrldandClaude Opus 5	50a8f12c77	feat(search): inline filters, and translate the search UI ... The filters themselves already existed end to end — the server takes q, from, has, before and after, the API client passes them, and the popover has fields for each. What it lacked was discovery: the panel sits behind a button, so the capability was invisible. Typing 'de:fulano' or 'has:image' straight into the search box now applies the same filters. Keys are accepted in both languages, since the app is bilingual, and an unrecognised token falls back to being search text — otherwise a message containing a URL or 'algo:coisa' would become unfindable. Inline filters win over the panel's: whoever just typed one is expressing the more recent intent. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-01 17:49:05 -03:00
devsyncwrldandClaude Opus 5	c4158ee245	docs: retire the fixes that shipped and were confirmed in use ... Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-01 17:13:30 -03:00
devsyncwrld	61c68761df	i18n: translate the channel and member sidebars ... Clears the two remaining rounds owed under the fork's per-update translation rule. Covers channels, direct messages, the context menus, the inline voice settings and the member list's loading and grouping labels. The member grouping needed care: one function returns either a fixed label or a role's own name, and role names are user data that must never be translated. It now marks only the fixed cases and the component resolves them at render, leaving role names untouched. The function is not a component, so it cannot call the hook itself.	2026-09-01 17:03:48 -03:00
devsyncwrld	c04b8b47eb	i18n: translate the chat composer and messages ... Catching up on the fork's rule that every update also translates one existing system — three updates went by without one. The composer's placeholder takes the channel as a parameter rather than being concatenated, since Portuguese puts the channel elsewhere in the sentence than English does. The translation hook is bound to `tr` in these two files, not `t`: both already use `t` for transfer records in inner scopes, which shadowed the function and made it uncallable exactly where it was needed.	2026-09-01 16:59:50 -03:00
devsyncwrld	d525bbb8c5	feat(desktop): capture system audio with process isolation ... Electron's audio: 'loopback' captures the whole output mix, this app's own playback included — so everyone else's voices went back out inside the share and each listener heard themselves. Not acoustic echo but a digital copy of the output, which is why headphones never helped, and why shareAudio already defaulted to off in the desktop app. Electron offers no way to exclude our own audio: the docs allow only 'loopback' or 'loopbackWithMute', and the handler discards the renderer's constraints (restrictOwnAudio never arrives). electron-native-screenshare does it at the OS level — WASAPI process loopback on Windows — capturing only the shared window when its pid resolves, and otherwise everything except us. The module hands raw PCM to the main process, so it crosses IPC and is scheduled onto a running cursor in Web Audio to become a MediaStreamTrack, published as ScreenShareAudio. Loading is optional and failure degrades to a silent share rather than blocking the app or the screen share. The browser path is untouched: Chrome honours restrictOwnAudio and has no echo. Verified by typecheck (web and Electron main) and the web suite. The audio path itself cannot be exercised here — no Windows, no Electron, no audio device.	2026-09-01 00:56:34 -03:00
devsyncwrld	310e9b86be	docs: diagnose the screen-share audio echo	2026-08-31 22:58:59 -03:00
devsyncwrld	e291b5e411	docs: drop delivered rows from the pending sections	2026-08-31 22:40:44 -03:00
devsyncwrld	c899253e52	fix: soundboard upload in Electron, and Spotify sync/disappearing/progress ... Soundboard: naming a clip used window.prompt, which Electron does not implement — it returned nothing, the flow aborted in silence, and adding a sound worked in the browser while doing nothing at all in the desktop app. Replaced with a two-step field inside the popover, identical in both. Spotify, three separate defects behind the two symptoms reported: Out of sync — a 20s poll stacked on the activity store's 5s debounce left everyone else on the previous track for up to 25s. The next poll is now scheduled just past the current track's end instead of on a fixed interval, and a track change bypasses the debounce (it happens once every few minutes; the debounce exists for chatty producers). Vanishing — a paused track, and the silent gap Spotify reports between two songs, both cleared the activity outright. Pausing is now carried as state rather than absence, and an empty answer is tolerated for 25s before the block comes down. Progress bar — timestamps are computed with the server's clock and were drawn against the viewer's, so any drift displaced the bar; and it kept advancing after a pause until the next poll. The ready payload now carries server time so each client can correct its own offset, and the bar freezes when paused. Tray, native notifications and system audio in screen share were all found already implemented and wired end to end; recorded in the roadmap rather than built again.	2026-08-31 22:39:28 -03:00
devsyncwrld	ff55d9d486	docs: plan desktop features and diagnose the Spotify sync bugs	2026-08-31 14:02:21 -03:00
devsyncwrld	e58021408c	docs: record the Electron window.prompt soundboard bug	2026-08-31 14:00:41 -03:00
devsyncwrld	2afe3453f0	docs: record four approved features not yet started	2026-08-31 13:57:01 -03:00
devsyncwrld	ef5545465d	docs: mark GIF favourites, audit log and statistics delivered	2026-08-31 13:30:26 -03:00
devsyncwrld	0fc6abeb6e	docs: mark Spotify delivered, drop resolved items	2026-08-31 13:04:35 -03:00
devsyncwrld	c022f2795f	docs: record the i18n foundation and translation queue	2026-08-31 12:25:03 -03:00
devsyncwrld	89e13441c8	docs: record the pt-BR language rule and new system ideas	2026-08-31 12:18:33 -03:00
devsyncwrld	b92a0d837e	docs: update roadmap after mic test and activity work	2026-08-31 12:05:18 -03:00
devsyncwrld	37407a5ecd	feat(voice): open the profile card from voice participants ... The profile popout already existed and was reachable from eleven places — messages, mentions, avatars, member list, DMs, activity panel — but no voice surface opened it, so clicking someone during a call did nothing. Wire it into the voice user rows (VoiceChannel's sidebar list) and the name label on grid tiles, whose avatar was already a ProfileAvatar; the name beside it not reacting read as the click failing. Left mobile alone deliberately: MobileSpacesScreen already opens the profile from its row wrapper, and MobileVoiceJoinSheet would layer a history-pushed full-screen profile inside a bottom sheet, which cannot be verified here.	2026-08-31 11:49:57 -03:00
devsyncwrld	cad3867027	docs: add fork roadmap	2026-08-31 11:45:02 -03:00