Because data in the Slack channels is expected to be kept private, and the Slack channel IDs may or may not be considered private (I don't know), this is a significant concern.
I believe the develop_new branch which uses matrix-puppet-server and matrix-puppet-bridge develop doesn't have this problem, but the new architecture is still in-the-works, and until it becomes stable this will remain an issue.
(Even if the problem's cause and solution is in matrix-puppet-bridge, the library, the problem affects the application and should be reported here (too))
Because data in the Slack channels is expected to be kept private, and the Slack channel IDs may or may not be considered private (I don't know), this is a significant concern.
I believe the develop_new branch which uses matrix-puppet-server and matrix-puppet-bridge develop doesn't have this problem, but the new architecture is still in-the-works, and until it becomes stable this will remain an issue.
(Even if the problem's cause and solution is in matrix-puppet-bridge, the library, the problem affects the application and should be reported here (too))