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

341–350 of 364 posts

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

#341

Post by nullindividual »

toyg wrote: post #324
nullindividual wrote: post #300

Earlier quoted context omitted.

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

But it now has a feature to integrate seamlessly with OneDrive, linking or replicating a folder on the user machine. Hence, I expect it has the same limitations in terms of naming.

OneDrive for Business (not consumer!) is SharePoint. It has the same restrictions as SharePoint (nb: because they're separate Web Applications, Microsoft can enable/disable features independently between "OneDrive" and SharePoint).

Yes, OneDrive client is restricted by the Win32 API in terms of allowable file names/path length (which is now 32k but Office doesn't respect MAX_PATH and implements its own ~250 path length limitation).

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

#342

Post by nomel »

justsomehnguy wrote: post #122
ChrisSD wrote: post #76

Earlier quoted context omitted.

On Unix perhaps. Windows forced IT folks to deal with the issue by having folders like "Program Files". Even the user's folder used to be in "Documents and Settings" (but they backed down from that eventually and now it's just "Users").

> but they backed down from that eventually Only because they were started to hit MAX_PATH there: C:\Users\Johnathan Aparecido da Silva\AppData\Local\ASUS\ASUS System Control Interface\AsusSoftwareManager C:\Documents and Settings\Johnathan Aparecido da Silva\AppData\Local\ASUS\ASUS System Control Interface\AsusSoftwareManager

The `subst` command provides an easy way around that. Link the last folder somewhere closer to the root, to make longe-than-255 paths accessible. Then, when you're done, remove the link and your files are protected from pesky things like virus/malware scanners.

I used it to hide my old virus/malware collection, made from what my computer was infected with through the years.

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

#343

Post by nomel »

queuebert wrote: post #308
xp84 wrote: post #211

Earlier quoted context omitted.

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.

Modern OSes can search within files for text, which mostly obviates using the filename for keywords.

They can also search images for subjects, location, etc.

Still, it would have been nice if a standard metadata format could be included with each file, in a way that survives file transfers.

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

#344

Post by astrange »

boffinAudio wrote: post #328
astrange wrote: post #274

Earlier 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 good at being CIA agents because they are supple and compliant and the CIA has tools to make that compliance into nationalistic zealotry that rivals the capabilities of most religions, having refined it through operations such as paperclip, etc..

They were already nationalistic, that's another part of being Mormons.

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

#345

Post by astrange »

stouset wrote: post #322
TazeTSchnitzel wrote: post #285

Earlier quoted context omitted.

They don't want people who might have done something embarrassing in their past, because foreign adversaries might try to blackmail them with that.

On the flip side, those are the exact people who often wouldn’t be embarrassed or ashamed of that kind of behavior. I’ve done a lot of things, and I’d openly admit just about all of it if anyone asked. On the other hand if you do find a Mormon who took some liberties in an earlier time in their life…

As well as admitting everything, it's easier to get a government job if you never did drugs, seeing as they're illegal.

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

#346

Post by nullindividual »

wizofaus wrote: post #310
nullindividual wrote: post #302

Earlier quoted context omitted.

;# is the Choice column separator value. That restriction makes sense in that context.

But it doesn't restrict you! You can create a choice field with a value that contains ;# and select it, but then it can't display correctly. Relatively minor bug as bugs go, but still...

Just tried in SPO (modern UI) without issues.

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

#347

Post by rexreed »

kentonv wrote: post #338
rexreed wrote: post #280

Earlier quoted context omitted.

Great site - I am reading all your posts about the LAN party house now. Do you have the real estate listing of the house when it was up for sale? I'm just curious as to where it was located - you mentioned a sliver of land, and I saw the asking price ($2M in Palo Alto) so I'm curious to see what it looked like from the outside and its location, if you don't mind sharing!

Hmmmm even though it's not mine anymore, posting the address doesn't feel right... seems like it'd be violating the privacy of the new owners of the house. Yes, even though I did post the address publicly when selling it -- that listing is gone now so arguably privacy has been regained. (Or if not, maybe you can find it, heh.) Sorry about that. There are a few more pictures of the house on the architect's (my father'…

Thanks! Your father's site and his work is amazing, including your house! And yes, I did end up finding the address and listing through a basic search, but your Dad's site actually has more and better pictures ;)

When you build your new Austin LAN-party-pad would love to see that.

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

#348

Post by wizofaus »

nullindividual wrote: post #346
wizofaus wrote: post #310

Earlier quoted context omitted.

But it doesn't restrict you! You can create a choice field with a value that contains ;# and select it, but then it can't display correctly. Relatively minor bug as bugs go, but still...

Just tried in SPO (modern UI) without issues.

Might only be an issue for multichoice fields.

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

#349

Post by telotortium »

kentonv wrote: post #338
rexreed wrote: post #280

Earlier quoted context omitted.

Great site - I am reading all your posts about the LAN party house now. Do you have the real estate listing of the house when it was up for sale? I'm just curious as to where it was located - you mentioned a sliver of land, and I saw the asking price ($2M in Palo Alto) so I'm curious to see what it looked like from the outside and its location, if you don't mind sharing!

Hmmmm even though it's not mine anymore, posting the address doesn't feel right... seems like it'd be violating the privacy of the new owners of the house. Yes, even though I did post the address publicly when selling it -- that listing is gone now so arguably privacy has been regained. (Or if not, maybe you can find it, heh.) Sorry about that. There are a few more pictures of the house on the architect's (my father'…

@kentonv, if you see this, it looks like your father's website is potentially broken on mobile. See https://photos.app.goo.gl/3tcui1CXypZC3PfE9 - the photo is a tiny thumbnail on the right hand side. If I switch to desktop mode, it's bigger, but still pretty small. Probably due to the left sidebar being a fixed size and always on the left. I'm using a Pixel 2, but with the latest Android and Chrome version.

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

#350

Post by kentonv »

telotortium wrote: post #349
kentonv wrote: post #338

Earlier quoted context omitted.

Hmmmm even though it's not mine anymore, posting the address doesn't feel right... seems like it'd be violating the privacy of the new owners of the house. Yes, even though I did post the address publicly when selling it -- that listing is gone now so arguably privacy has been regained. (Or if not, maybe you can find it, heh.) Sorry about that. There are a few more pictures of the house on the architect's (my father'…

@kentonv, if you see this, it looks like your father's website is potentially broken on mobile. See https://photos.app.goo.gl/3tcui1CXypZC3PfE9 - the photo is a tiny thumbnail on the right hand side. If I switch to desktop mode, it's bigger, but still pretty small. Probably due to the left sidebar being a fixed size and always on the left. I'm using a Pixel 2, but with the latest Android and Chrome version.

Yeah, I know. He's not a computer person, but somehow he managed to set up this web site without any help from me, which is kind of a miracle. Obviously the tech isn't great though. He doesn't actually need it to get clients or anything, he's retired, so whatever.

Maybe I'll help him put together a better site after the new house is done and ready to go on it...

Post reply on HN