I'm 'using punctuation in a filename feels wrong' years old.

[frauxirah@chaos.social]

@alicemcalicepants @piiabartos Less keen on that one, but willing to compromise.

[catselbow@fosstodon.org]

@alicemcalicepants @frauxirah @piiabartos

Windows still has a limit of 256 characters for a file's path (directory+name). You can create files that exceed that, but then they're inaccessible until you shorten the path.

I regularly see this in our accounting office, where they make folders with names like "Professor Joe Schmoe, August 2020 - grant numer 123456789 - provisional DO NOT USE THIS ONE version 7", nested several layers deep.

[glueckstein@digitalcourage.social]

@alicemcalicepants I am "the 8.3 filename structure" old.

[randamumaki@mstdn.social]

@alicemcalicepants I'm 'filenames are 8.3 alphanumerical characters' years old.

[frauxirah@chaos.social]

@catselbow @alicemcalicepants @piiabartos I come fresh from a horrible migration project with that exact issue. And then people complain the files wouldn't sychronise anymore. #SendHelp

[dianebruce@bsd.network]

@alicemcalicepants That reminds me of the time BNR up here connected their unix machine to their macs and ended up with '/' in the actual filenames.

[grumpyoldtechie@hostux.social]

@alicemcalicepants filenames? If you load your whole system from punch cards or that new-fangled paper tape you don't need no steenking filenames

[fighen@mastodon.bida.im]

@alicemcalicepants @oblomov It is Still wrong

[grumpyoldtechie@hostux.social]

@DianeBruce @alicemcalicepants More than 26 years ago? BTW if you really want to mess with people on Unix like systems put newlines in the filenames.

[brokar@mastodon.social]

@alicemcalicepants I'm 'why are files identified by their suffixes and not by their content' years old.

[technicaladept@techhub.social]

@alicemcalicepants no point in using those fancy pants FAT16 filenames if your batch files are just going to need to guess how they'll be presented to DOS. Bad enough that it's moved all my files to C:\docume~1\

[doboprobodyne@mathstodon.xyz]

@RandamuMaki @alicemcalicepants
I think we have the basis of an age verification system we can all get behind, here.

#fileSystems #ageVarification #socialMedia

[cascheranno@hachyderm.io]

@alicemcalicepants I’m ‘wtf are these spaces’ yrs old.

[cascheranno@hachyderm.io]

@alicemcalicepants I’m also, jokes aside, old enough to miss how vms automatically kept old versions of files.

[ariarhythmic@ohai.social]

@catselbow @alicemcalicepants @frauxirah @piiabartos isn't there a registry key to remove that limit?

Just 256 for the whole path sounds very restrictive

[azteclady@kind.social]

@alicemcalicepants yes.

oh lord, yes.

[cauzation@mastodon.social]

@alicemcalicepants Why do I feel like I should underscore this?..

[alxndr@tech.lgbt]

@alicemcalicepants Still wary of spaces, TBH.

[independentpen@mas.to]

@alicemcalicepants unless it's underscore. Also no spaces; you camel that text

[ajn142@infosec.exchange]

@ariarhythmic @catselbow @alicemcalicepants @frauxirah @piiabartos yes, all modern versions of Windows can support long paths, but the application interacting with the file still has to support it too, and that support has to be compiled in.

Last I looked, even Excel didn’t support this, but that’s been a few years.