3 ms·
this is only the tip of the iceberg of Teams hell. Another thing that really happens: 1. you share a $file with $person1 over chat. 2. you share that same $fil
by abakker 5y ago
this is only the tip of the iceberg of Teams hell. Another thing that really happens:
1. you share a $file with $person1 over chat.
2. you share that same $file with $person2 over chat. $person2 cannot read it. they do not have permission to access the file that is stored in the team with $person1. Over a certain file size, teams defaults to hosting _some_ files out of your one drive, but can't figure out the permissions.
Or:
1. you start chatting in a meeting. The chat persists. The meeting is cancelled. Now the chat is called $meeting_name (cancelled). All the files and chat are attached to that.
or:
1. you have a chat with $person1 and $person2
2. you are also on a team with $person1 and $person2
3. you are on a calendar invite with $person1 and $person2.
ALL of those have their own file storage directories, chats, and PERSISTENCE. But, they are not linked, and everything in them is permanent, but cannot be searched (effectively)
The fact that teams meetings have persistent file share and chat is actually mind bending. Because that feature is not just "meet with a team".
final one:
1. you can be on team with 5 people.
2. you can create infinite channels in that team, not everyone in the team is necessarily on every channel. The file structure of the channel is _not_ hierarchical from the team. sorta.
I honestly don't know what they are thinking. Instead of version control, save as, and renaming, we instead have an abysmal proliferation of shares which are at any given time being cleaned up, archived, or purged for non-use by an IT department who is doing their best. But, as users, I can spawn a new discrete file share environment for every single chat I have. Don't even contemplate what happens when you have 4 people in a chat, share a file and add a 5th person.
all the possible inversions are terrible.
Also: none of the stuff in the teams, files, folders, calendar chats, channels, or one-to-one chats end up in my Onedrive. None of this stuff can be turned off by group policy, either.
If anyone at microsoft reads this: Please, allow group policy to disable file STORAGE in arbitrary chats. share is fine, but I don't want to send a file to someone and have that stored version become the authoritative version. I want to send them a file. If i wanted a cloud version, I could put it in a team or in one drive.