Jitsi command line app : Meet

Meet creates a meeting with a secure ID and prints the meeting URL to stdout . It can style, open, copy, and send the URL for your convenience.

Usage:

$ meet
https://meet.jit.si/A8ul9DAc/Meeting
$ meet -c hack on meet
https://meet.jit.si/iN9SYLvP/HackOnMeet
🚀 copied to clipboard!

Created by myself and Yana Chen because we start so many Jitsi meetings every day!
License is GPLv3, please share :slight_smile:

5 Likes

Interesting tool, thanks for sharing.

Why the two-level name, tough ( with a “/” separator ) ?

The two-level name is for uniqueness: Jitsi uses the first level as part of the room ID, but only the second level for the meeting name shown to participants. For example, you & I can both have a meeting named “Mother’s Day” at the same time without conflict as long as we each use a different first level.

meet makes this easy by automatically generating a secure random first level and composing it with the meeting name you provide.

1 Like

Is this a documented feature or you just came across it by chance ? Very interesting, thank you!

I haven’t been able to find much documentation for Jitsi, and from my web searches and forum searches I can tell that a lot of other people can’d find it either, which is sad. I’ve been learning mostly from trying things and observing results, like I would with a proprietary service. I’ve tried reading the source code but it hasn’t been organized enough to teach me much yet.

1 Like

@damencho @saghul could you confirm or clarify if this is an intended / documented feature ?

1 Like

Yep, it is. We call the middle part the “tenant”. Imagine it as a way to segment companies with a single deployment, for example.

Note, however, that not all deployments may support it. meet.jit.si does and will.

2 Likes

@saghul thanks! I want to add support for meet to use other Jitsi installations. Is there a way I can automatically discover whether a given installation supports the tenant component?

1 Like

I’d be interested in contributing, nice work Ryan!

1 Like

Thank you @tigerhiddenadam, you are definitely welcome to contribute! Feel free to open an issue or use this thread to coordinate.

1 Like

This bypasses authentication.

What do you mean?

Do a HEAD request to try and fetch config.js and if you succeed it means it will work.

2 Likes

Sorry, I’ll elaborate.

On a Jitsi Meet server with Secure domain setup, a password is required when starting a meeting using URLs like https://meet.domain.com/meeting but anyone can start a meeting with URLs using the “tenant” in it, ie https://meet.domain.com/tenant/meeting.

I noticed this on a test server recently setup.

It would be helpful if someone else can reproduce this and perhaps file a security issue report if I don’t get to it first.

confirmed.

It can be avoided by zapping the sub-domain redirection in nginx config.

Thanks again! Do you know if that info is documented somewhere official that I can link to in meet’s docs?

Does anybody know of a Jitsi server which does not support the “tenant” feature which I can test against? Or are there instructions on how to run one with that feature disabled?

meet.saghul.net doesn’t support it. Or any deployment using the Docker setup, for that matter.