5 ms·

they're SharePoint limits, man. Teams is backed by SharePoint and it's not a secret, nor is it embarrassing.

lostlogin 3y ago
> nor is it embarrassing Isn’t it? The folders work fine on a Mac. Teams is not a things of beauty, and is rough as all hell for daily users.
- kbenson 3y ago
  It isn't. Services have limitations, it's nothing new. This isn't about the portion of the app running on Mac, or Linux for that matter, this is because the app is backed by a service that has a name limitation and that bubbles up through teams names. In the end it's no different than if some service doesn't allow all numeric names or names to start with numerals or be too short, of which there are plenty of constraints on plenty of services.
  - lostlogin 3y ago
    I think I expect more from my tools than you. I have a fair idea why the behaviour is there, I just don’t accept that it’s ok. There are problems large and small throughout the app and it really feels like someone went ‘close enough’ and called it done.
recursive 3y ago
> nor is it embarrassing I worked on a sharepoint project once. Let's just say I'm not putting it on my resume these days.
- syndicatedjelly 3y ago
  I avoid putting stuff on my resume that I don't want to work on again. I just pretend to re-learn Sharepoint for every new job I have
  - TYPE_FASTER 3y ago
    It used to change so frequently that I didn't have to pretend.
santoshalper 3y ago
And SharePoint itself is backed by the Windows Filesystem, which respects a lot of old DOS stuff for backwards compatibility.
- nullindividual 3y ago
  This is wrong when it comes to content stored in SharePoint, of which resides in content databases or a remote blob storage, but the file names are in guid format, not the source file name, which wouldn’t work for a file of any name and SharePoint due to shredding.
- ExoticPearTree 3y ago
  It is MS SQL Server, but I guess that also has its own issues with reserved names.

> nor is it embarrassing Isn’t it? The folders work fine on a Mac. Teams is not a things of beauty, and is rough as all hell for daily users.

kbenson 3y ago
It isn't. Services have limitations, it's nothing new. This isn't about the portion of the app running on Mac, or Linux for that matter, this is because the app is backed by a service that has a name limitation and that bubbles up through teams names. In the end it's no different than if some service doesn't allow all numeric names or names to start with numerals or be too short, of which there are plenty of constraints on plenty of services.
- lostlogin 3y ago
  I think I expect more from my tools than you. I have a fair idea why the behaviour is there, I just don’t accept that it’s ok. There are problems large and small throughout the app and it really feels like someone went ‘close enough’ and called it done.

recursive 3y ago

> nor is it embarrassing I worked on a sharepoint project once. Let's just say I'm not putting it on my resume these days.

syndicatedjelly 3y ago
I avoid putting stuff on my resume that I don't want to work on again. I just pretend to re-learn Sharepoint for every new job I have
- TYPE_FASTER 3y ago
  It used to change so frequently that I didn't have to pretend.

santoshalper 3y ago

And SharePoint itself is backed by the Windows Filesystem, which respects a lot of old DOS stuff for backwards compatibility.

nullindividual 3y ago
This is wrong when it comes to content stored in SharePoint, of which resides in content databases or a remote blob storage, but the file names are in guid format, not the source file name, which wouldn’t work for a file of any name and SharePoint due to shredding.
ExoticPearTree 3y ago
It is MS SQL Server, but I guess that also has its own issues with reserved names.