@Falco Is it possible to expose a public check in the site settings/serializer for whether LiveKit is configured, alongside voice_enabled? Today voice_enabled is client-exposed, but there’s no public signal for whether a site can serve LiveKit. The only LiveKit-related site attribute, voice_livekit_per_room_available, is scoped to the room-form checkbox, so it returns false under the all_rooms policy and can’t be used to answer “does this site do LiveKit at all”. RoomSerializer#expected_transport covers the per-room case nicely, but that requires fetching rooms first, and it comes back empty when voice_public_access is off, even on a site where LiveKit is fully configured. Would something like this be acceptable? It’s derived from existing state, exposes no credentials or policy detail, and needs no new endpoint. It would go in plugins/voice/plugin.rb, after the voice_livekit_per_room_available block and just before the Voice::DefaultRoomSeeder.ensure! line: # Public, credential-free signal that the site can serve LiveKit at all. add_to_serializer(:site, :voice_livekit_available) do Voice::Livekit.configured? && SiteSetting.voice_livekit_room_policy != "disabled" end

[imagen] nicolsdennis: RoomSerializer#expected_transport covers the per-room case nicely, but that requires fetching rooms first Actually you were right on the spot there. The official API is exactly doing a call to and parsing it like this curl https://meta.discourse.org/voice/rooms.json -s | jq '.rooms[] | {name: .name, transport: .expected_transport}' Which will give you the peer room transport. [imagen] nicolsdennis: it comes back empty when voice_public_access is off voice_public_access is not an existing setting. What are you talking about? Of course, you want to use auth on the API call to rooms.json to be able to fetch rooms only the current user have access to.

voice_enabled isn’t reachable from the JSON API at all: /site.json carries no site_settings key. So the only public signal that voice is running on a site is the presence of voice_assets_path. What I’m asking for is two public, credential-free booleans so a client can decide whether to surface voice before fetching any rooms. Both are derived from existing state and need no new endpoint, in plugins/voice/plugin.rb: At line 141, above voice_public_access: #Public, credential-free signals for API clients that voice is enabled. add_to_serializer(:site, :voice_available) { SiteSetting.voice_enabled } At line 152, above voice_livekit_per_room_available: # Whether joins can use LiveKit at all. A bare yes/no: no URL, key or # policy value. The per-room attribute below only gates the room form's # SFU checkbox, and reads false under the all_rooms policy. add_to_serializer(:site, :voice_livekit_available) do Voice::Livekit.configured? && SiteSetting.voice_livekit_room_policy != "disabled" end This exposes nothing new: expected_transport is an ungated attribute on RoomSerializer (line 30, defined at 150) and rooms#index skips login (rooms_controller.rb:18), so “livekit” / “mesh” is already anonymously readable per room. This just answers it without a room fetch that may come back empty.

Please don’t mention team members in-bulk like that (I edited the mentions out). It may help if you describe what your end goal is for this extra information. It’s hard to answer a feature-request without any justification for what you’ll be using the information for.

Apologies I asked a question on an announcement and I was split to support, which left me unaware of who to speak to since this is a feature request than troubleshooting, after reviewing for past 5hrs I tagged the members from the core commit/merge of voice. However to add some context. I have an application that acts as a multi-client for Discourse communities, each configured differently, so at boot it builds the navigation for whichever site the user is on. Chat appears if chat is enabled, and I’d like voice to appear if voice is enabled and actually joinable from the app. The app joins over LiveKit and can’t do mesh, so on a mesh site I want to leave voice out of the navigation entirely rather than show rooms that will fail to connect and make it look like the app is broken. So the flow is: read site info once at boot, decide whether voice belongs in the app for that site, then use expected_transport per room once the user opens it. The two booleans are just the first step, and without them I’m either showing a feature that can’t work or hiding one that can. Alternatively I can place “Not Available on this Forum” in a global alert within the application regardless of being enabled but this seemed like the better approach so I’ve pinpointed the entry point and gave the code and comments.

