Static-invite links to direct new users to existing servers #2143

New issue

Open

opened 2026-02-20 22:00:19 -05:00 by deekerman · 5 comments

deekerman commented

2026-02-20 22:00:19 -05:00

Owner

Originally created by @tobiasarndt on GitHub (Mar 9, 2021).

Context
Make it easier for new users to join existing servers, by adding the possibility to issue static invite-links.

Describe the feature you have in mind
If the user has an existing mumble installation, request to open mumble at the specified server from the browser, else ask the user to install mumble and supply download links.

Originally created by @tobiasarndt on GitHub (Mar 9, 2021). **Context** Make it easier for new users to join existing servers, by adding the possibility to issue static invite-links. **Describe the feature you have in mind** If the user has an existing mumble installation, request to open mumble at the specified server from the browser, else ask the user to install mumble and supply download links.

deekerman added the

client

feature-request

release-management

labels

2026-02-20 22:00:19 -05:00

deekerman commented

2026-02-20 22:00:22 -05:00

Author

Owner

@Krzmbrzl commented on GitHub (Mar 9, 2021):

You can already use links to join a Mumble server.
Prompting for Mumble to be installed when clicking on a Link is probably not possible though 🤔

@Krzmbrzl commented on GitHub (Mar 9, 2021): You can already use links to join a Mumble server. Prompting for Mumble to be installed when clicking on a Link is probably not possible though :thinking:

deekerman commented

2026-02-20 22:00:22 -05:00

Author

Owner

@Kissaki commented on GitHub (Mar 10, 2021):

I think that’s an interesting and reasonable suggestion. More of a service infrastructure / website feature though.

For example: We would host something on https://invite.mumble.info/<mumble-url> and trigger opening the mumble url with javascript, and if unsuccessful / no protocol handler registered we display some HTML information and download link / link to download page.

I think this is viable and useful.

And if the url is a parameter we do not have to implement any backend infrastructure.

We may want to not auto-open the mumble link though, and display a warning that it will 1. open Mumble, and 2. is not trusted or verified by us. Whether or not we base64 encode the url would be another question. I think seeing it open could increase trust(worthyness).

The client could then have a copy-url action in the Server menu with this invite link.

@Kissaki commented on GitHub (Mar 10, 2021): I think that’s an interesting and reasonable suggestion. More of a service infrastructure / website feature though. For example: We would host something on `https://invite.mumble.info/<mumble-url>` and trigger opening the mumble url with javascript, and if unsuccessful / no protocol handler registered we display some HTML information and download link / link to download page. I think this is viable and useful. And if the url is a parameter we do not have to implement any backend infrastructure. We may want to not auto-open the mumble link though, and display a warning that it will 1. open Mumble, and 2. is not trusted or verified by us. Whether or not we base64 encode the url would be another question. I think seeing it open could increase trust(worthyness). The client could then have a copy-url action in the Server menu with this invite link.

deekerman commented

2026-02-20 22:00:22 -05:00

Author

Owner

@Krzmbrzl commented on GitHub (Mar 10, 2021):

Ah okay yes that would be an option. I was thinking of a purely client-side process.

@Krzmbrzl commented on GitHub (Mar 10, 2021): Ah okay yes that would be an option. I was thinking of a purely client-side process.

deekerman commented

2026-02-20 22:00:22 -05:00

Author

Owner

@Krzmbrzl commented on GitHub (Mar 10, 2021):