39 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
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
devsyncwrld	c022f2795f	docs: record the i18n foundation and translation queue	2026-08-31 12:25:03 -03:00
devsyncwrld	688a1335cb	feat(i18n): language foundation with en and pt-BR ... Nothing in the project was translatable — every string sat inline in English. en.ts is the source dictionary and its type is derived from it, so a typo or a missing key fails typecheck instead of rendering the raw key at runtime. pt-BR.ts is deliberately Partial: translation proceeds one system per update and anything absent falls back to English, so a half-migrated interface is never broken, only partly English. Locale is persisted, guessed from the browser on first run, and kept in sync with <html lang> through a subscription — persisted state rehydrates after first paint, so a one-off assignment would miss it. Translates the voice input panel (including the mic test shipped earlier today) and the profile card as this round's system. Language options are labelled in the active language, so a wrong pick can always be undone.	2026-08-31 12:24:50 -03:00
devsyncwrld	89e13441c8	docs: record the pt-BR language rule and new system ideas	2026-08-31 12:18:33 -03:00
devsyncwrld	63afd2fc89	fix(profile): hoist the activity hook above the early return ... The activity selector sat below `if (!isOpen || !user) return null`. `user` arrives asynchronously, so the hook ran on some renders and not others; React counts hooks per render and tore the tree down with error #310 as soon as a profile finished loading. Move it above the guard and let the selector tolerate a null user. Typecheck and the suite both passed with the bug in place — TypeScript cannot see hook order and nothing renders this modal across the null-to-loaded transition.	2026-08-31 12:12:23 -03:00
devsyncwrld	d80de49768	chore(caddy): serve the Gitea site alongside the app ... The git server runs as its own stack in /opt/gitea and is reached by container name over the app's internal network, publishing no host port of its own. Only the reverse-proxy entry belongs here, where the Caddyfile lives.	2026-08-31 12:07:29 -03:00
devsyncwrld	b92a0d837e	docs: update roadmap after mic test and activity work	2026-08-31 12:05:18 -03:00
devsyncwrld	d7da0ff203	feat(activity): show the current activity on the profile card ... The activity pipeline was already complete end to end — Activity type, store, WS broadcast, server validation, presence relay, and an ActivityCard used by four list surfaces — but the profile card rendered none of it, which is the 'Listening to Spotify' block the design calls for. Add ProfileActivity: richer than ActivityCard because the card has room for artwork, track and artist, so it reads details/state/assets. All optional, so it degrades to the bare name that today's process-based detector supplies. Also scheme-check activity image assets server-side. activity.url was already restricted to http(s) but assets.largeImage/smallImage were only length-checked — an asymmetry that was harmless while nothing rendered them, and is not once they become <img src>: a client could point them at a host it controls and harvest the IP of everyone opening that profile.	2026-08-31 12:05:01 -03:00
devsyncwrld	bfe62d7078	feat(voice): mic test with loopback in voice settings ... The level meter only measured a stream a call had already opened, so settings offered no way to check a mic before joining — the panel said as much. Add startMicTest/stopMicTest on AudioManager: the processed input bus is routed to the master output through a dedicated gain node, so the loopback can be disconnected precisely. Settings had deliberately never opened the mic itself; a mic test cannot honour that, so the test hands the mic back when it stops. Releasing needs two independent guards, because the user may join a call mid-test: AudioManager only stops the exact stream it opened (identity check, not a flag), and the caller must consent — the UI reads the call state, which AudioManager cannot, as it does not import stores. Unmounting mid-test tears the loopback down too.	2026-08-31 11:59:51 -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
devsyncwrld	20526e1bc8	feat(gif): outlined GIF glyph, and GIF picker for the profile banner ... The composer's GIF button drew a filled rounded rect with the letters knocked out, which reads as a solid square rather than a picker. Invert it: stroked outline with filled letters, reusing the original glyph paths scaled to centre. Banners already accept absolute URLs on both ends (server isValidAssetUrl allows http(s); the profile render branches on banner.startsWith('http')), so the picker stores the remote URL directly with no upload path. Previews can now hold either a blob: or an https: URL, so revoking is guarded — calling revokeObjectURL on a remote URL is a silent no-op that would hide a mistake.	2026-08-31 11:44:40 -03:00
devsyncwrld	c70b0095a9	feat(voice): jump to the call from the voice panel ... The channel name under 'Voice Connected' was a plain div. Making it navigate needed more than an onClick: voiceStore never recorded which space the call was in, and spaceStore.channels only holds the space currently being viewed — so after navigating away the call's channel was unresolvable, which is also why the label degraded to a generic 'Voice Channel'. Capture space and channel name at join time (the only moment they are reliable) and use them for both the label and the jump. Covers space calls and DM calls.	2026-08-31 11:40:45 -03:00
devsyncwrld	08db5374cb	build: compile better-sqlite3 from source (no Node 20 prebuilt) ... better-sqlite3@12.11.1 ships prebuilt binaries for ABI 127/137/141/147 only; Node 20 is ABI 115, so prebuild-install falls back to node-gyp, which fails on node:20-slim for lack of python3/make/g++. Add the toolchain to the builder stage, and in the runtime stage install, use and purge it inside a single layer so the final image ships no compiler.	2026-08-31 11:09:14 -03:00