Live data from Hacker News

MS Teams channels cannot contain MS-DOS device names

learn.microsoft.com

141–150 of 364 posts

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

#141
post #45

Earlier quoted context omitted.

tale it is https://www.snopes.com/fact-check/railroad-gauge-chariots/

Snopes is not a good reference to cite, they have changed many artlcles based on research they missed. They tend to just want to get a page up when a topic is popular, then research it later.

I mean, correcting factual errors is pretty good trait for a fact-checking site, right?

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

#142

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.

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 that needs to pass through there, and generally makes it a nicer place to be.

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

#143

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…

they're SharePoint limits, man. Teams is backed by SharePoint and it's not a secret, nor is it embarrassing.

And SharePoint itself is backed by the Windows Filesystem, which respects a lot of old DOS stuff for backwards compatibility.

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

#144
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…

Wait, the MS Teams desktop app is deprecated? Never got any message about that ... Guess I might soon be forced to use double the evil, in Chrome and Teams in Chrome? Wow, the world becomes more dystopian by the day. Perhaps I should quit my job when I am forced to use Chrome. Well gonna use the desktop app for as long as I can. They will probably never fix their broken shit app, so that one can use it from any browser.

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

#145

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.

Although, at least what works today works tomorrow on IRC. Same cannot be claimed from MS Teams or Discord ...

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

#146
post #21

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

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.

[deleted]

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

#147

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.

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.

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

#148
post #60

Earlier quoted context omitted.

The Romans did not use war chariots, since they are basically useless in combat. They only used chariots for sports in the hippodrome.

Chariots are not “useless in combat”, but they are very expensive to field and only work in pretty narrow circumstances: wide, open, and relatively solid areas (aka not bogs). These circumstances were not a thing for Roman legions until they reached spain at least, possibly North Africa and the Middle East. As a result they were not part of Roman war doctrines. On the other hand they were very much part of bronze-age…

Spain is mountainous as hell; a chariout outside the Castille plains and Madrid would be scrap.

Get a height map of Spain and you can obviously see that a chariot trying to ride at Picos de Europa would be a nightmare.

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

#149
post #2

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

In the mid-90s there was a fun and short period of time where IRC clients like mIRC could be set to auto-receive files through DCC.. and would happily write to names like LPT1 (which of course would just write the data directly to the recipient’s printer)

Also, send a COM1 file containing "+++ATH" to someone you dislike to see them disconnect. I just made this up but it should work, right?

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

#150
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…

I think part of it is the constant drive to add features – sure, we can do chat and video! But, what if we put background blurring in there? Crap, Zoom has polls, we'll have to add polls now... well, shoot, if we're cranking out features like this and iterating quickly, we might as well use Electron.
Post reply on HN