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

161–170 of 364 posts

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

#161

Post by hn92726819 »

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.

It looks like non-utf8 is not allowed: https://superuser.com/questions/204287/what-characters-are-f...

Maybe it goes without saying, but for completeness, / is not allowed in filenames, and neither is null terminator (0x00 or \0) on mac either.

On Linux, only / and null terminator are banned from filenames.

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

#162

Post by nxobject »

justsomehnguy wrote: post #116
recursive wrote: post #78

Earlier quoted context omitted.

Yes. NTFS has no problem with non-latin letters and emojis in file names.

NTFS itself has not that many forbidden characters (though ':' is one of them, it denotes alternate stream). What people think about those CON, PRN, AUX, NUL etc are not filesystem limitation. And while we are here - nor backslash, nor forward slash are used in NTFS. It can care less about what char do you use for a directory separator . Just be sure to update your APIs.

NTFS on non-Windows systems aside, I wonder whether there are any "pure NT" environments you can access in Windows where you can create and use these folders.

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

#163

Post by veave »

yjftsjthsd-h wrote: post #106
reaperducer wrote: post #75

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

> AFAIK, everything else is fair game, even emojis FWIW, I generally expect emojis to be more compatible than other symbols, because they have no legacy meanings - ex. ™ has never been a path separator, or indeed anything else.

™ is not an emoji. It's part of the "Letterlike Symbols" block.

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

#164

Post by dicytea »

Ekaros wrote: post #26
mepian wrote: post #22

This is such a Microsoft thing to do. DOS compatibility will haunt us for the rest of this century at least.

Sometimes I wish we had fresh clean slate OS. Not the baggage of DOS or Unix... Something modern and sensible without insanity of either system.

By the time it's mature, you'll wish for another one. That is, if you're even alive by the time that happens.

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

#165

Post by dustingetz »

Dwedit wrote: post #147
yellow_lead wrote: post #34

Earlier quoted context omitted.

I bet there is another vulnerability here, although they also seem to blacklist % and ..

\\?\GLOBALROOT\ anyone? Now you're opening devices from the NT object namespace rather than files. Bonus: You can create the file C:\con\con using NT Native API filesystem calls. Someone even made a video of installing Windows into C:\con\con, and the kernel-side stuff works beautifully, and the explorer shell side dies horribly.

AOL chat would bluescreen a Win95 box if someone sent a chat message like “}s\con\con” - }s was the directive to play a sound

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

#167

Post by mmis1000 »

mschuster91 wrote: post #117
prepend wrote: post #105

Earlier quoted context omitted.

The key is to be terrible and simple from the beginning. IRC works just as poorly today as 30 years ago.

Which is why its usage has declined ever more and more thanks to Discord, which is a pain in itself. Freenode's collapse in particular pushed a lot of people to just say "fuck it" to IRC in general.

I think it is already killed by telegram even before discord emerges. The only thing you can't do on other IM other than IRC is having a really big chatroom that contains thousands of people. But it is no longer the case after telegram.

BTW, i think an irc bot is a good target if you are starting to learn writing a network program. The protocol is really simple(don't need complex xml parser...etc) yet requires all technique you need to write a proper client.

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

#168

Post by ikekkdcjkfke »

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…

Entreprise wishes i guess? Just look at all the group policies for windows update..

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

#169

Post by yjftsjthsd-h »

veave wrote: post #163
yjftsjthsd-h wrote: post #106

Earlier quoted context omitted.

> AFAIK, everything else is fair game, even emojis FWIW, I generally expect emojis to be more compatible than other symbols, because they have no legacy meanings - ex. ™ has never been a path separator, or indeed anything else.

™ is not an emoji. It's part of the "Letterlike Symbols" block.

Oops, good point. I think I'm going to leave it as-is on account of not knowing of any actual emoji that HN allows, but yes that is technically incorrect on my part.

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

#170

Post by kentonv »

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 prompt Blue Screen of Death for each machine.

For some reason my friends did not think it was funny.

Post reply on HN