181–190 of 364 posts
Earlier quoted context omitted.
™ is not an emoji. It's part of the "Letterlike Symbols" block.
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.
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.
Those should obviously be UUIDs. Labels and titles should be a simple changeable, internationalizable attribute. Like usernames. You don’t use usernames as primary keys for anything, do you? What happens when people marry?
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.
Earlier quoted context omitted.
It looks like non-utf8 is not allowed: https://superuser.com/questions/204287/what-characters-are-f... Maybe it goes without saying, but for completeness, / is not allowed in filenames, and neither is null terminator (0x00 or \0) on mac either. On Linux, only / and null terminator are banned from filenames.
Sadly, you are not correct about slashes. They are allowed in filenames for Macs https://alexwlchan.net/2021/slashes/
Earlier quoted context omitted.
> 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.
It’s only forbidden for Windows users. I think the only character that Macs don't allow is the colon. AFAIK, everything else is fair game, even emojis. I just created a project with "ê" in the title. I wonder if I'll be able to share that with my Windows coworkers on Teams.
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…
Arch, I suppose.
Earlier quoted context omitted.
I bet there is another vulnerability here, although they also seem to blacklist % and ..
\\?\GLOBALROOT\ anyone? Now you're opening devices from the NT object namespace rather than files. Bonus: You can create the file C:\con\con using NT Native API filesystem calls. Someone even made a video of installing Windows into C:\con\con, and the kernel-side stuff works beautifully, and the explorer shell side dies horribly.
So, just like running Windows normally then? :D
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…
It's bad, ok... But honestly what's the goal? To let people name anything , including the name of a channel, anything they like, like, say: "rm -rf /*" Wait, I've got better: that rm -rf, but written "fr- mr" with RLO left/right overrides. Surely that is something to aim for because nothing shall ever go wrong? Thankfully having a file named https://example.org is illegal in Linux (and Windows too right?). Seriously:…
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.