Using domain aliases in channel descriptions

[doublevcodes]

Amendment type

Content Update

Content type

Other

Please provide the location of the content

Multiple channel descriptions

What amendment do you think should be made to this content, and why?

Background

So, in multiple channel descriptions there are links to content on external pages such as the links to https://github.com/python-discord/meta/issues/new and https://www.pythondiscord.com/pages/guides/pydis-guides/off-topic-etiquette in the #community-meta and #ot.* channels respectively.

Proposal

My proposal is that you try to shorten these URLs wherever possible so that there’s more chance that the channel description fits on smaller screen sizes. Obviously, it still won’t fit on every screen size, but it might make it fit on more. To clarify, this means making references to pythondiscord.com, becoming pydis.com, and github.com/python-discord can become git.pydis.com.

[DMFriends]

I don't see why this is a problem, @doublevcodes. Users can always click on the channel description to expand it so the entire thing can be seen, like the screenshot below.

What we could do is add [Click to expand] to the beginning of each channel description. I think that's a better idea.

[bsoyka]

I think shortening the URLs where possible is a good idea, and there's not really a reason not to.

Plus, adding text like that to the start of every single channel description seems like it would just take up more space overall, pushing away potentially important details for those who won't actually click it.

[DMFriends]

Plus, adding text like that to the start of every single channel description seems like it would just take up more space overall, pushing away potentially important details for those who won't actually click it.

Hmm, ok. I see what you're saying. What I don't get is - if we do add that text to every single channel description and bold it, I wouldn't imagine someone not clicking it though, but it depends on the person.

I still sort of disagree about there being no reason not to shorten URLs. If we use a link shortener like bit.ly if you're familiar with that, some people may not know what that link is and decide it's unsafe to click it. For instance, in "The Coding Den" Discord server, they outright ban posting links obfuscated by link shorteners altogether.

So I still think we shouldn't shorten URLs in channel descriptions.

This is only my opinion on the matter, though.

[bsoyka]

The suggestion here isn't to use public link shorteners such as Bitly, though. These are domains we already run that are visibly our brand. This about sums it up:

To clarify, this means making references to pythondiscord.com, becoming pydis.com, and github.com/python-discord can become git.pydis.com.

Plus, the reasoning behind this suggestion is not to make the links any better to click on, but to allow a bit more information to show in the preview given before clicking.

[DMFriends]

The suggestion here isn't to use public link shorteners such as Bitly, though. These are domains we already run that are visibly our brand. This about sums it up:

To clarify, this means making references to pythondiscord.com, becoming pydis.com, and github.com/python-discord can become git.pydis.com.

Plus, the reasoning behind this suggestion is not to make the links any better to click on but to allow a bit more information to show in the preview given before clicking.

Ohhhkay, that changes things a bit. I guess I need to read the posts more carefully next time 😀

So if that's the case, I think that might work fairly well. I mean, this is something that can always be reverted if it doesn't go right, so I actually think it's worth a try now that I think about it.

[lemonsaurus]

I see no reason not to do this. Handling it now:

URLs shortened on:

• [x] Off-topic channels
• [x] dev-contrib
• [x] community-meta
• [x] dev-branding

I think that should be all the public-facing channels, if I forgot some, just poke me on #community-meta.