Ad-hoc guest access for voice channels

Sometimes I want to invite people to a voice channel for a short, spontaneous session without asking them to create a permanent Fluxer account first. A common example would be an online game: I'm playing with a few people who do not use Fluxer, and I would like to invite them to a voice channel just for the current match or gaming session. At the moment, they would need to go through the normal registration flow and provide an email address, even though they may only want to use the voice channel for an hour or two. For this kind of temporary access, creating a permanent account feels unnecessary and adds enough friction that people may simply not want to join. There is already a temporary-account / guest-access concept described in fluxer-meta #3 as part of Events / Calendar. However, the use case described there appears to be tied to a scheduled event. For spontaneous voice sessions, having to create a calendar event first would add unnecessary overhead. The guest access itself would be useful independently of Events.

I would like to be able to create a temporary guest invite directly from a voice channel. For example: Right-click voice channel → Create guest invite The invite could have options such as:

• Expiration time (for example 1 hour, 3 hours, 24 hours, or custom)
• Maximum number of uses
• Optional invite password

A guest opening the link should not have to create a normal Fluxer account or provide an email address or account password. Ideally, the flow would be as simple as: Open invite → choose display name → join voice channel The guest should only have access to the voice channel they were invited to, rather than becoming a normal member of the entire community or instance. The temporary guest session/identity should expire automatically. Once it has expired, the temporary guest account itself should also be permanently cleaned up rather than remaining indefinitely as a disabled or unused account. If a guest decides that they want to stay on Fluxer, there could optionally be a way to convert the guest into a normal account by providing an email address and password. Permanent accounts would therefore continue to use the normal registration/account model.

Related roadmap item: https://github.com/fluxerapp/fluxer-meta/issues/3 That issue already describes temporary accounts / guest access in the context of Events / Calendar, including allowing someone without an existing Fluxer account to join a linked voice channel temporarily. This proposal is not intended to replace or duplicate the event-based flow. The distinction is that this use case is ad-hoc and independent of the calendar: Event-based guest access: Create event → link voice channel → invite guests for the event Ad-hoc guest access: Open voice channel → create temporary guest invite → share link The underlying temporary guest mechanism may of course be shared between both features. I asked about this distinction in the Fluxer development server, and Hampus suggested opening a separate Ideas discussion describing the use case, which could be merged with the existing work later if appropriate. Some examples where ad-hoc guest access could be useful:

• Online gaming sessions
• LAN parties
• Quick calls with people who do not use Fluxer
• Workshops or small events
• Temporary project groups
• Support or troubleshooting calls
• Short-lived community voice sessions

The main goal is to make joining a temporary voice session nearly frictionless without turning every guest into a permanent account on the Fluxer instance.