> A vanity address is only human-meaningful up to a certain point in the string. Not really memorizable.
This is also the reason why they're discouraged from a security perspective.
You burn a given amount of CPU time to get CyberdyneSystemsZfzah3uf, then someone else burns the same amount of CPU time to get CyberdyneSystemsZy6jhaef, then humans don't notice that they're not the same thing even though you're relying on that for security.
What matters in practice is mostly by whether people memorize it. People choose to memorize Pi and the list of dictionary headwords (to play Scrabble, you don't need to speak or even read the language, just know all the valid words)
Once upon a time people would memorize telephone numbers of friends and people they call often, not so much now.
During the pandemic my gaming group uses Google Meet, some things use Zoom, we began having Friday evenings in Jitsi and we moved them to Gather Town.
Zoom is the only one that is resolutely impractical to memorize, every Zoom meeting gets a random huge ID and password, so you need to pass around lengthy nonsense URLs for each meeting and even then you might also need to share the password. This is done in the name of "security" although it isn't actually more secure than...
Jitsi takes arbitrary long strings to distinguish one conference from another, defaulting to generating word salad. So you tell everybody you're in "CloudsEffortlesslyChaseMushrooms" and joining creates it. If you want to name one "SecretHackerNewsRoom" you can, but I think somebody might guess that name.
Google Meet uses shorter, random IDs. You can't mint your own, and by contrast to word salad they're tricky to remember, but you can re-use them, and after a while your mind remembers ZWC-KLWL-CBMB or whatever because it's the same every week. Also your browser will auto-complete it, if you have that turned on.
Gather Town allows you to build and name custom places. Since you're customising them anyway, you get to name them. If you call it "RedLionPub" I'm guessing you might get uninvited guests. If you instead reference an inside joke ("TerramicDragonHouseOFish" or "InstantMonkeyDispatch") not so much. However there is an ID number baked into the URLs, and I don't know if there's search, so you'll likely end up memorizing or bookmarking URLs for a place you go often.
Passwording a Jitsi room in the way you would a Zoom meeting seems pointless, just give it a harder to guess name and save trying to memorize two separate facts when only one is needed.
Jitsi's end-to-end encryption passwords would be a reasonable choice (if your clients are capable) and you would need to memorize those separately from a room name since Jitsi's servers don't do anything with the encryption
(If you join a Jitsi call with say, four other participants using a password you don't know, your copies of their four audio and video streams are nonsense, chances are your decoders will give you silence and a black rectangle, although weird glitched blocky nonsense video is also possible and I guess it's conceivable you'd likewise get weird audio nonsense)
Having a public part (room id) and private part (password) fits very well into people's mental model of security/accessibility.
Doing it this way also lets you turn off authentication if you decide you don't need it and lets you use the same password if you need multiple conference rooms. This is the best solution in my opinion.
> If you join a Jitsi call with say, four other participants using a password you don't know, your copies of their four audio and video streams are nonsense
Not in my experience. Jitsi won't let me enter the room at all if I enter an invalid password.
I thought that's why you burned some CPU hunting for 'vanity' addresses[1]?
[1]: https://opensource.com/article/19/8/how-create-vanity-tor-on...