Edit history

Today, every time you launch Fluxer Desktop, you must manually navigate to your server and join the voice channel. There is no option to automatically connect to a designated community voice channel when the application starts. This would be a very usefull feature for power users who regularly spend time in voice channels, and will prevent requiring repetitive manual action each session.

Add an auto-join voice channel feature with two configuration modes: Mode 1 — Navigate & Join An option where Fluxer automatically navigates to the selected community on startup and joins its configured voice channel. This gives a fully hands-free experience: launch Fluxer and you're already connected and in the server, similar to how "Start in" behaviors work in other apps. Scope: only one community can be set as the startup auto-join target. This keeps startup behavior deterministic — Fluxer connects to exactly one server/channel at launch, matching how comparable clients (e.g. TeamSpeak 3's startup bookmark) handle it. Mode 2 — Default Channel on Visit A lighter option where Fluxer does not navigate anywhere automatically on startup. Instead, the user can set a default voice channel per community, for multiple communities, which is joined automatically whenever the user manually navigates to that community. This keeps startup behavior unchanged while removing the extra clicks of opening the channel list and picking a channel. Scope: default channels can be configured on unlimited communities — each community simply remembers your preferred channel and drops you into it when you visit. Both modes include optional settings for joining muted/deafened. In summary: configure default channels on as many communities as you like (Mode 2), but designate only one of them as the single startup destination (Mode 1). This mirrors the TeamSpeak 3 bookmark model, where every bookmark can store a channel but only one bookmark can auto-connect at launch.

A good precedent for this feature exists in TeamSpeak 3, which implements exactly these two behaviors through its bookmark system: TeamSpeak 3 lets users save each server as a bookmark, and each bookmark can be individually configured with:

• Default voice channel — each bookmark stores which voice channel to join when connecting to that server. Multiple bookmarks can each have their own default channel configured.
• Auto-join on startup — however, only one bookmark can be enabled for automatic connection at TeamSpeak launch. When that single bookmark triggers, it also joins the default channel stored in that bookmark.

In practice this means a TeamSpeak user can maintain multiple community bookmarks, each with their own saved channel preference (matching Mode 2). Only one of those bookmarks can be marked for startup auto-connect (matching Mode 1). Applying this pattern to Fluxer would map cleanly to the two modes:

• Mode 1 = select one community/bookmark to connect on startup + join its default channel
• Mode 2 = configure default channels for multiple communities, joined automatically when manually visiting each

This approach balances flexibility (multiple saved channels) with practical constraints (only one startup destination). Since TeamSpeak has validated this workflow over many years with its user base, it demonstrates both feasibility and user value.