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

111–120 of 364 posts

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

#111

Post by elnezah »

jmount wrote: post #104
failuser wrote: post #58

Earlier quoted context omitted.

This is a classic joke, but settling on a common gauge was really difficult, it was not just copying some old Roman standard. There were even riots when different railways started to standardize because common rail gauge meant you can move through the town without engaging with the local economy, see Erie gauge war. Russia still has a wider gauge than Europe and Australia has 3 different ones.

I rode a train in Spain where the train changed gauge at a station!

Spain has a peculiar train gauge. When you cross the border with France, the train slows down and gauge change happens on the fly.

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

#112

Post by cueo »

Brian_K_White wrote: post #8
owlninja wrote: post #2

Words: forms, CON, CONIN$, CONOUT$, PRN, AUX, NUL, COM1 to COM9, LPT1 to LPT9, desktop.ini, _vti_

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…

> I was about to say

Yet you said it twice[1].

[1] https://news.ycombinator.com/item?id=37076913

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

#113

Post by kbenson »

lostlogin wrote: post #63
naikrovek wrote: post #54

Earlier 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 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 constraints on plenty of services.

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

#114

Post by Sakos »

bradley13 wrote: post #87

So many of these limits seem arbitrary. Why 5? Why 500000? While they seem OK for most customers, why not make many of them MAXINT?

That sounds crazy to me and I understand why Microsoft or any company wouldn't want to do that. It seems completely reasonable to me to set reasonable limits to avoid excessive resource usage or unforeseen/untested/unwanted performance limitations.

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

#115

Post by [deleted] »

m3047 wrote: post #94
Brian_K_White wrote: post #17

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…

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

[deleted]

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

#116

Post by justsomehnguy »

recursive wrote: post #78
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.

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.

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

#117

Post by mschuster91 »

prepend wrote: post #105
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…

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.

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

#118

Post by paulddraper »

Brian_K_White wrote: post #17

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…

AWS has character restrictions on virtually everything.

The message bodies of SQS messages has restrictions on which whitespace characters can be used.

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

#119

Post by m3047 »

m3047 wrote: post #94
Brian_K_White wrote: post #17

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…

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

Looking at the list of characters and character ranges the omission of 7F is curious.

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

#120

Post by SamuelAdams »

paulddraper wrote: post #118
Brian_K_White wrote: post #17

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…

AWS has character restrictions on virtually everything. The message bodies of SQS messages has restrictions on which whitespace characters can be used.

I noticed this recently too. We set up alerts on cloud watch logs and I tried to put an emoji in the alert message, which delivers to an SNS topic, which goes to an email. And cloudformation complained loudly that there was an unsupported character in the alarm message.
Post reply on HN