5 ms·
At my previous job, I decided to make a Slack channel named after one of the C preprocessor directives (#define I think, or maybe #endif). A handful of people f
by TazeTSchnitzel 3y ago
At my previous job, I decided to make a Slack channel named after one of the C preprocessor directives (#define I think, or maybe #endif). A handful of people found it and appreciated the joke.
But then, a few months later, one of the admins contacted me to ask if it would be okay to delete the channel. You see, in large organisations, Slack knows which channels are not meant to be visible to other parts of the org, and it was causing mentions of the C preprocessor directive to be censored for people outside my group ^^;
- OJFord 3y agoThat'll teach 'em to put it in a code block!
- JuanPosadas 3y agoOne of my biggest pet peeves is people dumping whitespace-sensitive plain text without any kind of code blocks, rendering it completely unreadable.
- onionisafruit 3y agoFunny that slack’s attempt to keep it from being mentioned revealed the existence of a private channel.
- TazeTSchnitzel 3y agoSlack's search actually had a bug where it would return results with matches inside hidden channel names, highlighting the censored section :)
- kubanczyk 3y agoI don't think it works for private channels. Since, as OP says, non-members occasionally could find the channel, it was probably a public channel. The people who complained were probably "multi-channel guests". They'd see masked-out channel names except where they are explicitly allowed.
- TazeTSchnitzel 3y agoAh, no, they wouldn't have been guests. The organisation was large enough that it had multiple “workspaces” corresponding to different divisions. Channels always belong to a workspace, but some are shared between workspaces. You can only see the channels belonging to or shared with your workspace.