| 00:11:43 | | Arcorann (Arcorann) joins |
| 00:46:01 | | Sluggs quits [Excess Flood] |
| 00:47:48 | | Sluggs joins |
| 02:02:23 | <ymgve> | JAA: https://archive.org/details/tosec-main |
| 02:03:28 | <ymgve> | the original torrent is 1. one of those that gets stuck at 99% due to metadata 2. incomplete, only containing 20% of the files in the item 3. somehow contains some older files that is _not_ in the item |
| 04:29:01 | | DogsRNice quits [Read error: Connection reset by peer] |
| 04:29:46 | | qw3rty__ quits [Ping timeout: 255 seconds] |
| 04:30:52 | | qw3rty__ joins |
| 04:54:53 | | G4te_Keep3r34924 quits [Ping timeout: 272 seconds] |
| 04:55:29 | | G4te_Keep3r34924 joins |
| 08:48:01 | | BearFortress quits [Client Quit] |
| 08:58:31 | <riking> | there have been a bunch of file modifications on the item but derive was never retriggered |
| 10:20:09 | | BearFortress joins |
| 10:24:01 | <@JAA> | ymgve: When an item is larger than a certain size threshold, IA won't generate a torrent. But it also won't delete the existing torrent file. The torrent in that item is from April 2023, but the last modification of the item's files was yesterday. |
| 10:24:34 | <ymgve> | yeah the item got modified when I added a comment with a magnet link |
| 10:24:57 | <ymgve> | but it seems like some files were changed out when TOSEC released an update last summer |
| 10:25:07 | <@JAA> | I don't recall what the size limit is, but probably 200 or 250 GiB, and this item is 254 GiB. |
| 10:25:55 | <@JAA> | > SKIPPING UPDATE to tosec-main_archive.torrent IN /6/items/tosec-main... item (260166 MB) exceeds maximum size (256000 MB) |
| 10:25:59 | <ymgve> | so what's a good way to link to the (hopefully) proper torrent I built? just a comment like I did, or a separate upload with the new torrent file? |
| 10:26:00 | <@JAA> | Yup, that's exactly what it is. |
| 10:26:14 | <@JAA> | Note that every metadata change etc. would invalidate the torrent, too. |
| 10:26:36 | <ymgve> | yeah, I excluded the metadata from the torrent I made |
| 10:27:25 | <@JAA> | If you upload a torrent file to an item, it'll get downloaded by IA, so that'd be duplicating all the item data. |
| 10:29:06 | <@JAA> | A review like that seems fine, I think. |
| 10:29:45 | <@JAA> | I wish IA would delete or at least deprecate the torrent when the item has been modified since. |
| 10:29:56 | <@JAA> | This leads to confusion constantly. |
| 10:30:29 | <ymgve> | it also seems to lead to lots of torrents that get stuck at 99.9% because the metadata is different |
| 10:30:48 | <ymgve> | the comment on the torrent says to download a new version, but generally there is no new torrent file |
| 10:35:55 | <ymgve> | for example https://archive.org/details/atarist-supremacy-vol1 |
| 10:37:44 | <@JAA> | Can't see what happened there, unfortunately. |
| 10:40:21 | <ymgve> | hm, actually, maybe the metadata isn't wrong on that one, but it still doesn't complete |
| 10:42:40 | <@JAA> | The metadata was updated since the torrent was generated. |
| 10:43:39 | <@JAA> | There's normally a reason why the torrent isn't regenerated, such as the 'SKIPPING UPDATE' I quoted above for tosec-main, but I can't see the details on atarist-supremacy-vol1 for whatever reason. |
| 11:02:27 | <ymgve> | oh wow, I guess there's some issues with how web seeds are listed in the torrent file |
| 11:03:52 | <ymgve> | I manually added the webseed "https://ia904503.us.archive.org/1/items/" and suddenly it completed |
| 11:05:59 | <ymgve> | not sure why it manages to download the large files but fails on the metadata though |
| 13:07:37 | | Arcorann quits [Ping timeout: 272 seconds] |
| 13:14:32 | | qwertyasdfuiopghjkl (qwertyasdfuiopghjkl) joins |
| 13:19:25 | | BearFortress quits [Ping timeout: 255 seconds] |
| 13:45:58 | | systwi_ joins |
| 15:27:32 | | kokos joins |
| 15:33:28 | | DavidSaguna joins |
| 15:33:56 | <DavidSaguna> | Hey, apologies if this information is already somewhere out there (couldn't find a recent twitter post), but is the Internet Archive down for maintenance or is it something unplanned? For me it's not working |
| 15:37:40 | <that_lurker> | some services seem to be down and as there is no post on social it could be unplanned |
| 15:41:38 | | steering (steering) joins |
| 15:56:40 | <DavidSaguna> | Alright! |
| 16:08:28 | | DavidSaguna quits [Read error: Connection reset by peer] |
| 16:19:03 | | Craigle quits [Quit: The Lounge - https://thelounge.chat] |
| 16:20:26 | | Craigle (Craigle) joins |
| 16:28:17 | | qwertyasdfuiopghjkl quits [Client Quit] |
| 16:43:17 | | qwertyasdfuiopghjkl (qwertyasdfuiopghjkl) joins |
| 16:53:42 | | BearFortress joins |
| 18:21:57 | | JaffaCakes118_2 (JaffaCakes118) joins |
| 18:25:07 | | JaffaCakes118 quits [Remote host closed the connection] |
| 19:30:54 | | DavidSaguna joins |
| 19:31:53 | <DavidSaguna> | They just posted the reason https://x.com/internetarchive/status/1810033483097743461 |
| 20:20:54 | | DavidSaguna quits [Read error: Connection reset by peer] |
| 20:46:28 | | DogsRNice joins |
| 20:46:29 | <imer> | that power grid is f'd lol can't even remember when I had the last outage locally.. |
| 20:59:25 | <fireonlive> | i hear california power is quite... bad |
| 20:59:30 | <fireonlive> | privatized too |
| 20:59:43 | <fireonlive> | power? profits! |
| 22:12:37 | <@JAA> | Hey now, it's only been 30 years since the first wildfire they were found guilty of causing by negligence of their equipment. You can't expect them to fix things that quickly! |
| 22:24:28 | | ymgve_ joins |
| 22:28:45 | | ymgve quits [Ping timeout: 272 seconds] |
| 22:48:23 | <fireonlive> | very unreasonable of me! x3 |