Re:Updated Okta Statement on Lapsus$
by Spooky23 on Tuesday March 22, 2022 @04:18PM
(#30770963)
Channel sprawl is very normal. While my day job has a broad scope in the org, I’m a “member” of over 900 MS Teams. I’d guess that 3% are active and i interact with 0.
[ Parent
| on HN ]
Re:Updated Okta Statement on Lapsus$
by sleepybrett on Tuesday March 22, 2022 @05:49PM
(#30772016)
At a previous job a new slack channel was spun up for every incident, no matter how minor by automation. So yeah a few thousand doesn't sound that weird to me.
Re:Updated Okta Statement on Lapsus$
by tialaramex on Tuesday March 22, 2022 @05:48PM
(#30772005)
900 teams? That's a lot, are you sure you don't mean 900 channels (or whatever Teams calls them) instead?
Re:Updated Okta Statement on Lapsus$
by zwayhowder on Tuesday March 22, 2022 @07:50PM
(#30773119)
A lot of people want to have full control so rather than create a channel called "Project Phoenix" in a team called "Operations" they'll create a whole new team, and use the general channel.
Much like the OP here I'm in hundreds of teams, and almost all of them do all their talking in #general and they wonder why people never respond to notifications.
The Teams UX and general paradigm is awful. Right now I'm in 3 group chats and two channels (in two Teams) discussing the Okta incident. Huge overlap of them, but not 100% so some people aren't getting all the information.
I forgot to mention that the teams interface is truly awful. I do what I should be doing in a “Team” in one of a half dozen pinned group adhoc chats.
The context switch between a mostly useless teams tab and a needlessly full screen IM window is too heavy for me.