3 ms·

Does this imply it's writing a file to the fs for its internal storage, with the name matching the channel's name instead of a channel ID?

by lol768 3y ago

Brian_K_White 3y ago
I think it only implies they worry about people cutting and pasting channel names into other things like random powershell scripts.
icegreentea2 3y ago
Not necessarily - it could mean that at some point they believe they'll need to create folder or file with the same name as a team, and they don't wanna have to deal with weird collisions. It's been a while since I've used Teams+Sharepoint, but I vaguely remember being able to have a Sharepoint workspace per team channel, and then being able to mount those workspaces as a shared/network drive. Stuff that might end up in the workspace is like... shared/uploaded files or something?
- i_am_jl 3y ago
  It's been a while since I've used Teams+Sharepoint, but I vaguely remember being able to have a Sharepoint workspace per team channel, and then being able to mount those workspaces as a shared/network drive. Stuff that might end up in the workspace is like... shared/uploaded files or something? This is correct. Every channel is backed by a Sharepoint folder (maybe this is configurable?) that contains stuff like uploaded images, videos, recordings and transcripts of meetings, etc.
  - Roark66 3y ago
    It's hilarious on Linux you need chrome to use teams for screen sharing / video to work, and Firefox for sharepoint file sharing to properly work. If someone shares a file on a channel, you can open it in chrome. But you can't share any files yourself, because either the upload button doesn't work or when it does it looks like you shared the file in the chat for a split second then it dissapears.
- ant6n 3y ago
  This%20is%20what%20escape%20sequences%20are%20for.
  - kevincox 3y ago
    If these folders are user-visible (for example browsable in SharePoint) then this leads to a bad user experience. The downside of restricting channel names needs to be weighed against the downside of needing to escape the SharePoint folder names.
markstos 3y ago
Yes. Or something equally head-scratching.
randomdata 3y ago
Could be someone taking DRY a bit too seriously, using validation code that is shared with places where the names do matter.

Does this imply it's writing a file to the fs for its internal storage, with the name matching the channel's name instead of a channel ID?

by lol768 3y ago

Does this imply it's writing a file to the fs for its internal storage, with the name matching the channel's name instead of a channel ID?

Brian_K_White 3y ago

I think it only implies they worry about people cutting and pasting channel names into other things like random powershell scripts.

icegreentea2 3y ago

Not necessarily - it could mean that at some point they believe they'll need to create folder or file with the same name as a team, and they don't wanna have to deal with weird collisions. It's been a while since I've used Teams+Sharepoint, but I vaguely remember being able to have a Sharepoint workspace per team channel, and then being able to mount those workspaces as a shared/network drive. Stuff that might end up in the workspace is like... shared/uploaded files or something?

i_am_jl 3y ago
It's been a while since I've used Teams+Sharepoint, but I vaguely remember being able to have a Sharepoint workspace per team channel, and then being able to mount those workspaces as a shared/network drive. Stuff that might end up in the workspace is like... shared/uploaded files or something? This is correct. Every channel is backed by a Sharepoint folder (maybe this is configurable?) that contains stuff like uploaded images, videos, recordings and transcripts of meetings, etc.
- Roark66 3y ago
  It's hilarious on Linux you need chrome to use teams for screen sharing / video to work, and Firefox for sharepoint file sharing to properly work. If someone shares a file on a channel, you can open it in chrome. But you can't share any files yourself, because either the upload button doesn't work or when it does it looks like you shared the file in the chat for a split second then it dissapears.
ant6n 3y ago
This%20is%20what%20escape%20sequences%20are%20for.
- kevincox 3y ago
  If these folders are user-visible (for example browsable in SharePoint) then this leads to a bad user experience. The downside of restricting channel names needs to be weighed against the downside of needing to escape the SharePoint folder names.

markstos 3y ago

Yes. Or something equally head-scratching.

randomdata 3y ago

Could be someone taking DRY a bit too seriously, using validation code that is shared with places where the names do matter.