| 00:13:11 | | Barto quits [Client Quit] |
| 00:14:15 | | Barto (Barto) joins |
| 01:59:03 | | sepro quits [Read error: Connection reset by peer] |
| 01:59:24 | | sepro2 (sepro) joins |
| 02:09:55 | | tzt quits [Remote host closed the connection] |
| 02:25:00 | | Doranwen quits [Remote host closed the connection] |
| 02:25:24 | | Doranwen (Doranwen) joins |
| 02:36:38 | | tzt (tzt) joins |
| 08:36:25 | | Sanqui_ is now known as Sanqui |
| 11:29:20 | | JaffaCakes118_2 (JaffaCakes118) joins |
| 11:30:06 | | JaffaCakes118 quits [Remote host closed the connection] |
| 11:30:06 | | JaffaCakes118_2 quits [Read error: Connection reset by peer] |
| 11:30:15 | | JaffaCakes118_2 (JaffaCakes118) joins |
| 12:11:21 | | JaffaCakes118_2 quits [Read error: Connection reset by peer] |
| 14:16:46 | | JaffaCakes118 (JaffaCakes118) joins |
| 15:02:33 | | Lord_Nightmare quits [Quit: ZNC - http://znc.in] |
| 15:06:27 | | Lord_Nightmare (Lord_Nightmare) joins |
| 15:24:20 | <IDK> | did IA start moving stuff to internet archive canada? |
| 15:24:31 | <IDK> | im seeing some archivebot stuff being moved to https://dn720900.ca.archive.org/0/ |
| 15:27:39 | <IDK> | (example https://dn720605.ca.archive.org/0/items/archiveteam_archivebot_go_20200527230002/www.scdc.sh.cn-inf-20200527-140137-cquui.json) |
| 15:45:22 | <IDK> | And the canada one is usually 3-5x the speed as the us servers |
| 16:12:57 | <@arkiver> | IDK: yeah! |
| 16:23:19 | <IDK> | so, are all items expected to have a canadian copy |
| 16:23:32 | <IDK> | or has it already happened |
| 16:58:31 | | JaffaCakes118_2 (JaffaCakes118) joins |
| 16:58:37 | | JaffaCakes118 quits [Remote host closed the connection] |
| 17:07:52 | | JaffaCakes (JaffaCakes118) joins |
| 17:11:37 | | JaffaCakes118_2 quits [Ping timeout: 255 seconds] |
| 18:27:04 | | qwertyasdfuiopghjkl quits [Quit: Client closed] |
| 18:28:43 | | andrew quits [Client Quit] |
| 18:35:29 | | qwertyasdfuiopghjkl (qwertyasdfuiopghjkl) joins |
| 18:36:59 | | andrew (andrew) joins |
| 18:49:43 | | rewby quits [Ping timeout: 255 seconds] |
| 19:24:00 | | rewby (rewby) joins |
| 21:04:43 | | SootBector quits [Ping timeout: 260 seconds] |
| 21:06:49 | | SootBector (SootBector) joins |
| 21:10:36 | | that_lurker quits [Remote host closed the connection] |
| 21:10:40 | | that_lurker joins |
| 21:10:41 | | that_lurker is now authenticated as that_lurker |
| 23:01:56 | <@JAA> | Ugh, why are the good item names hogged by darked nonsense? I wanted to create a placeholder item for previous_item and next_item metadata fields to explicitly indicate that no such item exists, i.e. that it's the end of the series (as opposed to that field simply having been forgotten). But 'None' was used for various stuff over the years and darked in late 2023, and 'no_item' was darked for being |
| 23:02:02 | <@JAA> | spam. :-( |
| 23:03:23 | <@JAA> | And TIL that the S3 API error is useless when you try to upload an item with a case collision. E.g. uploading 'none' will return a generic InvalidBucket error about how it's not a valid identifier. The IA CLI apparently catches that and at least mentions in its error message that case collisions can cause this. |
| 23:03:33 | <@JAA> | I haven't yet found a way to canonicalise an item identifier though. |
| 23:04:41 | <@JAA> | The S3 error: |
| 23:04:41 | <@JAA> | > <Error><Code>InvalidBucketName</Code><Message>The specified bucket is not valid.</Message><Resource>Bucket names should be valid archive identifiers; try someting matching this regular expression: ^[a-zA-Z0-9][a-zA-Z0-9_.-]{4,100}$ (or, if you are making unusual identifiers, this user may lack the special permission to do so)</Resource><RequestId>snip</RequestId></Error> |
| 23:05:02 | <@JAA> | IA CLI prints this: |
| 23:05:04 | <@JAA> | > The specified bucket is not valid. - auto_make_bucket requested, 'none' does not exist and name is unavailable. A case alias may already exist. |