That code is obfuscated and is weird for other communities/people to share. When individuals share links to the Django discord, it’s not possible to inspect that it’s actually the correct server. I think sharing a djangoproject.com link, even if it redirects, is more trustworthy.
There’s also the scenario in which something happens Discord’s end and the code were invalidated, we’d have a number of places to change. It might be worth to start that process sooner rather than later.
Links (if this is agreed upon, I apologize for doing this in a backwards way):
Definitely worth doing. However I wonder if doing a subdomain would be more in keeping with the rest the things we use as a community? (ie have chat.djangoproject.com, since we have code. and forum. already)
I think this is a good idea, and I support Andrew’s suggestion of a subdomain. The other subdomains aren’t redirects, though—does that pose more of a challenge in implementation? I’m not sure of the setup of djangoproject.com.
It’s probably good to do something like this. We can also get a custom URL rather than using an invite link but it’s not ideal as it’s reliant on people boosting the server (essentially, people paying money), and we’re roughly on the edge of having enough boosts for this at the moment, and could lose that URL.
I don’t mind much if it’s a subdomain or not or how it’s implemented.