00:07:59<myself>they've always said 18 minutes, never been clear on where it came from
00:08:10<myself>all pickup timeframes are arbitrary, why not make it not-round
00:22:02sec^nd quits [Remote host closed the connection]
00:22:20sec^nd (second) joins
00:35:55etnguyen03 quits [Client Quit]
00:39:47ATinySpaceMarine quits [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
01:27:51opl8 (opl) joins
01:29:58opl quits [Ping timeout: 260 seconds]
01:29:58opl8 is now known as opl
01:37:04etnguyen03 (etnguyen03) joins
01:37:54Sluggs quits [Ping timeout: 250 seconds]
01:42:20Sluggs joins
01:48:08etnguyen03 quits [Remote host closed the connection]
01:48:51etnguyen03 (etnguyen03) joins
02:45:43etnguyen03 quits [Remote host closed the connection]
02:46:26etnguyen03 (etnguyen03) joins
03:11:49ATinySpaceMarine joins
03:41:24TastyWiener95 quits [Ping timeout: 250 seconds]
03:42:30TastyWiener95 (TastyWiener95) joins
03:44:18TastyWiener95 quits [Read error: Connection reset by peer]
03:47:11etnguyen03 quits [Client Quit]
03:51:15etnguyen03 (etnguyen03) joins
04:07:10etnguyen03 quits [Remote host closed the connection]
05:16:02HP_Archivist quits [Quit: Leaving]
05:32:32pixel (pixel) joins
07:14:08tek_dmn quits [Ping timeout: 260 seconds]
07:33:44flotwig_ joins
07:35:08flotwig quits [Ping timeout: 260 seconds]
07:35:09flotwig_ is now known as flotwig
07:47:02pabs quits [Read error: Connection reset by peer]
07:47:46pabs (pabs) joins
08:58:58SootBector quits [Remote host closed the connection]
08:59:17SootBector (SootBector) joins
09:15:23nulldata quits [Quit: So long and thanks for all the fish!]
09:15:59nulldata (nulldata) joins
09:32:13Naruyoko5 quits [Read error: Connection reset by peer]
09:40:17ducky_ (ducky) joins
09:41:34ducky quits [Ping timeout: 260 seconds]
09:41:34ducky_ is now known as ducky
11:01:04LunarianBunny1147 quits [Quit: The Lounge - https://thelounge.chat]
11:01:55LunarianBunny1147 (LunarianBunny1147) joins
11:02:49HackMii quits [Remote host closed the connection]
11:03:16HackMii (hacktheplanet) joins
11:45:21arch quits [Remote host closed the connection]
11:45:43arch joins
11:54:12tek_dmn (tek_dmn) joins
12:00:01Bleo18260072271962345 quits [Quit: The Lounge - https://thelounge.chat]
12:02:48Bleo18260072271962345 joins
12:05:13benjins3 quits [Ping timeout: 260 seconds]
12:14:29tek_dmn quits [Client Quit]
12:17:47tek_dmn (tek_dmn) joins
12:35:59benjins3 joins
12:36:20NotGLaDOS (NotGLaDOS) joins
12:51:02Naruyoko joins
12:55:09Naruyoko quits [Read error: Connection reset by peer]
12:57:22Naruyoko joins
13:00:24tek_dmn quits [Client Quit]
13:00:40tek_dmn (tek_dmn) joins
13:03:12i_have_n0_idea quits [Quit: The Lounge - https://thelounge.chat]
13:03:34i_have_n0_idea (i_have_n0_idea) joins
13:08:33medecau (medecau) joins
13:11:56arch quits [Remote host closed the connection]
13:12:11arch joins
13:13:03medecau quits [Client Quit]
13:26:07i_have_n0_idea quits [Client Quit]
13:27:52i_have_n0_idea (i_have_n0_idea) joins
14:19:10<steering>something something URLs are hard? https://www.themoviedb.org/movie/1128939-a --> https://www.themoviedb.org/movie/1128939-balto-iv-wolf-destiny-part-one but that's a "Oops! We can't find the page you're looking for" (at least it's an actual 404)
14:19:30<steering>if it can't be found then how does it still know the title/slug :D
14:29:28grill (grill) joins
14:31:53<masterx244|m><steering> "if it can't be found then how..." <- something like that managed to confirm a unreleased lego set once. their shopsite had a snitchy 404 with a redirect like that that was caught by a data miner.
15:29:28valdikss quits [Ping timeout: 250 seconds]
15:33:41valdikss joins
15:49:14<sparky1492>Good Day All, Does anyone use ArchiveBox for archiving personal use? I have a question about the docker compose and the network config.
15:53:18valdikss quits [Ping timeout: 260 seconds]
15:53:20<sparky1492>or i guess anyone with decent Docker understanding could help. Here is the default compose.yaml(https://docker-compose.archivebox.io)
15:59:51BornOn420 quits [Remote host closed the connection]
16:00:26BornOn420 (BornOn420) joins
16:05:17matoro quits [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
16:05:30matoro joins
16:05:42Mateon1 quits [Remote host closed the connection]
16:05:53Mateon1 joins
16:21:47sparky1492 quits [Quit: No Rain, No Rainbows]
16:22:04sparky1492 (sparky1492) joins
16:44:09<nulldata>sparky1492 - What is the question?
16:48:46<sparky1492>nulldata: in the referenced compose.yaml, towards the bottom has "networks: dns: ipam:....." since I'm not using the pi-hole section can I not just replace the network section with just 'networks: {}' ?
16:50:48<sparky1492>or would I need to leave that since I'm running two of the containers in that stack?
16:56:02valdikss joins
17:00:20HP_Archivist (HP_Archivist) joins
17:17:56<nstrom|m>https://bunny.net/blog/introducing-magic-containers-what-edge-computing-was-meant-to-be/
17:19:06valdikss quits [Ping timeout: 250 seconds]
18:01:27corentin joins
18:04:32valdikss joins
18:26:16valdikss quits [Ping timeout: 250 seconds]
18:26:42<nulldata>sparky1492 - yeah you can comment it out with a # or remove it as long as kept the networks commented out in the other containers you're using
18:30:32valdikss joins
18:40:08valdikss quits [Ping timeout: 260 seconds]
18:56:58valdikss joins
18:59:26arch quits [Remote host closed the connection]
18:59:35arch joins
19:00:36<sparky1492>nulldata: 👍 Thank you very much for you time
19:06:08riteo quits [Ping timeout: 250 seconds]
19:14:43riteo (riteo) joins
19:33:06<@JAA>steering: There are YouTube channel URLs that don't work on their own, only if you click a link for them on the web interface.
19:33:29<@JAA>URLs are hard indeed.
19:44:11SootBector quits [Ping timeout: 276 seconds]
19:45:20SootBector (SootBector) joins
19:45:23<@JAA>nstrom|m: Interesting! The endpoint and env variable detection caught my eye in particular. It's stupid that there's no mechanism to programmatically communicate that.
20:17:33grill quits [Ping timeout: 260 seconds]
20:19:19arch quits [Remote host closed the connection]
20:19:28arch joins
20:31:22Sidpatchy (Sidpatchy) joins
20:35:29arch quits [Remote host closed the connection]
20:35:38arch joins
21:39:26<nstrom|m>looks like they do have api support on their roadmap but who knows what that means
22:08:49ducky quits [Ping timeout: 260 seconds]
22:08:55ducky (ducky) joins
22:09:18<@JAA>I mean on the container side. That sort of information should have a standardised encoding in the Containerfile. For env variables, there's ENV, but that requires a default or dummy value, and you can't attach an explanation to it. I'm not sure what exactly 'endpoint' means in this context; is it just the port(s) exposed by the container? There's EXPOSE for signalling that, and I suppose you don't
22:09:24<@JAA>need additional metadata in most cases.
22:31:33BlueMaxima joins
22:39:23<nstrom|m>Ah I see. Yeah not sure. I'm sure they were thinking of plain Jane web apps and not random services but a container's a container
22:40:24etnguyen03 (etnguyen03) joins
22:47:01<@JAA>I mean, half the point of that announcement is that everyone else only supports web apps but they're more flexible.
22:52:23caylin quits [Remote host closed the connection]
22:52:45caylin (caylin) joins
23:25:58katocala quits [Ping timeout: 260 seconds]
23:26:46katocala joins