00:06:04etnguyen03 quits [Client Quit]
00:13:25<@arkiver>so boards.ie is not shutting down anymore
00:14:11<@arkiver>for TTN, looks like the posts have sequential IDs and they don't go above 60k, so that seems like a good AB target
00:14:21<@arkiver>AB job* i should say
00:15:45Guest58 quits [Client Quit]
00:15:56cultpony quits [Ping timeout: 256 seconds]
00:17:52<@arkiver>tatu.nu i just put in AB
00:17:54Webuser714510 joins
00:17:58<@arkiver>jjang0u is covered with #jjang0n
00:18:30cultpony (cultpony) joins
00:18:31etnguyen03 (etnguyen03) joins
00:19:34Webuser714510 quits [Client Quit]
00:25:20<tzt>Japanese beatmania mastodon instance bms.social is shutting down on 2025-12-20 https://fohte.net/blog/posts/2025-11-30-close-bms-social
00:50:03Guest58 joins
00:52:24etnguyen03 quits [Client Quit]
01:08:24Guest58 quits [Client Quit]
01:08:48Guest58 joins
01:17:56<klea>arkiver: what's latest ttn post id?
01:18:05<klea>is there some kind of redirect?
01:18:27<klea>yes
01:18:29<klea>nice
01:18:37<klea>iirc !ao follows redirects right?
01:19:30<klea>https://social.ttn.place/post/59286 seems to make redirect
01:21:15nexussfan quits [Client Quit]
01:21:36nexussfan (nexussfan) joins
01:32:37Guest58 quits [Read error: Connection reset by peer]
01:34:13Guest58 joins
01:48:44etnguyen03 (etnguyen03) joins
01:57:44ducky quits [Ping timeout: 260 seconds]
02:00:10Guest58 quits [Client Quit]
02:02:24kansei quits [Quit: ZNC 1.10.1 - https://znc.in]
02:16:22flotwig quits [Quit: ZNC - http://znc.in]
02:18:49Guest58 joins
02:38:57ducky (ducky) joins
02:41:04Guest58 quits [Client Quit]
02:45:44Guest58 joins
02:45:52Justin[home] quits [Remote host closed the connection]
02:49:44klea wonders if poop.is was archived -- https://git.j3s.sh/poop.is/
02:50:46jason joins
02:51:13Guest58 quits [Client Quit]
02:53:37Guest58 joins
02:55:50kansei (kansei) joins
02:59:44DopefishJustin joins
03:03:10flotwig joins
03:04:03Guest58 quits [Client Quit]
03:06:40Guest58 joins
03:11:11notarobot17 joins
03:13:39Guest58 quits [Client Quit]
03:16:46Guest58 joins
03:24:52Guest58 quits [Client Quit]
03:25:42Guest58 joins
03:25:44klea wonders who runs atdr.meo.ws
03:29:22jason quits [Read error: Connection reset by peer]
03:29:23Guest58 quits [Client Quit]
03:29:35jason joins
03:32:03jason quits [Read error: Connection reset by peer]
03:32:06notarobot17 quits [Client Quit]
03:32:31etnguyen03 quits [Client Quit]
03:33:14jason joins
03:33:57notarobot17 joins
03:34:51etnguyen03 (etnguyen03) joins
03:41:28hexagonwin_ quits [Read error: Connection reset by peer]
03:42:11hexagonwin joins
03:42:58flotwig quits [Client Quit]
03:54:27etnguyen03 quits [Remote host closed the connection]
04:01:09flotwig joins
04:02:23sg72 quits [Remote host closed the connection]
04:03:44sg72 joins
04:09:55<Guest>klea: https://archive.ph/9DQIZ
04:10:19<Guest>the page on meo.ws is gone now though
04:31:31SootBector quits [Remote host closed the connection]
04:32:40SootBector (SootBector) joins
04:32:56jason quits [Remote host closed the connection]
04:33:20Guest58 joins
04:36:31<@JAA>It's part of the core AT infra.
04:37:59Guest58 quits [Ping timeout: 272 seconds]
04:41:54<Guest>it stands for ArchiveTeamDockerRegistry right? ATDR
04:47:42<@JAA>Yes
05:01:34<h2ibot>Cooljeanius edited Android Applications (-21, Android is not iOS): https://wiki.archiveteam.org/?diff=58212&oldid=58201
05:15:07Guest58 joins
05:23:02Webuser951325 joins
05:23:06Webuser951325 quits [Client Quit]
05:33:22Bestest quits [Quit: Ooops, wrong browser tab.]
05:45:47Chris50104 (Chris5010) joins
05:47:39Chris5010 quits [Ping timeout: 272 seconds]
05:47:39Chris50104 is now known as Chris5010
06:20:24AlsoHP_Archivist joins
06:24:16HP_Archivist quits [Ping timeout: 256 seconds]
06:24:44nexussfan quits [Quit: Konversation terminated!]
06:25:41linuxgemini quits [Quit: Ping timeout (120 seconds)]
06:25:50linuxgemini (linuxgemini) joins
06:25:58AlsoHP_Archivist quits [Ping timeout: 256 seconds]
06:56:08linuxgemini quits [Client Quit]
06:56:27linuxgemini (linuxgemini) joins
07:11:30Dada joins
07:13:09DogsRNice quits [Read error: Connection reset by peer]
07:27:46nathang2184 quits [Quit: The Lounge - https://thelounge.chat]
07:30:12cyanbox_ joins
07:32:50cyanbox quits [Ping timeout: 256 seconds]
07:43:33croissant` quits [Ping timeout: 272 seconds]
07:45:42croissant joins
08:17:36ducky quits [Ping timeout: 260 seconds]
08:19:06vitzli (vitzli) joins
08:28:38nathang2184 joins
08:34:20nathang2184 quits [Client Quit]
08:35:06nathang2184 joins
08:39:58vitzli quits [Client Quit]
08:54:31lennier2 quits [Read error: Connection reset by peer]
08:54:47lennier2 joins
09:07:24IDK quits [Quit: Connection closed for inactivity]
09:19:26ducky (ducky) joins
09:25:27Guest58 quits [Quit: My Mac has gone to sleep. ZZZzzz…]
10:20:28Dada quits [Remote host closed the connection]
10:44:59Wohlstand (Wohlstand) joins
11:04:13CYBERDEV__ joins
11:05:13CYBERDEV_ quits [Read error: Connection reset by peer]
11:46:10Guest58 joins
12:27:41Dada joins
12:33:49linuxgemini quits [Quit: Ping timeout (120 seconds)]
12:34:11linuxgemini (linuxgemini) joins
13:04:43Guest58 quits [Client Quit]
13:10:59pedantic-darwin quits [Ping timeout: 272 seconds]
13:14:11fangfufu quits [Quit: ZNC 1.9.1+deb2+b3 - https://znc.in]
13:31:30fangfufu joins
14:06:40lennier2 quits [Ping timeout: 256 seconds]
14:07:14khaoohs quits [Ping timeout: 256 seconds]
14:13:07nathang2184 quits [Quit: The Lounge - https://thelounge.chat]
14:21:11Guest58 joins
14:33:12nathang2184 joins
14:40:04nathang2184 quits [Client Quit]
14:41:14nathang2184 joins
14:47:12APOLLO03 quits [Read error: Connection reset by peer]
14:48:00APOLLO03 joins
14:59:44khaoohs joins
15:50:51<justauser|m>Time to finish the Yay.boo.
15:53:04<justauser|m>https://transfer.archivete.am/tV3vU/yayboo_comb.txt
15:53:05<eggdrop>inline (for browser viewing): https://transfer.archivete.am/inline/tV3vU/yayboo_comb.txt
15:53:11<justauser|m>All of the above, combined.
15:53:46<justauser|m>TheTechRobo: ^ I guess.
16:03:04Webuser690112 joins
16:03:33Webuser690112 quits [Client Quit]
16:25:20<TheTechRobo>for what?
16:28:53<DigitalDragons>nicolas17: fixed it :D
16:32:15<DigitalDragons>klea: I happen to have already made that :p
16:32:17<DigitalDragons>if you put https://fixit.digitaldragon.dev/ in front of an expired Discord CDN url, it will refresh it and then redirect
16:32:19<@arkiver>TheTechRobo: to run the front pages through #jseater
16:32:22<@arkiver>if possible
16:32:25<@arkiver>they'll also be run through AB
16:32:32<klea>DigitalDragons: thanks
16:32:35<klea>that's neat
16:32:54<klea>DigitalDragons: could you make some bulk endpoint or smth, or does AB handle !ao < jobs 201 by following it?
16:34:09klea wonders if DigitalDragons's fixit. thing is public or not, knows it'd require registering to discord, and poking to their api to send a message at least
16:35:57<DigitalDragons>AB can just follow the redirects on an !ao <, but fixit is kinda slow because of Discord ratelimiting
16:37:22<DigitalDragons>if there's a large pile of links we need archived I think there are some things I can do to improve that, it would just take some work
16:39:04<DigitalDragons>it's public, but also don't go shouting from the rooftops about it because it can get overloaded (=slow) quite easily ':)
16:41:34<klea>i mean the code
16:42:06<klea>as in, i'd like to see how it works, and try to make my own thingy based on it for a pile of urlls
16:42:30<DigitalDragons>oh oops
16:42:37<DigitalDragons>i can do that, one minute
16:42:51<klea>thanks in advance :)
16:45:06<klea>i've noticed https://control.archiveteam.net has expired cert
16:55:29<DigitalDragons>klea: https://github.com/DigitalDwagon/DiscordRehydrator
16:55:36ducky quits [Ping timeout: 260 seconds]
16:58:33ducky (ducky) joins
16:59:53<klea>thanks
17:01:34<klea>oh darn, hardcoded guild id :p
17:04:56<katia>darn
17:08:32<DigitalDragons>i was *very* lazy when i wrote that
17:08:47<DigitalDragons>the token was hardcoded too until about 10 minutes ago :D
17:30:10Shard795 quits [Quit: Im doing something rq. Il brb]
17:32:51khaoohs quits [Client Quit]
17:36:02Shard7959 (Shard) joins
17:43:46<klea>lol
17:43:53<klea>oh, that's what the 10 minutes where for ;p
18:04:24Shard7959 quits [Client Quit]
18:05:00Shard7959 (Shard) joins
18:11:43Shard7959 quits [Client Quit]
18:12:24Shard7959 (Shard) joins
18:13:16DogDisco joins
18:41:44<klea>should i make a wiki entry for the nixos cache
18:41:50<klea>ie, the small s3 repo called cache.nixos.org
18:41:57<klea>by small i mean hosts likely a lot of data
18:51:11<that_lurker>A section about nixos in general might be useful
18:54:16<that_lurker>good thing we can blame hexa- if some form of archival takes that down :-P
18:56:51Webuser775104 joins
18:57:18Webuser775104 quits [Client Quit]
19:10:04sec^nd quits [Remote host closed the connection]
19:10:41sec^nd (second) joins
19:13:15nathang2184 quits [Ping timeout: 272 seconds]
19:19:55IDK (IDK) joins
19:22:14dendory quits [Quit: The Lounge - https://thelounge.chat]
19:23:34dendory (dendory) joins
19:32:29khaoohs joins
19:38:26<klea>wdym by blame hexa-?
19:39:49<that_lurker>hexa- is on the NixOS infra team
19:40:01<klea>oh
19:40:26klea wonders if hexa- could provide us a list of all entries in the cache bucket, and/or approximate filesize
19:41:26<klea>someone being on NixOS's infra team seems like a good reason to make the entirety of the ci rely on nix expressions, maybe the nixos project could even contribute some execution time on hydra.nixos.org
19:42:32DogsRNice joins
20:06:12<TheTechRobo>!remindme 6h mnbot queue thing
20:06:12<eggdrop>[remind] ok, i'll remind you at 2025-12-03T02:06:12Z
20:25:19nathang2184 joins
20:33:01gosc joins
20:51:45HP_Archivist (HP_Archivist) joins
21:09:16<DogDisco>I found some mediafire links that require a password. The passwords are known though. Is there a way to archive those on #mediaonfire?
21:14:07<@JAA>That's a question for #mediaonfire then. :-)
21:19:58<DogDisco>JAA ah ok I thought that channel was commands only. Thanks for letting me know!
21:27:56Dada quits [Remote host closed the connection]
21:47:48gosc quits [Client Quit]
21:48:14<hexa->klea: something north of 700 TiB
21:48:25<hexa->TheTechRobo: actually team lead :)
21:48:49<klea>hexa-: thanks, now JAA has a proportion for how big the cache is
21:48:55<hexa->the nix-cache s3 bucket is configured as requester-pays
21:48:59<klea>oh
21:49:21<klea>no, i was thinking of getting things via https://cache.nixos.org/ without going trough the bucket
21:49:30<hexa->yeah, that'll work
21:49:39<klea>is there some way to get a list of all the hashes?
21:49:47<@JAA>klea: Yeah, that's the same figure we arrived at in our recent brief discussion about it.
21:49:58<hexa->hrm hrm
21:50:02<klea>JAA: but this time it's confirmed by a official source!
21:50:16<hexa->can probably procure parquet files
21:50:17<klea>not just is this data possibly out of date?
21:50:26<@JAA>I think it was confirmed then as well by some official-ish graphs of how the size has grown.
21:50:27<klea>JAA: how should we query it?
21:50:37<hexa->https://docs.google.com/spreadsheets/d/1KA2tbPsi1kQuwlHJC89iWUQBXPv6p1N3n0t73bbK7n4/edit?gid=1886954529#gid=1886954529
21:50:38<klea>it was a officialish excel table on google
21:50:40<klea>yeah that
21:50:43<@JAA>Yeah
21:50:46<hexa->that's mine :)
21:50:55<@JAA>Hah
21:50:57<klea>oh nice
21:51:20<klea>how do we archive such a big thing?
21:52:04<@JAA>The hard part is convincing IA that this is a good idea. :-)
21:52:05<hexa->does it even make sense to begin with? ;p
21:52:23<klea>JAA: oh, we have to talk to people?
21:52:26klea hides
21:52:33Webuser267529 joins
21:52:44Webuser267529 quits [Client Quit]
21:52:58<klea>hexa-: yes, because amazon's not a non profit, but we should probably also resurrect #internetarchive.bak maybe?
21:53:28<@JAA>Holographic basically free storage when?
21:53:42<klea>i don't have that
21:53:43<hexa->you tell me
21:54:19klea wonders if nixos would like some help in making their cache bigger
21:54:38<klea>i guess probably not
21:55:13<hexa->hell no
21:55:30<hexa->personally I want us to become more agile with the cache data :p
21:55:44@JAA builds a 'nixos-cache' package that contains all the cache data.
21:56:00<klea>by more agile you mean have less data?
21:56:09<hexa->yeah, keep like 3y at most
21:56:18<klea>see this is why we have to archive it
21:56:21<hexa->we support up to 7 months with security
21:56:31<hexa->and everything beyond that is complicated
21:56:46<hexa->i say 3y because that's a semi-reasonable timeframe to bisect anything across the monorepo
21:56:48<klea>hexa-: we need old old old stuff (at least keep sources (including sources for vendorthingies))
21:56:54<hexa->and having cached stuff along the path helps a ton
21:57:05<hexa->there is the tarballs mirror as well
21:57:20<hexa->https://tarballs.nixos.org/
21:57:23<klea>probably before deleting data it'd be neat if it was dumped to AT, and IA would be happy
21:57:33<klea>oh no, more content?
21:57:38<@JAA>A lot of old software only survives through random tarballs or binaries from distros and other places.
21:57:39<hexa->yeah, I don't think we're in a hurry
21:57:49<klea>2025-12-02 21:57:38 <@JAA> A lot of old software only survives through random tarballs or binaries from distros and other places. <- yes, this is why nixos should keep everything
21:57:54<klea>every cache keep everything
21:58:00<@JAA>So yeah, if this ever turns from a vague idea to a plan, I'm sure we'll hear about it. :-)
21:58:20<klea>afaik the tinycore linux thingy is small because they don't update packages unless they think they're needed :p
21:59:02<hexa->nixpkgs is very rebuilds heavy because rebuilds happen based on reverse dependency changes
21:59:15<hexa->wait … dependency changes? reverse dependency changes?
21:59:19<klea>what
21:59:23<hexa->well, if we update bash we have to rebuild the world
21:59:30<hexa->so it's reverse dependencies :D
21:59:31<klea>everything depends on bash
21:59:38<hexa->in a way
21:59:51klea was thinking about trying to make nix expressions for AT, to be able to build the things that AT relies on and tests, and very happily send that to the hydra.nixos.org setup :p
22:00:03<@JAA>Right, anything that directly or indirectly depends on X needs to be rebuilt when X changes.
22:00:07<klea>but i guess that'd have to get approved by nixos, which would be unlikely
22:00:17<hexa->when most distros just do rebuilds whenever ABI changes
22:00:17<klea>2025-12-02 22:00:02 <@JAA> Right, anything that directly or indirectly depends on X needs to be rebuilt when X changes. <- afaik yes
22:00:29<hexa->and for the most time I thought that was super wasteful
22:00:32<klea>i experience this because i have some packages on my nixcfg
22:00:50<klea>hexa-: what uses does it have, appart from being the most up to date?
22:01:13<hexa->the way derivations are defined make it that way
22:01:27<klea>yeah it's neatish in a way
22:01:52<hexa->you have a package definition, that gets transformed into an aterm definition (the derivation) and that has a hash of all inputs
22:02:11<hexa->if the inputs change then that hash gets invalidated and you need to build/substitute a new derivation
22:02:17<klea>i should try to move those packages away from my nix configuration and into nixpkgs, yes probably, will i, likely not since i have at least one package thingy i expressed myself and added my own patch for myself, which isn't included in upstream, and wouldn't like to add it, but if i add that derivation, without the patch, i'm not using the derivation
22:03:35<klea>and also, being a patch means the only step it'd save me is downloading the source code and go vendor code, which well, if i have to update the files myself because i don't think the nix robot updater thing dealt with go module packages and vendorhash (i'm not sure it maybe does), means i'd have to do anyways
22:04:12<klea>hexa-: would it be possible to be evilish and define 'fake' derivations that are just the hash of the abi somehow, i guess not since of how nix is made
22:05:15<hexa->the derivation hash can certainly be bruteforced without brain/compute some day
22:05:26<hexa->s/without/with/
22:08:56<@JAA>Why aren't the binaries separated from the metadata? When Bash is updated, nearly no other package that depends on it actually changes since it's just used as a script interpreter in the vast majority of cases.
22:09:56<@JAA>So you'd have new versions that reference the new Bash version in the metadata but still point to the same binary in that case.
22:10:06<klea>nix expression -> derivation -> binary
22:10:08<@JAA>Bonus points if you do rebuild the binaries but end up with identical output due to reproducible builds. :-)
22:11:28<klea>"#!/nix/store/cl2gkgnh26mmpka81pc2g5bzjfrili92-bash-5.3p3/bin/bash" != "#!/nix/store/rlq03x4cwf8zn73hxaxnx0zn5q9kifls-bash-5.3p3/bin/bash"
22:12:07<@JAA>Hmm, yeah
22:15:43NF885 (NF885) joins
22:22:56etnguyen03 (etnguyen03) joins
22:25:24NF885 quits [Client Quit]
22:38:19Webuser921711 joins
22:38:35Webuser921711 quits [Client Quit]
22:40:57etnguyen03 quits [Client Quit]
22:45:26<h2ibot>Nintendofan885 edited Radio Free Asia (+247, add no new news delivery): https://wiki.archiveteam.org/?diff=58213&oldid=56457
22:46:10DogDisco leaves [Ooops, wrong browser tab.]
22:59:58<hexa->https://discourse.nixos.org/t/nixpkgs-core-team-update-2025-11-30-github-scaling-issues/72709
23:03:16ericgallager quits [Quit: This computer has gone to sleep]
23:08:59nexussfan (nexussfan) joins
23:23:25etnguyen03 (etnguyen03) joins
23:27:13nathang2184 quits [Ping timeout: 272 seconds]
23:41:46HackMii quits [Remote host closed the connection]
23:42:05HackMii (hacktheplanet) joins
23:44:40etnguyen03 quits [Client Quit]
23:53:04etnguyen03 (etnguyen03) joins