31–40 of 364 posts
This backwards compatibility chain reminds me of the age old tale of how rockets are the width of two horses... (1) (1) http://astrodigital.org/space/stshorse.html
Also, you might be interested in this: https://youtu.be/1NqRbBvujHY?t=2236
I was about to say "Which is essentially leaking the existence of something terrible inside. They should be embarrassed to say something like this in public. Like saying you can't have %s or $PS1. Why the hell not? What are you doing with this user-supplied input?" But maybe it's more about what everyone else might do with a channel name. Ie they might cut & paste it anywhere, and I guess windows users aren't expecte…
It's just a restriction imposed on SharePoint folder names bubbling up. Nothing fancy.
This is most likely due to those names not being allowed for files or folders in the Windows file system. MS Teams channels create a matching folder in SharePoint where file attachments are stored.
Ahahaha, I love this! I love how this new fandango thing harkens back to the earliest days of MS-DOS when it ran on a 086 or 286, back in the early (very early) 90s. Have to respect MS' backwards compatibility fanaticism. Impossibly as if a native port of MS Teams would be created for MS-DOS 3.1 (hahahaha). When more plausibly the MS Teams servers run on an ancient crazy proprietary MS-DOS 3.1 mainframe (still implau…
earliest days of MS-DOS when it ran on a 086 or 286, back in the early (very early) 90s. About a decade off: MS-DOS was running on 8086 in the early 80s.
Ahahaha, I love this! I love how this new fandango thing harkens back to the earliest days of MS-DOS when it ran on a 086 or 286, back in the early (very early) 90s. Have to respect MS' backwards compatibility fanaticism. Impossibly as if a native port of MS Teams would be created for MS-DOS 3.1 (hahahaha). When more plausibly the MS Teams servers run on an ancient crazy proprietary MS-DOS 3.1 mainframe (still implau…
Agree BC is a laundable goal and appreciate their efforts. Though I do wish it didn't include limiting passwords to obscenely short lengths or absurd subsets of characters.
Why is it that most "chat/conference" apps become horrible sooner or later? I still remember when teams used to be an OK app. It even had a Linux desktop client. I remember when slack was actually fast, I remember Skype out being more reliable to make phone calls than my mobile/cell service. Today slack is extremely slow if you add few organisations to it (but at least you can add more than one). Teams has deprecated…
Teams is so weird, “ Number of org-wide teams allowed in a tenant” is limited to 25. So my company can only have 25 “general” teams. I think it would be neat to learn the rationale behind some of these settings.
If you are participating in 25 teams, it's likely already too many, general or not.
Having to navigate 25 teams that are full of stuff doesn't concern you sounds like an absolute nightmare.
You'd burn out everyone in the organization with a setup like this.
I was about to say "Which is essentially leaking the existence of something terrible inside. They should be embarrassed to say something like this in public. Like saying you can't have %s or $PS1. Why the hell not? What are you doing with this user-supplied input?" But maybe it's more about what everyone else might do with a channel name. Ie they might cut & paste it anywhere, and I guess windows users aren't expecte…
> essentially leaking the existence of something terrible inside It's just a restriction imposed on SharePoint folder names bubbling up. Nothing fancy.