Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Please don't post about US Politics.
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either [email protected] or [email protected].
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email [email protected]. For other questions check our partnered communities list, or use the search function.
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
You must have a nice well maintained slack instance. We just migrated to it from teams and they've added me to 50 + channels some with thousands of people and the whole program churns. It doesn't send timely notifications or sometimes none at all. If I leave any of the bogus channels I get automatically added back. Nobody wants to use it we all want teams back. The worst part is it only keeps DM history for two weeks our teams would keep history for years.
The last point is purely a configuration thing. Our Teams instance only keeps DMs for I think 30ish days -- legal wants to minimize the surface area of discoverable material. Same reason our Exchange instance nukes emails over 12 months old unless you manually move them to an archive.
Adding people back to channels is definitely an admin choice. 2 weeks history is a plan limit, I think only the free tier has it.
You can mute channels / go @s only, create new channels for whatever needs you have. Hopefully you can find a way to make it more usable within the confines of your admins config. Also note, the config may not even be intentional, so it may be worth reaching out to IT
I'm slowly starting to live with it and it's getting better the more channels I mute and group. The notification issue is still real though I've adjusted quite a few settings to get it working better. Including disabling mobile notifications and making slack use it's own notification system and not the system integrated one for Windows. The automation opportunities that exist are exciting too but will take us a while to flesh out.