[imagen] nicolsdennis: The app joins over LiveKit and can’t do mesh, so on a mesh site I want to leave voice out of the navigation entirely rather than show rooms that will fail to connect and make it look like the app is broken. Thanks for the explanation! The request makes sense. The voice plugin is new and in an experimental state. It will likely go through changes in the next few weeks and months. Especially internal changes. We are open to exposing this information in some fashion, but can’t be sure yet what that form will be. It depends on how the LiveKit integration evolves.

[imagen] nicolsdennis: after reviewing for past 5hrs I tagged the members from the core commit/merge of voice. If you think 5h is too much to wait, you may be new to the concept of async comms in forums. Welcome! [imagen] nicolsdennis: RoomSerializer#expected_transport covers the per-room case nicely, but that requires fetching rooms first, and it comes back empty when voice_public_access is off, even on a site where LiveKit is fully configured. I will investigate this and come up with something we can use.

[imagen] Falco: If you think 5h is too much to wait, you may be new to the concept of async comms in forums. Welcome! nicolsdennis: I think you misunderstood, I was up from 1am to 5am reviewing what was done and the merges that’s how i found the team members i originally tagged. Not that i’m waiting on a reply for 5hrs. The app already submitted for review and it’s utilizing the default system I already have. [imagen] pmusaraj: The voice plugin is new and in an experimental state. It will likely go through changes in the next few weeks and months. Especially internal changes. We are open to exposing this information in some fashion, but can’t be sure yet what that form will be. It depends on how the LiveKit integration evolves. That’s fine by me, take as much time as needed. I’ve done my testing over a period of 6 months, took some fine tuning for scaling.

I was looking at plugin.rb line 144, where it’s added to the site serializer, backed by Guardian#voice_public_access? in lib/voice/guardian_extension.rb line 16. I read it as a setting when it isn’t one, so that’s my error. And thanks for the rooms.json pointer, the authenticated call with expected_transport is what I was missing. All I’m after is whether the site can serve LiveKit at all, in the site payload. Can room transport can tell me that: available_for? returns room.livekit_enabled under per_room (lib/voice/livekit.rb line 26), and expected_transport returns the pin first (room_serializer.rb line 150), including after a mesh fallback (rooms_controller.rb line 169).

@Falco I’ll test further on my local instance. A separate question Is voice_allowed_groups exposed to clients anywhere, and is expected_transport the intended way to tell LiveKit from mesh per room in a list? I’d want to hide mesh rooms and show only LiveKit ones where available, I don’t see how to separate them.

[imagen] nicolsdennis: A separate question Is voice_allowed_groups exposed to clients anywhere No. Exposing that would be borderline information disclosure. Only the current user needs to know about his own permissions. [imagen] nicolsdennis: is expected_transport the intended way to tell LiveKit from mesh per room in a list? Yes, 100%. [imagen] nicolsdennis: I’d want to hide mesh rooms and show only LiveKit ones where available, I don’t see how to separate them. Use expected_transport.

Okay, thanks much for the assitance.

Exposición del estado de LiveKit en el serializador de la configuración del sitio

Soporte del producto

nicolsdennis (Nicols Dennis) 4 Septiembre, 2026 13:25 13

Esto es lo que he hecho: A Social Mobile & Desktop Client for Communities (2) - #30 by nicolsdennis

Tema		Respuestas	Vistas
Live: Discord-style voice and video rooms, now bundled with Discourse :studio_microphone: Announcements live	82	4306	4 Noviembre 2026
Integrating Discourse Voice with LiveKit Integrations live	0	186	3 Septiembre 2026
Resenha - Add Discord-style Video and Voice Rooms and Calls to Your Community :studio_microphone: Plugin	83	7665	10 Octubre 2026
Developing Discourse Plugins - Part 3 - Add custom site settings Developer Guides plugin-guides , tutorial	39	25062	15 Marzo 2025
A plugin for chat to connect to a video conferencing tool Feature chat , completed	2	727	3 Septiembre 2026

Exposición del estado de LiveKit en el serializador de la configuración del sitio

Temas relacionados