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

291–300 of 364 posts

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

#291

Post by Dalewyn »

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.

Freenode collapsing had everything to do with humanity being terrible and nothing to do with IRC itself.

Given similar people, similar collapses can happen to Discord or any other communication medium of your choice.

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

#292

Post by Dalewyn »

xp84 wrote: post #211
queuebert wrote: post #44

Earlier quoted context omitted.

Brevity forces thought, which I prefer to "Putting a Sentence in a File Name.docx". FORTRAN originally had the same limitation for function names, and that lead to some classics such as GEMM and SAXPY.

When it comes to file names, I disagree that brevity serves a useful purpose. I name my files like I’m an Amazon reseller so that I’m sure to find it with Search later no matter which detail I remember. “Budget Spreadsheet (worked on with Jane) with projections with and without buying a new Tesla Model Y or Chevy Chevrolet Bolt - 2023 2024 2025.xlsx” that’s my idea of a file name.

If it floats your boat, you do you my dude.

But that being said, you're the reason why file systems are abstracted away more and more with all file system queries force fed through some kind of search engine.

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

#293

Post by mihaaly »

thefz wrote: post #33
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…

> essentially leaking the existence of something terrible inside It's just a restriction imposed on SharePoint folder names bubbling up. Nothing fancy.

Or the terribleness falls one down very fancy?

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

#294

Post by Dalewyn »

flanked-evergl wrote: post #49
yellow_lead wrote: post #6

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

The notion that change is always good/better is false, and change for the sake of change is terrible.

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

#295

Post by duxup »

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 app that does everything always seems to stink.

It's no coincidence that my favorite note taking app is ... Apple's Notes App. I've used other apps but I've found that all that heft from all the extra features makes it more of a hassle for me in the end.

I get how it happens, even my current employer / small team are looking into internal documentation routes and ... oh man the list of things people want just goes on and I fear leads to some beastly solution.

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

#296

Post by prepend »

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.

Check again in 30 more years. I’m guessing discord will have zero users and Teams will be on its 10 different product name.

But I expect IRC will still have its users.

That’s like comparing the US empire to the Roman empire. They haven’t been around long enough to talk about popularity.

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

#297

Post by prepend »

rejectfinite wrote: post #71
prepend wrote: post #25

Teams is so weird, “ Number of org-wide teams allowed in a tenant” is limited to 25. So my company can only have 25 “general” teams. I think it would be neat to learn the rationale behind some of these settings.

You want the ENTIRE company to be auto added to more than 25 teams?

I don’t want the entire company to be added to any teams. Maybe one.

But I think it’s funny that someone said “20 is not enough but 30 is too many.” And then implemented it.

Setting such an arbitrary limit so low is what is interesting to me. Fight for an opinion of “none” or “one and only one.” But allowing the hellscape of 25 teams where people accidentally invite all employees to their meeting, but not allowing 100 teams is funny.

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

#298

Post by Brian_K_White »

xp84 wrote: post #218
dharmab wrote: post #20

Earlier quoted context omitted.

The Something Terrible in this case is early DOS which did not have separate folders. So the device files were in the same namespace as the user's files, so the user couldn't name a file CON or LPT1. These are preserved for backwards compatibility. To this day you can write a program that writes to a CON file in any folder, and the program will print the write to console.

Another interesting aspect of this, which I remember specifically from reading MS-DOS manuals in the 90s as a kid (I was an incredibly fun 12 year old) is that this choice was an intentional one done in the name of flexibility. These device names were correctly written with a colon, but you are allowed to omit the colons. For instance: copy con lpt1 And copy con: lpt1: were interchangeable. If they’d chosen to not sa…

One of my favorite bbs sig tags was "REAL programmers use COPY CON FILE.EXE"

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

#299

Post by AndrewKemendo »

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…

Classic! My favorite “anyone can do it hack” was ping flooding people during a lan-party

Good old memories

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

#300

Post by nullindividual »

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.

SharePoint stores files as binaries in a SQL database (or a reference to an Azure Blob Store). The filesystem doesn’t come into play.
Post reply on HN