HomeSearchPrevious dayNext day

03:06:02HP_Archivist quits [Read error: Connection reset by peer]
04:14:30killshot joins
04:31:58pabs quits [Client Quit]
04:32:14pabs (pabs) joins
04:40:21qwertyasdfuiopghjkl quits [Client Quit]
04:44:50sonick (sonick) joins
04:51:31qwertyasdfuiopghjkl (qwertyasdfuiopghjkl) joins
04:58:32dvd_ quits [Ping timeout: 252 seconds]
05:09:47atphoenix quits [Read error: Connection reset by peer]
05:12:18atphoenix (atphoenix) joins
05:24:20atphoenix quits [Read error: Connection reset by peer]
05:27:23atphoenix (atphoenix) joins
07:57:16Arcorann (Arcorann) joins
10:07:12sonick quits [Client Quit]
11:17:46Iki1 joins
11:20:58Iki quits [Ping timeout: 252 seconds]
12:25:17Iki1 quits [Ping timeout: 265 seconds]
12:41:46HP_Archivist (HP_Archivist) joins
13:00:33Iki joins
13:23:37Iki quits [Ping timeout: 252 seconds]
13:46:03HP_Archivist quits [Client Quit]
14:04:52DiscantX quits [Ping timeout: 252 seconds]
14:08:41DiscantX joins
14:28:34Iki joins
14:33:28qwertyasdfuiopghjkl quits [Client Quit]
14:54:57geezabiscuit (geezabiscuit) joins
15:01:31Arcorann quits [Ping timeout: 252 seconds]
15:06:20dvd joins
15:15:30dvd_ joins
15:16:22dvd quits [Ping timeout: 252 seconds]
15:26:16Iki quits [Ping timeout: 252 seconds]
15:27:19Iki joins
15:35:01dvd__ joins
15:35:24Iki1 joins
15:35:51geezabiscuit quits [Client Quit]
15:35:51dvd_ quits [Remote host closed the connection]
15:35:51Iki quits [Remote host closed the connection]
15:36:27geezabiscuit (geezabiscuit) joins
16:42:57ymgve joins
16:44:20<ymgve>anyone got issues with torrents from the archive recently? it seems like the last piece doesn't download from the webseed
16:58:24ymgve_ joins
17:00:52ymgve quits [Ping timeout: 252 seconds]
17:01:53ymgve__ joins
17:05:16ymgve_ quits [Ping timeout: 252 seconds]
17:27:33ymgve__ is now known as ymgve
17:35:42killshot quits [Ping timeout: 252 seconds]
17:45:57ymgve_ joins
17:48:43ymgve quits [Ping timeout: 252 seconds]
18:37:26dvd__ quits [Remote host closed the connection]
18:44:35ymgve_ is now known as ymgve
19:10:46dvd joins
19:10:47dvd_ joins
19:11:10dvd_ quits [Remote host closed the connection]
19:44:38Barto quits [Ping timeout: 265 seconds]
19:51:17BearFortress quits [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
20:33:14Barto (Barto) joins
21:08:00tech234a quits [Quit: Connection closed for inactivity]
21:10:40<@arkiver>ymgve: can you give me an exampe?
21:10:42<@arkiver>example*
21:10:53<@arkiver>this is unfortunately a problem that i didn't hear for the first time
21:11:07<ymgve>https://archive.org/details/atarist-supremacy-vol2
21:11:27<ymgve>and https://archive.org/details/amiga-elysian-archive
21:11:35<@arkiver>thank you
21:12:15<ymgve>do you have any relation to the discmaster project btw?
21:25:23<@arkiver>no
22:39:18Sanqui quits [Ping timeout: 252 seconds]
22:43:18HP_Archivist (HP_Archivist) joins
22:59:04Sanqui joins
22:59:06Sanqui quits [Changing host]
22:59:06Sanqui (Sanqui) joins
23:05:19HP_Archivist quits [Client Quit]
23:09:21tzt quits [Client Quit]
23:10:56tzt (tzt) joins
23:35:23<atphoenix>I noticed today that WBM sometimes considers URLs to be equivalent that are not actually equivalent. This makes the calendar/timeline not work correctly. I specifically ran into this with the case-sensitive URL https://goo.gl/4WJatw
23:36:43<atphoenix>If you start at https://web.archive.org/web/*/https://goo.gl/4WJatw and follow the 2019 archive link, you end up at https://web.archive.org/web/20190105222011/http://goo.gl/4wjatw
23:37:34Sanqui quits [Client Quit]
23:37:55Sanqui joins
23:37:57Sanqui quits [Changing host]
23:37:57Sanqui (Sanqui) joins
23:38:03<atphoenix>The current destination of https://goo.gl/4WJatw is https://developer.android.com/studio#downloads
23:38:57<@JAA>That's the WBM's definition of equivalent, yeah.
23:39:38<@JAA>Protocol, auth data, leading 'www.' (and port number?) are stripped, and the rest of the URL is lowercased.
23:39:41<@JAA>And yes, it sucks.
23:40:26<@JAA>There's also some further normalisation for IDNs and percent encoding, I think.
23:45:04<atphoenix>as a heuristic, that's a decent way to try to fill in gaps and redundancies, but it's also flawed, especially when dealing with cases like case sensitive URL shorteners that could be pointing to completely opposite things in the various capitalizations.
23:49:53<@JAA>Yep. I moaned extensively about it when I dealt with the Picosong archive, which uses case-sensitive short codes as well.

HomeSearchPrevious dayNext day