Earlier quoted context omitted.
Now I actually wonder were there ever any machines that had LPT9, COM9 I could barely see.
You can reassign real device to any of these names
Reassign and actually use all of them are different things.
MS Teams channels cannot contain MS-DOS device names
91–100 of 364 posts
Re: MS Teams channels cannot contain MS-DOS device names
#92Earlier quoted context omitted.
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…
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 uploa…
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.
Re: MS Teams channels cannot contain MS-DOS device names
#93Earlier quoted context omitted.
> essentially leaking the existence of something terrible inside It's just a restriction imposed on SharePoint folder names bubbling up. Nothing fancy.
Those should obviously be UUIDs. Labels and titles should be a simple changeable, internationalizable attribute. Like usernames. You don’t use usernames as primary keys for anything, do you? What happens when people marry?
> You don’t use usernames as primary keys for anything, do you?
Sure you do. Saves doing joins all over the place just to get someone's username. Makes hand writing SQL easier.
Apply head to desk.
Re: MS Teams channels cannot contain MS-DOS device names
#94I 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…
> leaking the existence of something terrible inside
If you should get the opportunity to look at a raw (DNS) NXDOMAIN passive DNS (PDNS) feed there's a lot of plain brokenness, but the nuggets can be truly alarming. This is what happens when translating between naming services: naming services typically have application domains, and names in one context are interpreted differently in another. Bobby Tables is well known, but how about that special file "-rf"? Was a time when the happy path for Active Directory essentially trusted DNS domain names implicitly for things like file shares. Sounds ok until you realize executable files might be on those "drives".
(Honestly I don't find the string "MS-DOS" anywhere in that document.) (Edit: Did find the reference to e.g. CON, LPT1...)
Re: MS Teams channels cannot contain MS-DOS device names
#95Words: forms, CON, CONIN$, CONOUT$, PRN, AUX, NUL, COM1 to COM9, LPT1 to LPT9, desktop.ini, _vti_
Now I actually wonder were there ever any machines that had LPT9, COM9 I could barely see.
MSDOS 3.3 had COM1, COM2, COM3, COM4, LPT1, LPT2, and LPT3. LPT4-9 and COM5-9 was not part of MSDOS.
Re: MS Teams channels cannot contain MS-DOS device names
#96Earlier quoted context omitted.
One man's tech debt is another man's API stability
One man's API stability is another man's perpetual nightmare, especially if the API is bad. Things have to change to get better, and if systems are designed in a way which prevents API improvements, then you will just have perma-crap software.
> perma-crap software
Yeah, we are talking about Microsoft here.
I guess some people will pop-up from nowhere and disagree with your rationale, but it is flawless. Everybody loves the stability anyway.
Re: MS Teams channels cannot contain MS-DOS device names
#97Re: MS Teams channels cannot contain MS-DOS device names
#98I sort of get most of these - they're internal to various bits of Microsoft technology. 'CON' plus the ones ending in $ are internal device names dating back to MS-DOS, 'desktop.ini' is a magic file that Explorer uses, '_vti_' is something I've seen but can't remember what it was from. But 'forms'? Why is 'forms' a bad word?
I did some quick looking and it seems like SharePoint creates a hidden folder called “forms” to store, unsurprisingly, forms associated with a resource. Aren’t polluted namespaces grand?
Re: MS Teams channels cannot contain MS-DOS device names
#99Earlier quoted context omitted.
It’s only forbidden for Windows users. I think the only character that Macs don't allow is the colon. AFAIK, everything else is fair game, even emojis. I just created a project with "ê" in the title. I wonder if I'll be able to share that with my Windows coworkers on Teams.
Yes. NTFS has no problem with non-latin letters and emojis in file names.
I had to test it, but this is true. I just renamed my TODO.txt to [sobbing emoji].txt
Re: MS Teams channels cannot contain MS-DOS device names
#100Earlier quoted context omitted.
they're SharePoint limits, man. Teams is backed by SharePoint and it's not a secret, nor is it embarrassing.
> 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.
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