Some of those limits look unreal to me. Do they really limit you to 200 people in a private channel?
MS Teams channels cannot contain MS-DOS device names
281–290 of 364 posts
Re: MS Teams channels cannot contain MS-DOS device names
#282Earlier quoted context omitted.
Now I actually wonder were there ever any machines that had LPT9, COM9 I could barely see.
MSDOS 3.3 had COM1, COM2, COM3, COM4, LPT1, LPT2, and LPT3. LPT4-9 and COM5-9 was not part of MSDOS.
IIRC those were mapped to specific I/O and IRQ Ports back in the day.
COM1: I/O port 0x3F8, IRQ 4
COM2: I/O port 0x2F8, IRQ 3
COM3: I/O port 0x3E8, IRQ 4
COM4: I/O port 0x2E8, IRQ 3
Re: MS Teams channels cannot contain MS-DOS device names
#283Earlier quoted context omitted.
Is the Windows version ever exposed as a string in the Windows API? Seems strange in my mind, but I have no experience with Windows. On the one hand it sounds like something Microsoft would do for backwards compatibility, but on the other hand it seems like a weird API to provide. I found GetVersion[1] but that returns the version as two numbers. [1] https://learn.microsoft.com/en-us/windows/win32/api/sysinfoa...
I don't know if the rumor is true, but even if Windows itself doesn't provide an API that looks like that (I also looked around real quick and didn't find anything), it's not unreasonable that there could be libraries that provide the version that way.
The rumour is not true, despite reddit's insistence. Windows exposes it's version is a series of numbers, and even if it didn't, Windows 9 could have returned "Windows Nine", "Window v9" or loads of other things.
Re: MS Teams channels cannot contain MS-DOS device names
#284I can't be the only one thinking that generally MS Team is offering probably worst experience in the messaging market.
It's absolute fucking garbage when it comes to text chat. It boggles my mind that they had so many examples on how to do it right and fucked it up so badly
I honestly think they should fire every single PM on that team. Like literally just keep the engineers and give them no more direction than make it better and designers need to approve any UI changes.
That's it.
Re: MS Teams channels cannot contain MS-DOS device names
#285Earlier quoted context omitted.
They're also good at getting security clearances since they never do anything, so those might've been CIA agents.
>They're also good at getting security clearances since they never do anything I never understood why you should mass deny security clearances to people who like to "party".
They don't want people who might have done something embarrassing in their past, because foreign adversaries might try to blackmail them with that.
Re: MS Teams channels cannot contain MS-DOS device names
#286Reminds me of the rumor that the reason it went "Windows 7", "8", "10" and skipped "9" is because the fear of a codebase that went: if(version.StartsWith(“Windows 9”)) { /* 95 and 98 */ ... }
Is the Windows version ever exposed as a string in the Windows API? Seems strange in my mind, but I have no experience with Windows. On the one hand it sounds like something Microsoft would do for backwards compatibility, but on the other hand it seems like a weird API to provide. I found GetVersion[1] but that returns the version as two numbers. [1] https://learn.microsoft.com/en-us/windows/win32/api/sysinfoa...
You're imagining that all developers do things properly. I've seen Bash code that used a regex to get the first two digits from `python --version`. Hopefully they'll never release a Python 3.10!
Re: MS Teams channels cannot contain MS-DOS device names
#287This 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.
Microsoft, when confronted with a problem, think "I know, I'll build it on top of SharePoint."
Every time, it seemed like it was going to be so easy and powerful. Each time, it turned out to be impossible to implement relatively vanilla functionality.
Re: MS Teams channels cannot contain MS-DOS device names
#288Earlier quoted context omitted.
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!
Ah, good times. Lim yo han!! (Aka slayers boxers ? Right ?). As a Terran player, I was in such awe. And then came Flash (lee young ho), the GOAT. I watched every one of his games. StarCraft 2 never came close to the accidental perfection that SC1 is.
Re: MS Teams channels cannot contain MS-DOS device names
#289Pretty soon we’ll need historians to explain this to younger generations.
Maybe alongside the school of computer science at universities we’ll have a school of computer archeology and a school of computer ethics where we’ll be taught not to use negative reinforcement for AI training…
Re: MS Teams channels cannot contain MS-DOS device names
#290Earlier quoted context omitted.
most of those are the usual forbidden path and filename characters. % is used to surround environment variables for interpretation, for example.
> 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.
Once I planned to share files between a Mac and a Win PC through a product synching folders but gave up very soon due to the constant errors and problems with file names worked in one but not in the other, dominantly filenames that I did not choose but received (e.g. link dragged from address bar to folder, but others too) but some I choose following some preexisting logic.