1749 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
devsyncwrldandClaude Fable 5.1	872066e5be	feat: rebrand to Resenhacord with a new logo, and post a notice when a message is pinned ... Rebrand. The product name is now Resenhacord everywhere a person reads it: window title, tray, notifications, About panel, PWA manifest, page title, recovery and instance-picker screens, and the four i18n strings that named the app. Code identifiers (BackspaceElectronAPI, @backspace/* workspace names, the federation protocol) are unchanged — they are not a brand, and renaming them buys nothing but churn. AGPL notices and upstream attribution stay as they were. Two rename details that would each have hurt real users: - electron-builder's productName changed but appId did not. NSIS keys the installation on appId, so the updater replaces the Backspace install in place instead of leaving a second app beside it. - userData is keyed on app name, so the rename would have moved every install to an empty profile — logged out, instance URL gone. main.ts now walks a migration chain ("@backspace/desktop" → "Backspace" → "Resenhacord"), each step a no-op once its source is gone, and one whose target already holds data leaves it alone. Autostart lookups accept the old registry entry name too. Logo. Two speech bubbles in conversation, violet behind, rose in front with three dots — the front one is talking. Sources are hand-written SVG in assets/brand (square viewBox; the gap between bubbles is a mask, not paint, so the alpha-only macOS template keeps the silhouette). PNG sources are rendered from the icon SVG and the whole set — .icns, .ico, Linux PNGs, tray variants, favicons, PWA, maskable — comes from the existing gen-icons pipeline unchanged. Pin notice. Pinning a message now posts "X pinned a message to this channel. See all pinned messages." into the channel, the way Discord does, with two links: the message itself (jumps to it) and the pins panel. Space messages had no `type` column — only DM messages carried system events — so this adds one (migration 0018, default 'user', verified against a copy of the production database: 88 rows, all 'user'). The route inserts a type='system' row alongside the pin and broadcasts it as message_created, so the client renders it with the SystemMessage renderer it already has. Unpinning posts nothing; it is housekeeping, not news. System notices are excluded from the notification toast and the message sound — they are not from anyone. The pins panel and jump target are local state in MainContent; a notice deep in the timeline reaches them through two small uiStore requests (a counter and an id), neither persisted. Verified: web build, 506 web tests (2 new), server typecheck, 804 server tests, desktop typecheck. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>	2026-09-02 23:15:14 -03:00
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	1ec5d88fa2	chore: version 1.5.0 ... Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-02 21:58:05 -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	a54d998ba9	chore: version 1.4.0 ... Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-02 12:52:31 -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	293378293d	fix(ci): match release assets by name, and close the guard block ... Two defects, both mine, and the second hid the first. The cleanup built a regex and matched it against the jq line '<id> <name>', so the anchor in latest.yml could never match — it sits after the id. Only the .exe was removed, and each publish left another latest.yml behind. Gitea then served the older one, so the updater kept reporting the previous version as current: an update that exists and is never offered, with nothing logged anywhere. Filtering now happens inside jq, comparing the name directly. The guard meant to catch exactly that was missing its closing fi, so the step died on a syntax error before reaching it. Verified with bash -n this time, which is what should have happened before it ever ran on a runner. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-01 19:14:59 -03:00
devsyncwrldandClaude Opus 5	c5abb6fd64	chore: version 1.3.0 ... Carries the silent native notification, which lives in the Electron main process and therefore only takes effect from a new installer — the reason this release is needed beyond exercising the restart prompt. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-01 19:07:26 -03:00
devsyncwrldandClaude Opus 5	1fb61377b9	feat(notify): in-app notifications with the app's own sound ... The system balloon carries the OS notification sound, which does not belong to this app, and it only fired while the window was out of focus — with the app focused nothing appeared at all. Notifications now surface inside the window, carry the same synthesised timbre as the rest of the app's sounds, and clicking one opens the channel. The native balloon is kept for when the window is not visible, since an in-app card nobody can see is no notification, but it is now silent: the app plays its own effect instead. A focused window is notified only about other channels — announcing the conversation someone is already reading is noise. Also fixes the Gitea publish cleanup, which silently deleted nothing: it interpolated an Actions expression inside a bash , and when the pattern did not match, the loop passed over every asset. The release ended with two latest.yml files and the updater served the older one, reporting 1.1.0 as current — an update that exists but is never offered, with no error anywhere. The filter is plain bash now, logs what it found, and the job fails if more than one latest.yml survives. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-01 18:57:02 -03:00
devsyncwrldandClaude Opus 5	1a1067bbb6	chore: version 1.2.0 ... Pins, filtered search, custom emojis and stickers, and the in-app restart prompt. The prompt itself is only visible once an update is offered, so this release is what makes it observable. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-01 18:49:23 -03:00
devsyncwrldandClaude Opus 5	71d2109b2f	feat(desktop): in-app prompt to restart for an update ... The main process already showed a system notification when an update finished downloading, and nothing in the renderer listened — so the only cue vanished on its own and was missed by anyone not watching the desktop at that moment. A prompt now stays in the window until it is acted on or dismissed, with the restart wired to the install-update channel the preload already exposed. Dismissing is 'not now', not 'never': a later version reopens the prompt, since the version it refers to has changed. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-01 18:31:59 -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	7d003021d1	feat(expressions): custom emojis and stickers per space ... Emojis and stickers get separate tables on purpose: an emoji sits inside a sentence and a sticker is the whole message, so their sizes, limits and render paths differ. Emoji names are unique per space and restricted to letters, digits and underscore — :name: has to resolve to one image, and a space or colon inside the name would make the reference impossible to delimit. Sticker names are labels picked from a grid, so they accept anything. Rendering reuses the existing markdown pipeline by rewriting :name: into image syntax, which needs no plugin. Code spans and fences are left alone: text someone wrapped in backticks was meant to be shown literally, and turning it into an image would destroy what they wrote. Messages carry stickerId with ON DELETE set null — removing a sticker from the space must not delete the history of everyone who used it. The server refuses a sticker from another space, which would otherwise leak images between unrelated servers. Expressions load once per space and stay in memory: the message renderer consults the map for every :name: it finds, and a request per lookup would turn each message into a cascade. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-01 17:57:32 -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	4ceb5cd66a	feat(pins): pin messages to a channel ... Pinned state lives on the message rather than a join table: a message is pinned in exactly one channel, its own, so a separate table would add a join to every lookup and buy nothing. Every message now carries its pin state, so the timeline can mark a pin without a second request and the panel and the timeline cannot disagree. Toggling is deliberately not optimistic — the server refuses past the channel's limit, and showing it pinned before confirmation would lie in exactly that case. The pins list reuses the same assembly the channel history uses, extracted into one helper, so the two cannot drift apart in what they include. The migration also adds the (channel, user, created) index the filtered search will need, since both touch the same table and one migration is cheaper than two. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-01 17:45:33 -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	ce6bba0510	fix(ci): pulseaudio headers, and an ASCII release payload ... Linux got past pipewire and stopped on pulse/pulseaudio.h — the module compiles both backends, so both sets of headers are needed. Windows reached the upload and Gitea rejected the release creation with HTTP 422, 'invalid UTF-8 within /name': the JSON body carried accented text and the Windows runner's shell mangles the encoding on the way out. The payload is now ASCII, with a comment saying why, so it does not get 'improved' back into Portuguese. latest	2026-09-01 16:04:01 -03:00
devsyncwrld	9ea399ded5	fix(ci): install pipewire headers, and make the Gitea upload diagnosable ... Two separate failures on the first run. Linux could not compile the native module: it needs libpipewire-0.3-dev, which its README states and the apt list omitted. Windows built everything, native module verified, then died on the upload with a bare JSONDecodeError. The cause was curl -sf, which discards the error body, so a failed release creation surfaced as an empty pipe and no reason at all. The step now captures status and body and prints them, treats a failed create as possibly the other matrix job having just created it, and passes target_commitish so the tag can be created. Embedded python gave way to jq: a multi-line heredoc inside a YAML literal block ends the block at the first unindented line, which is how the file became invalid YAML in the first place.	2026-09-01 15:58:26 -03:00
devsyncwrld	9f7723d104	ci: build on GitHub, publish updates from Gitea ... GitHub stays the build machine — it has the Windows runners the native audio module needs — but the update feed moves to this fork's own Gitea. The GitHub repository is private, and electron-updater against a private GitHub repo needs a token inside the shipped app, which is a leaked token. Gitea serves release assets to anyone, so the installer carries no credential. The flow was verified end to end against the live instance before writing this: create release, upload asset, download anonymously. The release tag is fixed at 'latest' because electron-updater fetches latest.yml before it knows which version exists, so the URL cannot carry a version; CI replaces that release's assets each publish. electron-builder runs with --publish never since it cannot upload to Gitea, but still emits the latest.yml the updater reads. Needs a GITEA_TOKEN secret on the GitHub repository.	2026-09-01 15:49:25 -03:00
devsyncwrld	5b84843217	fix(screenshare): make shared system audio audible ... Listeners had to run the participant at 200% with attenuation off. Two causes, both on the publishing side. WASAPI returns the process mix at a level well below what a microphone track arrives at, so the track was quiet before it ever left the machine. A gain stage now boosts it, followed by a limiter — a compressor with a high ratio and fast attack — so the boost cannot clip loud passages. And the track was published with LiveKit's defaults, which are tuned for speech: mono, low bitrate, and DTX enabled, which stops transmitting during silence. On game and music audio that reads as thin and clipped. It now publishes with the music stereo preset, stereo forced, and DTX and RED off. Lives in packages/web, so it reaches the desktop app through a normal deploy — no new installer.	2026-09-01 15:36:55 -03:00
devsyncwrld	bd8decb4b3	fix(ci): actually compile the native audio module, and prove it ... The previous run went green and produced an installer with no system-audio capture in it — the exact silent failure this module exists to prevent. Two causes. electron-rebuild takes -w as one comma-separated list, not a repeated flag; passing it twice made argv.w an array and the CLI threw 'argv.w.split is not a function', which also broke uiohook-napi's rebuild that had been working. And pnpm 10 refuses to run a dependency's build script unless it is listed in onlyBuiltDependencies, so node-gyp never ran for it at all — the log said 'Ignored build scripts' and nothing else complained. Neither surfaced because desktop's postinstall ends in , which exists so contributors without build tools can install. That is reasonable locally and dangerous in CI, so the workflow now asserts a compiled .node exists and fails loudly when it does not, instead of trusting an exit code that was designed to lie.	2026-09-01 15:13:26 -03:00
devsyncwrld	52f43d4d61	build: record electron-native-screenshare in the lockfile ... The dependency was added to packages/desktop/package.json without regenerating the lockfile, so CI's --frozen-lockfile refused the install — correctly: a build that resolves fresh versions is a build that differs from what was tested.	2026-09-01 15:06:59 -03:00
devsyncwrld	7eaba5e3f3	ci: build only the architectures this group runs ... Windows arm64 doubled the slowest job in the matrix — two Electron distributions downloaded, native modules compiled twice — and nobody here runs Windows on ARM. Linux arm64 went for the same reason. Removing arm64 also retires the fpm step: electron-builder's bundled fpm is x86_64-only and failed on the arm64 runner, which is the only reason a native fpm was installed (ruby, ruby-dev, build-essential and a gem with native extensions, on every run). On an x86_64 runner the bundled one works. Matrix is now Windows x64 and Linux x64.	2026-09-01 14:02:54 -03:00
devsyncwrld	124db82a0c	ci: drop the macOS build from the release matrix ... Nobody in this group runs macOS, and on a private repository the macOS runner bills at 10x — it was the most expensive platform in the matrix, compiled on every tag for zero users. This edits a file inherited from upstream, so it will conflict on merges. That is the accepted cost: the alternative is paying for a macOS build indefinitely.	2026-09-01 14:00:12 -03:00
devsyncwrld	b4d001eb26	ci: add a fast Windows-only desktop build ... release.yml builds four platforms and publishes a release, which is right for a release and slow for 'give me an exe to test'. Wall time is set by the Windows job, which compiles native modules and downloads Electron twice because it targets x64 and arm64 together — and Windows-on-ARM is not something this group runs. This path builds one architecture, caches the Electron and electron-builder downloads (~100MB re-fetched every run otherwise), and uploads the installer as an artifact, so it needs neither a tag nor a version bump. Kept as a separate file: release.yml comes from upstream and takes merges, so editing it would conflict on every update. Cost matters too on a private repository: macOS runners bill at 10x and Windows at 2x, so the full matrix was paying for macOS builds on every tag.	2026-09-01 13:29:18 -03:00
devsyncwrld	60c51a1635	chore: version 1.1.0 ... First release built from the fork. electron-builder names artifacts and the GitHub release from package.json rather than the git tag, so the two have to agree or electron-updater compares mismatched versions and never offers the update. v1.0.0 is already taken by upstream's tag in this history.	2026-09-01 13:15:13 -03:00
devsyncwrld	d208b0c277	build(desktop): publish releases to syncwrld/resenhacord	2026-09-01 13:14:43 -03:00
devsyncwrld	2f836cd366	build(desktop): correct the fork's GitHub owner to syncwrld	2026-09-01 13:11:49 -03:00
devsyncwrld	f7f2cf75ab	build(desktop): point releases at the fork and rebuild the new native module ... release.yml already builds and publishes desktop installers for every platform on a v* tag, so no new workflow was needed — it needed adapting to the fork. electron-builder published to upstream's repository, so releases (and with them the electron-updater feed, which had no source at all) went nowhere useful. More consequential: postinstall ran electron-rebuild against uiohook-napi only. electron-native-screenshare would have been compiled for Node's ABI rather than Electron's and failed to load at runtime — and since the loader degrades quietly by design, the symptom would have been screen sharing with no sound and no error, which is the exact bug this module exists to fix. Documented in docs/build-desktop.md, including why the build has to run on GitHub (Gitea Actions provides no hosted runners, and the module needs MSVC) and why the Windows runner stays pinned to windows-2022.	2026-09-01 13:10:10 -03:00
devsyncwrld	3deed92dd9	feat(sounds): replace call and stream effects ... The originals were all 1.14s — long enough to be intrusive for events that fire whenever anyone joins, leaves, or watches a stream. Synthesised rather than sourced: no third-party file, so no licensing question in a public repository. The parameters are measured, not guessed — envelope, spectral peaks and decay taken from two reference sounds the instance owner supplied. The timbre is fundamental plus octave at near-equal strength (1.00 / 0.85 / 0.10 / 0.02) decaying to 1/e in 0.19s, with no reverb. Call join rises C4→G4, leave falls D4→G3, matching the references' intervals and their 100ms spacing. The stream pair reuses those resolution notes as single tones at ~55% the volume: they fire far more often during a broadcast, so they have to sit under the call sounds rather than beside them. Stream start is the one event that happens once per broadcast, so it can be a chord — with a low thump and a short air layer that both die inside 150ms, adding weight without length. Stream end mirrors it descending, quieter, and without the air, since brightness reads as arrival. Generators and the measured parameters are kept in tools/sfx so these can be retuned without redoing the analysis. Total size drops from 150KB to 41KB.	2026-09-01 13:01:06 -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	e89966435a	fix(soundboard): read MANAGE_SPACE from the space bitfield ... The add-sound control was gated on channelPermissions, which carries the per-channel bitfield; MANAGE_SPACE lives in the space-level one. The check silently evaluated false for everybody, including owners, so the button never rendered and there was no way to add a sound at all. Also raise the clip cap to 2 MB — a 30-second clip at a high bitrate cleared 1 MB — and stop reporting every upload failure as 'too large', which sent people to shrink a file that was not the problem.	2026-08-31 13:54:00 -03:00
devsyncwrld	f5451e1b14	feat: soundboard, account menu, and call timer ... Soundboard: the trigger travels over the WebSocket and every client in the call plays the clip locally, instead of mixing it into the presser's microphone or publishing a LiveKit track. No upstream bandwidth, no media stack changes, and the clip is not degraded by voice processing. Fan-out uses a new sendToRoomParticipants rather than sendToRoom: the latter broadcasts a space room to the whole space, which is right for the presence the sidebar shows and wrong for anything audible. The cooldown is enforced server-side — a client-side one only slows down people not trying to abuse it, and a soundboard is the easiest thing here to turn into a weapon. Playing is open to anyone in the call; deciding what the buttons are needs MANAGE_SPACE. Account menu: the name in the user bar had cursor-pointer and no handler, so the interface was already promising a click that did nothing. Offers profile, status and copy-id — not the Clips or account switching the reference design shows, which would be dead UI here. Call timer: startedAt comes from the server, so a late joiner sees the call's age rather than their own arrival. Empty space rooms are destroyed already, which is what makes the next call start from zero — no reset logic needed.	2026-08-31 13:45:18 -03:00
devsyncwrld	ef5545465d	docs: mark GIF favourites, audit log and statistics delivered	2026-08-31 13:30:26 -03:00
devsyncwrld	1830051732	feat(stats): voice-time and message leaderboards per space ... Voice stays get their own table rather than joining the audit log: that table records points in time, a call is an interval, and pairing join/leave point events would leave every query guessing at joins whose leave never arrived. Sessions are opened and closed inside joinRoom/leaveCurrentRoom rather than at the seven call sites that reach them, so no path can be missed, and destroyRoom closes them too — it bypasses leaveCurrentRoom and would otherwise leak open rows. A restart leaves sessions open with an unknowable end time. They are closed at startedAt, discarding that time rather than inventing it: crediting the gap would hand someone hours they never spent, and the numbers are the point. Mirrors the existing users.status sweep on boot. Only closed sessions count, so a figure does not move on every refresh. Bars scale to the leader, not the total — with five people every share of a total looks identical. Statistics are readable by any member, since they are the group's own numbers; the audit log, which names who did what, stays on MANAGE_SPACE.	2026-08-31 13:29:59 -03:00
devsyncwrld	bbb190cbda	feat(audit): append-only audit log for spaces ... Records who changed what, and is the mechanism statistics will read — one event table rather than two logs that drift apart. The table is deliberately generic (action + target + JSON metadata) so a new action needs no migration. Writes never throw: a kick must not fail because its log entry could not be written, since the kick already happened. Leaving is recorded as a different action from being removed. The same route serves both, and a log that conflates them misleads exactly when it matters. Actor is nullable with ON DELETE SET NULL: the event outlives the account, and a log that vanished with its actor would be worthless. Reads are gated on MANAGE_SPACE rather than a new permission bit, which would default to nobody until every role was re-edited. Paging uses the snowflake id, stable even for two events in the same millisecond, and an action this build does not know still renders a row.	2026-08-31 13:22:52 -03:00
devsyncwrld	fb662bfe12	feat(gif): favourites and category shortcuts ... Favourites are stored server-side per user, so one made on the phone is there on the desktop — the point of favouriting. The whole result is stored rather than an id: the provider offers no lookup by id, so an id-only favourite could not be rendered without re-finding it through search. Category chips translate their label but not their query, which goes to a provider that indexes in English. The star sits beside the tile button rather than inside it: a button within a button is invalid and swallows the click. Toggling is optimistic and reverts on failure, and favourites skip both the loading skeleton and the infinite scroll, which belong to provider-backed browsing only. Server caps favourites per user and rejects non-http(s) URLs, which become <img src> in everyone's picker.	2026-08-31 13:12:50 -03:00
devsyncwrld	0fc6abeb6e	docs: mark Spotify delivered, drop resolved items	2026-08-31 13:04:35 -03:00
devsyncwrld	75316b0882	feat(spotify): show the current track as an activity ... OAuth Authorization Code flow, with tokens kept server-side: refreshing needs the client secret, so the browser never holds a Spotify token — it asks this instance what is playing and this instance calls Spotify. The callback arrives as a plain browser redirect with no Authorization header, so the OAuth state carries the user id signed with the instance secret and is compared in constant time; without that, anyone could bind their Spotify account to another user. Activities are now tracked per producer. pushActivities replaced the whole list, so the desktop game detector and Spotify would erase each other — losing exactly the case this is for, a game and Spotify at once. Polling backs off when the tab is hidden and keeps the last known track on a network error rather than reporting 'stopped listening'. A rejected refresh token (access revoked on Spotify's side) drops the row so the UI stops claiming a live connection. Scope is read-only: user-read-currently-playing and user-read-playback-state. Per the fork's language rule, the new UI ships in en and pt-BR, and this round also translates the privacy panel.	2026-08-31 12:37:08 -03:00