Mattermost-server: Hardcoded town-square channel

[jolks]

Across Go and React code, town-square channel is hardcoded. Maybe we can make it configuration-based so teams can easily change it and the platform can redirect correctly to /channel/<new name>.

However doing this, we also have to change the mobile app code e.g. mattermost/android code.

[Darren66]

Second that.

[lfbrock]

Hi @jolks + @Darren66,

Right now it's not possible to change the URL for town square to make redirects easier, since there are various times we need to redirect people back to town square.

I created a ticket here in the backlog to fix it, if you want to you can also add a feature suggestion so other people can upvote it if it's important to them.

[jolks]

Thanks for your feedback @lfbrock. I posted to the feature suggestion at here.

[lfbrock]

Thanks!

[megapctr]

Sorry to dig this up, do you think it would make sense to add a concept of a _default_ or a _main channel_? That way we avoid hardcoding a channel id, while still having a safe place to redirect to. The user could make some other channel the default one, and then be able to delete town square

[lfbrock]

@megapctr - is there a reason you would want to have a default channel instead of just being able to change the URL for town square?

Also feel free to sign up for our daily builds server and come join our UX Design channel if you'd like to discuss it more in depth.

[megapctr]

I guess that the channel url is some sort of an id. Changing an id not a good idea, as other things may depend on them (db table relations for example). Because of that, a "default channel" flag would make more sense architecture-wise.