00:01:29pie_ quits []
00:08:08pie_ joins
00:18:01fishingf0rpie joins
00:21:56fishingforpie quits [Ping timeout: 268 seconds]
00:22:48holbrooke joins
00:23:40holbrooke quits [Client Quit]
00:34:34holbrooke joins
00:35:04holbrooke quits [Client Quit]
00:36:57holbrooke joins
00:37:51holbrooke quits [Client Quit]
00:46:25holbrooke joins
00:47:30holbrooke quits [Client Quit]
02:31:21holbrooke joins
02:32:03holbrooke quits [Client Quit]
02:57:04holbrooke joins
02:57:53holbrooke quits [Client Quit]
02:59:03holbrooke joins
03:08:56holbrooke quits [Client Quit]
03:26:34holbrooke joins
03:28:04holbrooke quits [Client Quit]
03:36:48Mateon2 joins
03:37:49Minkafighter7 quits [Client Quit]
03:37:49Mateon1 quits [Remote host closed the connection]
03:37:49Mateon2 is now known as Mateon1
03:37:55Minkafighter7 joins
04:07:52mut4ntmonkey quits [Remote host closed the connection]
04:08:31mut4ntmonkey (mutantmonkey) joins
04:29:11thuban joins
05:23:26atphoenix_ is now known as atphoenix
05:31:56<atphoenix>Doranwen, interesting story about commas. Here is another way to have some filesystem fun: use Linux to mount an NTFS filesystem. Then you can create filenames, folders, and really deep trees, that are technically okay for NTFS (or at least according to the Linux NTFS parser), but that Windows Explorer cannot handle and will choke on. The easiest fix is to mount it again on Linux, rename the relevant files, and if it was tree depth
05:31:56<atphoenix>issue, lessen the depth. The Windows CHKDSK may detect files and folders with these anomalies, and offer to 'repair' them (by renaming them to something 'helpful' like FILE0001.CHK or similar), but it is cleaner to go back to Linux to make edits.
05:32:32<Doranwen>atphoenix: In this case, the files were on Linux in the first place, but I can see how that would happen.
05:33:06<Doranwen>They were reasonably long file names as they were, and tripling the length of the name must've hit some limit or something…
05:33:16<Doranwen>*It was a reasonably long file name as it was
05:34:08<Doranwen>Renaming to remove the commas and resend over worked just fine, which I should've done in the first place, lol. I was just used to "eh, fix it afterwards" (because I can just remove the beginning and end of the filename and the rest is intact) and didn't think about how *two* commas in that name might be pushing it, lol.
05:39:13<atphoenix>The most common way I have run into said filesystem anomalies is by saving webpages on Linux, where the page title has a : (colon) in it. Windows Explorer doesn't allow that, but NTFS does. So I had copied the saved page to an NTFS partition, and when back in Windows...Explorer was not able to work with the file.
05:41:02borislav quits [Remote host closed the connection]
05:42:18<atphoenix>you may have hit the 255 characters name length limit
05:58:08<pabs>https://appleinsider.com/articles/22/11/04/apple-kills-long-time-event-archive-on-youtube/
05:58:36<pabs>https://nitter.net/realmrpippy/status/1588599228510502912
06:12:14sec^nd quits [Ping timeout: 255 seconds]
06:46:20sec^nd (second) joins
06:53:41nepeat quits [Client Quit]
06:53:41qwertyasdfuiopghjkl quits [Client Quit]
06:53:59nepeat (nepeat) joins
06:54:14qwertyasdfuiopghjkl joins
06:57:55sec^nd quits [Remote host closed the connection]
07:05:16sec^nd (second) joins
07:14:10BlueMaxima quits [Read error: Connection reset by peer]
09:34:48Mateon1 quits [Remote host closed the connection]
09:35:15Mateon1 joins
09:55:37Mateon2 joins
09:56:58Mateon1 quits [Remote host closed the connection]
09:56:58Mateon2 is now known as Mateon1
10:01:28qwertyasdfuiopghjkl quits [Remote host closed the connection]
10:22:25spirit joins
10:40:06qw3rty_ joins
10:40:07qw3rty quits [Read error: Connection reset by peer]
10:40:12sec^nd quits [Ping timeout: 255 seconds]
10:42:34jodizzle quits [Quit: ...]
10:49:27jodizzle (jodizzle) joins
10:56:11qwertyasdfuiopghjkl joins
11:09:58sec^nd (second) joins
11:10:35sec^nd quits [Remote host closed the connection]
11:51:16sec^nd (second) joins
11:54:39sonick (sonick) joins
12:00:37sec^nd quits [Remote host closed the connection]
12:26:57sec^nd (second) joins
12:31:27Arcorann quits [Ping timeout: 268 seconds]
13:00:14<@JAA>IIRC, you can also create capitalisation collisions on NTFS from Linux. That's not a FS limitation, just a Windows API limitation. It gets fun when you access it from Windows again.
13:01:09<@JAA>Just like you can create COM, AUX, etc. on Linux but not through the Windows API.
13:02:16<@JAA>These limitations date back to the DOS days, I think? It's ridiculous that they're still in place four decades later...
13:02:47<@JAA>(Also, CON, not COM, or alternatively COM1.)
13:44:48Mateon1 quits [Remote host closed the connection]
13:52:24Mateon1 joins
14:23:30Mateon1 quits [Client Quit]
14:52:52Chris5010 quits [Ping timeout: 240 seconds]
15:42:16<atphoenix>CON (console) and AUX definitely date back to DOS days. Back on MS-DOS 3.3, one way to create simple, short, text files (there was no built-in friendly editor [EDLIN wasn't friendly]) was to issue this command: "COPY CON NOTES.TXT". That's let you type one line on the console, hit enter, and it'd be added to the file. No editing capability after hitting enter, but it served basic needs for short text and batch file creation.
15:42:52<atphoenix>s/That's/That'd
16:19:19nepeat_ (nepeat) joins
16:19:53qwertyasdfuiopghjkl quits [Client Quit]
16:19:53nepeat quits [Client Quit]
16:21:00tech_exorcist (tech_exorcist) joins
16:24:12tech_exorcist quits [Client Quit]
16:24:24tech_exorcist (tech_exorcist) joins
16:25:31<Barto>JAA: even pre-dos limitation. CP/M i'd say
16:27:54<Barto>https://twitter.com/foone/status/1058676834940776450 foone got it covered
16:28:24<@JAA>:-)
16:28:45<@JAA>Can always rely on a good rant from foone.
16:28:55<Barto>trusty source :-)
16:33:20<@JAA>Didn't know about C:\con\con, hah, fun!
16:34:27<Barto>clearly something i'll attempt next time i see win95
16:34:31<Barto>but that doesn't happen often
16:35:32qwertyasdfuiopghjkl joins
16:36:13Chris5010 (Chris5010) joins
16:45:09<atphoenix>Barto, I wonder if you can try it on this: https://www.ghacks.net/2022/10/24/run-windows-95-as-a-javascript-app-on-your-computer-and-play-a-bit-of-doom-while-you-are-at-it/
16:46:36<atphoenix>https://github.com/felixrieseberg/windows95
16:47:04<Barto>https://archive.org/details/win95_in_dosbox
16:56:30sec^nd quits [Remote host closed the connection]
16:56:37<Barto>aaand, it worked
16:56:53sec^nd (second) joins
17:01:54sec^nd quits [Remote host closed the connection]
17:02:23sec^nd (second) joins
17:13:41sec^nd quits [Remote host closed the connection]
17:14:06sec^nd (second) joins
17:38:13Mateon1 joins
17:39:12dm4v_ joins
17:41:38dm4v quits [Ping timeout: 268 seconds]
17:41:38dm4v_ is now known as dm4v
18:20:13fishingf0rpie quits [Client Quit]
18:42:53sec^nd quits [Remote host closed the connection]
18:44:23sec^nd (second) joins
19:08:02jess quits []
19:11:36Mateon1 quits [Remote host closed the connection]
19:11:46Mateon1 joins
19:20:49driib quits [Read error: Connection reset by peer]
19:20:52Terbium quits [Ping timeout: 240 seconds]
19:20:55driib (driib) joins
19:21:04Terbium joins
19:28:25fishingforpie joins
20:11:39TheTechRobo quits [Remote host closed the connection]
20:13:55TheTechRobo (TheTechRobo) joins
20:25:23jess (jess) joins
20:58:28tech_exorcist quits [Client Quit]
21:33:27BlueMaxima joins
21:42:52Gereon6200 quits [Ping timeout: 240 seconds]
22:37:53Mateon1 quits [Remote host closed the connection]
22:38:02Mateon1 joins
22:38:32borislav joins
23:19:25qwertyasdfuiopghjkl100 joins
23:21:11qwertyasdfuiopghjkl quits [Ping timeout: 265 seconds]
23:24:02qwertyasdfuiopghjkl100 is now known as qwertyasdfuiopghjkl