Live data from Hacker News

MS Teams channels cannot contain MS-DOS device names

learn.microsoft.com

191–200 of 364 posts

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

#191

Earlier quoted context omitted.

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

IRC is so trivial that hosting your own is easy. Telegram is awesome but it's still centralized.

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

#192

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 has its claws in msft and it will forever be their achilles heel.

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

#193

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…

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

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

#194

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!

It's still being played heavily and professionally in Korea and there are many non Korean tournaments too.

I watch pro matches everyday!

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

#195
post #33

Earlier quoted context omitted.

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

i was going to write a bunch of suggestions for solving the problem but then i remembered i hate microsoft

Name checks out.

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

#196

Earlier quoted context omitted.

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.

You just need to come in below whatever layer notices them. I'm sure they've been used to smuggle viruses in, so the layer that blocks them may get lower and lower.

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

#197
post #181

Earlier quoted context omitted.

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.

I think the confusion comes from the fact that some platforms render it as a drawing as if it was an emoji. I never understood why...

Speaking only for myself, the confusion comes purely from the fact that I think of all text as "ASCII" or "Unicode" (...or "something else that nobody should use in the modern era"), and I don't really distinguish within "valid unicode that isn't ascii".

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

#198

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’d bet RedHat 5.2.

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

#199

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've come across an apocryphal tale in the U.S. west describing why certain towns and cities have main streets that are the width required to fully turn a wagon pulled by x number of horses. Likewise, in the Canadian House Of Parliament, the width between the Prime Minister's desk and that of the Leader Of The Opposition is said to be that of two swords raised, tip to tip, based on the British House Of Commons tradit…

Even today size of streets in many cities is determined by the space needed to either turn a fire truck or have two fire trucks pass.

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

#200
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 great but imagine if we can send/share money too.

Your chat app is great but imagine if we can send/share conference meetings too.

Your chat app is great but imagine if we can send/share calendar invites too.

Your chat app is great but imagine if we can send/share food delivery requests too.

Your chat app is great but imagine if we can send/share gaming sessions too.

Your chat app is great but imagine if we can send/share X too.

There is no limit on X. The internet is about sharing X. a chat app is about sharing X. There is no bound to how much it can grow really.

Post reply on HN