| 2 Jul 2025 |
 emily | fun | 23:55:02 |
 Katalin 🔪 | wtf | 23:55:08 |
| Katalin 🔪 | if you do this in iCloud drive, it shows up as “h” and “h 2” on a mac | 23:55:25 |
 Zhaofeng Li | lol, do they keep the associations between the... um, disambiguated versions? | 23:56:21 |
| Katalin 🔪 | yes | 23:56:28 |
| Zhaofeng Li | what if you then create a "h 2" on your phone? | 23:56:52 |
| emily | remember how Finder swaps / and :? | 23:57:08 |
| Katalin 🔪 | it shows up as “h 3” on the mac | 23:57:12 |
| emily | just thought you should have to think about that | 23:57:21 |
| Katalin 🔪 | In reply to @emilazy:matrix.org
remember how Finder swaps / and :? yeah. fun | 23:57:31 |
| 3 Jul 2025 |
 Randy Eckenrode | I hate that. | 00:00:48 |
| Zhaofeng Li | I guess slashes are more important to have than colons 😛 | 00:01:04 |
| Randy Eckenrode | Classic Mac OS uses : as the directory separator. | 00:01:20 |
| emily | it's – yeah | 00:01:23 |
| emily | you could use / but not : back then | 00:01:30 |
| emily | so when they ported stuff to an OS that has the reverse… | 00:01:40 |
| Randy Eckenrode | But classic Mac OS is long dead. Carbon is dead. Just screw those old applications. | 00:02:00 |
| emily | you could still see :-y paths in like, iTunes and stuff not that long ago (voice in my earpiece tells me how long ago it was) shouldn't I have a pension by now | 00:02:03 |
| emily | Katalin ⚧︎: also yeah so APFS fixes Unicode 9 from 2016 for all eternity | 00:02:18 |
| Randy Eckenrode | Or make it depend on the linked SDK. If your SDK is 26, / for you. | 00:02:25 |
| emily | stuff involving normalization rules for characters added after that just, won't get normalized | 00:02:35 |
| emily | so it's stupid and awful | 00:02:46 |
| emily | apparently case-sensitive APFS normalizes differently: https://eclecticlight.co/2017/04/06/apfs-is-currently-unusable-with-most-non-english-languages/ | 00:03:39 |
| emily | not sure if they changed this | 00:03:42 |
| Zhaofeng Li | Can it be for user friendliness? I guess people may want to have files named "A/B Test" or "Google I/O 26" | 00:03:46 |
| Zhaofeng Li | ... or to be precise, appear to be named | 00:03:54 |
| emily | it's all cursed anyway. you can't apply a simple set of string processing rules to result in filenames that users will reliably consider distinct iff your algorithm produces different output | 00:04:16 |
| Zhaofeng Li | but for colons, you can replace them with dashes and convey a similar meaning | 00:04:20 |
| emily | so it's pointless to even try | 00:04:23 |
| Randy Eckenrode | You can create files with newlines in the filename though. | 00:11:00 |
