Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

MS Teams channels cannot contain MS-DOS device names

learn.microsoft.com

Post reply on HN
Print view View original

201–210 of 364 posts

Re: MS Teams channels cannot contain MS-DOS device names

#201

Post by bombcar »

extraduder_ire wrote: post #142
michaelmrose wrote: post #121

Earlier quoted context omitted.

Thanks for the anecdote that was interesting. I think the Erie gauge war demonstrates that people feel entitled to any advantage of circumstances that they have profited from in the past as if such were their property even when the actual matter are issue is in fact others property.

I've seen this happen with planned bypasses of small towns, either through individuals fighting CPOs for their land, or people in the town opposing planning permission notices. (there's a few I can think of where the council's current plan involves waiting for certain people to die, since that's less effort overall) Usually such bypasses are great for these towns, as it removes most of the articulated road shipping t…

It depends on the town, it can also kill or relocate it. The town in Pixar's Cars is realistically depicted in that way.

Re: MS Teams channels cannot contain MS-DOS device names

#202

Post by kentonv »

saalweachter wrote: post #193
EspressoGPT wrote: post #186

Earlier quoted context omitted.

> Circa 1998 I was a teenage Linux zealot who would attend LAN parties carrying a Linux box. Arch, I suppose.

Arch wasn't around in 1998. I'm going to put my money on Slackware.

I think it was RedHat.

I had tried Debian first but switched to RedHat pretty quickly afterwards.

(Back then, RedHat had nothing to do with "enterprise", it was just the most polished Linux distro around. Ubuntu didn't exist yet.)

(These days FWIW I use boring old Debian, and I'm not a zealot about it. It works for me. Use what works for you, I don't care. I have a separate machine for gaming and it runs Windows. I know Steam works pretty well on Linux these days but Windows is still less hassle for games.)

Re: MS Teams channels cannot contain MS-DOS device names

#203

Post by duskwuff »

reaperducer wrote: post #75
lostlogin wrote: post #57

Earlier quoted context omitted.

> the usual forbidden path and filename characters. It’s pretty irritating when files and folders on my Mac can’t be uploaded to Teams due to this limitation. It’s only forbidden for Windows users.

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.

> I think the only character that Macs don't allow is the colon.

Colon is allowed in the filesystem; it's displayed as a forward slash in the UI.

(There's historical reasons they do this: Classic Mac OS used colon as a path separator.)

Re: MS Teams channels cannot contain MS-DOS device names

#205

Post by h2odragon »

eddythompson80 wrote: post #200
Roark66 wrote: post #24

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…

Because believe it or not, a chat/conference is the most easy gateway to an "everything app" just like with WeChat. Afterall, a chat/conference app is a microcosm of the "internet". Your chat app is great but imagine if we can send/share audio clips too. Your chat app is great but imagine if we can send/share video clips too. Your chat app is great but imagine if we can send/share live video too. Your chat app is gre…

"every program expands until it can read email... make that netnews..."

Re: MS Teams channels cannot contain MS-DOS device names

#206

Post by cogman10 »

code_runner wrote: post #188
kentonv wrote: post #170

Circa 1998 I was a teenage Linux zealot who would attend LAN parties carrying a Linux box. It actually worked -- at the time, WINE practically existed to support Starcraft, Quake 2 could run natively, and that covered like 95% of what people were playing. One time I thought it would be funny to run a shell script that looped through every Windows share on the network and tried to open `CON/CON` on it, resulting in a…

love this story very much. I had no idea WINE had been around for that long and was able to play starcraft etc. I have really great memories of playing starcraft with friends back in the day.... that game had enough staying power that we could all get into and out of in middle school and then again in college!

Wine is nearly as old as linux. First released in 1993.

I had some awkward conversations with my parents as a teenage nerd looking into "winehq". They didn't believe me that it had nothing to do with alcohol.

Re: MS Teams channels cannot contain MS-DOS device names

#207

Post by godzillabrennus »

kentonv wrote: post #202
saalweachter wrote: post #193

Earlier quoted context omitted.

Arch wasn't around in 1998. I'm going to put my money on Slackware.

I think it was RedHat. I had tried Debian first but switched to RedHat pretty quickly afterwards. (Back then, RedHat had nothing to do with "enterprise", it was just the most polished Linux distro around. Ubuntu didn't exist yet.) (These days FWIW I use boring old Debian, and I'm not a zealot about it. It works for me. Use what works for you, I don't care. I have a separate machine for gaming and it runs Windows. I k…

Back when Redhat was the name of the enterprise releases and the open source releases.

Re: MS Teams channels cannot contain MS-DOS device names

#208

Post by xp84 »

ChrisSD wrote: post #76
glonq wrote: post #70

Earlier quoted context omitted.

Whenever I create a filename that is long or has spaces, I still pause and worry "okay, what might break if I do this", even though such concerns probably died a couple decades ago. Actually scripts breaking if files or paths have a space in them seems to be a thorn in the side of dev/ops/it folks that never goes away, does it?

On Unix perhaps. Windows forced IT folks to deal with the issue by having folders like "Program Files". Even the user's folder used to be in "Documents and Settings" (but they backed down from that eventually and now it's just "Users").

This was actually genius, though it was/is so annoying typing these verbose paths

Re: MS Teams channels cannot contain MS-DOS device names

#209

Post by lostlogin »

kbenson wrote: post #113
lostlogin wrote: post #63

Earlier quoted context omitted.

> 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.

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 constrai…

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.

Re: MS Teams channels cannot contain MS-DOS device names

#210

Post by andix »

conscion wrote: post #10

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.

And matching Active Directory groups. It's kind of cool to use them, because it's a really easy way to let the users administrate access to resources without opening a support ticket.
Post reply on HN