00:00:07<klea>cruller: should we also write about the things for tomorrow and next day (ie 2026-01-01)?
00:01:46<@JAA>klea: Yeah, see recent discussion about section transclusions. I haven't looked at that closer yet though.
00:01:52<klea>> 2026-01-01: Pair.com mailing lists (PairLists) will be shut down. While this has not yet been announced on their website, this has been emailed to list managers. https://coco3.org/TCCN/TCCN-432.html https://pairlist7.pair.net/pipermail/techtoolslist/2025q3/003870.html
00:02:32<klea>is there some way to get the list of all lists' names?, based on https://pairlist7.pair.net/pipermail/techtoolslist/, i suppose other lists would also have indexes that can be ABed
00:04:10lunik1 joins
00:05:21<cruller>klea: At the very least, I will add a note regarding the canceled and postponed ones.
00:05:33<klea>good
00:06:31<klea>https://en.wikipedia.org/wiki/Help:Labeled_section_transclusion
00:07:05<klea>JAA: i was thinking of doing the inverse, but yeah it seems like a fine idea, making a bunch of labels and then smaller pages that translcude the deathwatch using those labels
00:07:18<cruller>That aside, I believe Deathwatch should have an archiving status field. However, it shouldn't be so resource-intensive to input that it hinders archiving.
00:07:47<hexagonwin>arkiver is ktoon finished? if 'series:' items are HTML, doesn't it mean the latest/last downloads shouldn't be 'series:' since they always discover new stuff (episode/image)?
00:07:55<@JAA>The thing is more that it clutters the page even further.
00:08:09<@JAA>Not that the current approach is good, mind you.
00:08:19<hexagonwin>i'm just slightly worried due to its small size, and we have about 15hrs left till deadline
00:08:49<nicolas17>didn't we talk about turning deathwatch into a ticket system once? :P
00:09:31<klea>inb4 we start running phorge
00:09:45<klea>nicolas17: if you have time could you link me to irclogs about it?
00:10:33<klea>JAA: <section begin=dying-2025-01 />¨CONTENT¨<section end=dying-2025-01 /> doesn't look so bad
00:10:54<@JAA>nicolas17: We talked about that kind of thing, but as an additional thing, not a replacement, I think.
00:11:19<klea>i don't know how we could do to let users easily edit those sections, i was thinking of doing the inverse making deathwatch as small as possible and linking outwards
00:11:43<klea>then those sections of the deathwatch per year would be smaller, even if it'd make moving things between sections slightly annoying.
00:12:22<klea>we could do per year and have the section tag thingies per month (and also add to some specific days if there's too many entries)
00:12:28<@JAA>If that moving were a rare task, whatever, but it's definitely not (and should be more frequent than we do).
00:12:35<nicolas17>maybe leave Deathwatch as it is, but create a new page for every site and add more info there, how hard could it be (:
00:12:54<@JAA>I mean, Deathwatch already links to the pages when they exist.
00:13:56<klea>we can add more section labels for dates, add more spaces for when editing the wikitext (is there a way to make those not show?) and have a section of machine generated transclusion pages for easier viewing
00:14:07<klea>but that still clutters it a bit much.
00:14:08Dada joins
00:14:18<@JAA>Keeping editing simple is important, too.
00:14:39<@JAA>As in, random people adding things that are shutting down.
00:15:04Dada quits [Remote host closed the connection]
00:16:19<@OrIdow6>Yeah
00:18:58<@OrIdow6>I do like the wiki being a big public notepad without understanding much machinery needed to edit
00:19:55<klea>that's why i said putting lots of spaces (i meant newlines), and maybe comments to make it clear how to add stuff easily
00:23:02<cruller>13. https://www.greun.nu/ — This must be one of "some that are still unfinished but can be completed even now." Just 25 pages.
00:23:07<cruller>14. https://community.ns.nl/ — Saved with AB on 2025-06-21. It has been offline from December 15.
00:23:12<cruller>15. https://www.myktoon.com/ — Saved with DPoS.
00:23:26<cruller>Ex1. https://arca.live/ https://refsheet.net/ https://horaro.org/ are still online.
00:25:39<cruller>Sorry for sending so many messages :P
00:29:47<klea>cruller: don't worry, the messages are actually usefull :)
00:36:44<DigitalDragons>Maybe issues in a repo on the gitea is a nice simple ticketing system? Then you can either make an issue as you add something to deathwatch or someone else can go back and make an issue later
00:36:52<DigitalDragons>(is the gitea open registration?)
00:39:43<@OrIdow6>cruller: It's tradition - https://irclogs.archivete.am/archiveteam-bs/2024-12-16#laf550d06
00:41:38<@OrIdow6>I feel like we need a wiki page summarizing discussion of the gitea idea
00:43:11<klea>DigitalDragons: i believe gitea's not configured as open registration
00:43:12etnguyen03 quits [Client Quit]
00:44:02<DigitalDragons>right, okay
00:44:11<DigitalDragons>Phorge or something would be cool but someone would have to set that up and I think people are busy
00:44:45Guest58 quits [Read error: Connection reset by peer]
00:44:57klea kindly asks busy for a little small container to setup a lamp stack
00:45:27<@OrIdow6>Previous discussions on this: https://irclogs.archivete.am/archiveteam-bs/2021-06-05#lf2101768 https://irclogs.archivete.am/archiveteam-bs/2022-08-27#l5344ff5e https://irclogs.archivete.am/archiveteam-bs/2024-11-06#la3a5dcb3
00:45:56<klea>OrIdow6: thanks!
00:46:30<@OrIdow6>Interesting how it was originally merged with the idea of scanning social media for shutdown discussion
00:47:57<klea>https://irclogs.archivete.am/archiveteam-bs/2024-11-06#l2fe6fe7a highligthing **no one wanted to host it**, i wonder, are people trying to avoid maintenance?
00:49:30<nicolas17>tbh I think we should try gitlab.com or something just to experiment with the ticket workflow, rather than bikeshedding what exact software to use or who will host it
00:49:40<nicolas17>and either way it can wait until january :D
00:50:32<klea>or next year :p
00:50:47klea sees opp
00:50:50<klea>sorry
00:52:52<eggdrop>[remind] OrIdow6: add realkalos to hoaxes
00:53:06cyanbox joins
00:53:12<@OrIdow6>eggdrop: What does that mean, how long ago did I ask for this remind
00:53:34<nicolas17>dec 16
00:53:40<klea>OrIdow6: https://irclogs.archivete.am/archiveteam-bs/2025-12-17#l641ab70f
00:53:42<@OrIdow6>Whatever
00:53:42<@OrIdow6>!remindme 2w add realkalos to hoaxes
00:53:43<eggdrop>[remind] ok, i'll remind you at 2026-01-14T00:53:42Z
00:54:03<klea>lol
00:54:12<nicolas17>procrastination++
00:54:12<eggdrop>[karma] 'procrastination' now has 79 karma!
00:54:25<klea>procrastination++
00:54:26<eggdrop>[karma] 'procrastination' now has 80 karma!
00:55:25<@OrIdow6>I'm evidently on IRC around the same time
00:56:10<klea>[remind] OrIdow6 that is a request by yourself to add realkalos (what is that?) to https://wiki.archiveteam.org/index.php/Shutdown_rumors,_hoaxes,_and_scares
01:10:42<@JAA>OrIdow6: Yeah, that general plan is still on the menu. There were some blockers that were only very recently sorted out.
01:11:43etnguyen03 (etnguyen03) joins
01:22:10<h2ibot>DigitalDragon created Better Tracking for Deathwatch (+1671, Created page with "''See past discussions on…): https://wiki.archiveteam.org/?title=Better%20Tracking%20for%20Deathwatch
01:22:55<DigitalDragons>I did my best to summarize but might've missed some stuff
01:34:11<h2ibot>Cruller edited Deathwatch (+373, Update regarding CreativeLive and the Shogi…): https://wiki.archiveteam.org/?diff=59058&oldid=59030
02:04:21nexussfan quits [Quit: Konversation terminated!]
02:43:32Island joins
02:59:23<h2ibot>PaulWise edited Internet Archive/Save Page Now (+198, add more SPN blocklist entries): https://wiki.archiveteam.org/?diff=59059&oldid=58724
03:23:53<tzt>Baker & Taylor, a library services company, will shut down 2026, a lot of library catalogs rely on it for book metadata, it looks like baker-taylor.com was saved in AB but contentcafe2.btol.com, which has the book metadata has not been archived. The SSL certificate for baker-taylor.com expired 12 days ago and has not been renewed so it seems that shutdown is immninent.
03:42:00<tzt>The service uses ASP.NET Web Forms, with a POST request link on each of the pages with book data, but it can be reformatted to GET. Here is an example URL: https://contentcafe2.btol. com/ContentCafeClient/ContentCafe.aspx?UserID=ebsco-test&Password=ebsco-test&ItemKey=0679405593
03:42:12etnguyen03 quits [Client Quit]
03:42:45etnguyen03 (etnguyen03) joins
03:43:09<tzt>The ItemKey is the book ISBN
03:46:32etnguyen03 quits [Remote host closed the connection]
03:56:16<nicolas17>yikes
04:04:09<nulldata>Do we have a list of ISBNs?
04:29:28Wohlstand (Wohlstand) joins
04:36:53<@arkiver>hexagonwin: i think it's finished... we went through the user uploaded stuff, since as you mentioned the other comics seemed to be behind a wall
04:37:34DogsRNice quits [Read error: Connection reset by peer]
04:38:20<@arkiver>justauser: can https://transfer.archivete.am/aqSnd/pair.com_pair.net_pairlist.net_ddg.txt simply go in ArchiveBot?
04:38:20<eggdrop>inline (for browser viewing): https://transfer.archivete.am/inline/aqSnd/pair.com_pair.net_pairlist.net_ddg.txt
04:38:32<@arkiver>and https://transfer.archivete.am/dlfpw/pair.com_pair.net_pairlist.net.cdx.zst
04:39:17<@arkiver>nicolas17: klea: you can use https://archive.fart.website/archivebot/viewer/ to see if at least something ran for a site
04:41:24<@arkiver>tzt: is there a more precise deadline than "2026"?
04:48:55<@OrIdow6>DigitalDragons: Thanks!
04:53:39<h2ibot>OrIdow6 edited Better Tracking for Deathwatch (+422, On Mediawiki extensions): https://wiki.archiveteam.org/?diff=59060&oldid=59057
04:55:16<@arkiver>good a web page is being made on this :)
04:56:00<@arkiver>i think it is important to keep things simple, so anyone would be able to add an entry without requiring technical knowledge
04:56:09<@arkiver>or too many accounts in various places
05:00:41<@JAA>https://transfer.archivete.am/dlfpw/pair.com_pair.net_pairlist.net.cdx.zst is surts, so definitely not AB-able.
05:05:17<@arkiver>interesting, why format it like that :P
05:05:52<@arkiver>nearly 500k URLs
05:06:05<@arkiver>may be doable with AB in time
05:06:13<@arkiver>with high concurrency
05:07:57<@JAA>Probably took the first field from the CDX API response instead of the original URL.
05:11:49<@arkiver>ah didn't know it was taken from the CDX API
05:17:49<@JAA>And I had somehow missed the context of this disappearing.
05:18:41<@JAA>Looking into throwing these into AB.
05:22:43<h2ibot>PaulWise edited Obstacles (+61, Vercel Security Checkpoint, Deflect): https://wiki.archiveteam.org/?diff=59061&oldid=58626
05:23:43<h2ibot>JustAnotherArchivist edited Deathwatch (+161, /* 2026 */ Add PE-Community.eu): https://wiki.archiveteam.org/?diff=59062&oldid=59058
05:30:50<hexagonwin>arkiver: i see... it does seem like *some* non-user-uploaded comics are still public, like https://v2.myktoon.com/web/works/list.kt?worksseq=3
05:31:44<hexagonwin>seems like stuff linked on https://v2.myktoon.com/web/homescreen/box_webtoon.kt ("박스오피스" on top navbar) is largely not paywalled?
05:34:32SootBector quits [Remote host closed the connection]
05:35:39SootBector (SootBector) joins
05:37:11<@JAA>Ugh, there's duplication, e.g. https://pairlist2.pair.net/pipermail/wolfdev/ == https://two.pairlist.net/pipermail/wolfdev/
05:48:43<tzt>tzt: it appears that Content Cafe has been acquired according to this post but it will be transitioned to "LibraryOne" https://old.reddit.com/r/librarians/comments/1pq6fog/baker_and_taylor_not_dead_yet_well_at_least_part/
05:48:49<tzt>arkiver:
05:59:47Webuser041704 joins
06:07:51Webuser041704 quits [Client Quit]
06:13:18<@JAA>Oh
06:13:45<@JAA>I think I found a way to get a complete list of the mailing lists.
06:15:14SootBector quits [Remote host closed the connection]
06:16:21SootBector (SootBector) joins
06:21:13<pabs>JAA++
06:21:14<eggdrop>[karma] 'JAA' now has 326 karma!
06:28:59gosc joins
06:34:53<h2ibot>PaulWise edited Better Tracking for Deathwatch (+440, custom software idea): https://wiki.archiveteam.org/?diff=59063&oldid=59060
06:45:29<gosc>archivebot can handle 700k urls right?
06:47:09<pabs>yes, could take a while though
06:47:27<gosc>oh nice
06:47:35<pabs>if you also need fast, DPoS is the only option
06:47:43<gosc>I see
06:47:57<pokechu22>or split the list into several and do several archivebot jobs
06:48:03<pabs>or qwarc I guess
07:04:58<h2ibot>PaulWise edited In The Media (+124, Honey fraud video): https://wiki.archiveteam.org/?diff=59064&oldid=58985
07:14:51Island quits [Read error: Connection reset by peer]
07:16:16<@arkiver>qwarc may be a good fit in this case
07:18:35<@JAA>Which case?
07:27:32<@arkiver>to get a copy of pair.com lists
07:27:37<@arkiver>JAA: ^
07:29:16driib97 quits [Quit: Ping timeout (120 seconds)]
07:29:51<@arkiver>cruller: from what you checked - do you think there are any that need a custom project?
07:30:13driib97 (driib) joins
07:30:24Island joins
07:36:44driib97 quits [Ping timeout: 256 seconds]
07:40:47<@JAA>arkiver: Not a terrible fit, but qwarc isn't really good at generic recursion.
07:44:35<cruller>arkiver: I've only checked whether starting AB now would finish it today, but AFAIK there aren't.
08:04:07<@JAA>It appears that pairlistN.pair.net is the canonical location for the lists. The {one,two,...}.pairlist.net servers redirect there on some URLs.
08:09:32<cruller>https://digizeitschriften.de/id/{id} won't load with noscript, but since there are no POST requests or complex processing, I think creating a URL and doing AB should suffice. (If you want to archive each document's metadata)
08:10:59<cruller>s/URL/URL list/
08:13:23<cruller>However, the metadata for each document may be available from another database if its ID is known.
08:17:48<cruller>Oh, digizeitschriften seems to have just gone offline... nvm
08:23:33tzt quits [Ping timeout: 272 seconds]
08:25:14tzt (tzt) joins
08:31:33Island quits [Read error: Connection reset by peer]
08:34:04beastbg8_ joins
08:38:07beastbg8__ quits [Ping timeout: 272 seconds]
09:16:26<@JAA>AB jobs for pairlistN.pair.net are running. One !ao < job for the /mailman/listinfo/x and one !a < job per host (1 through 10) for /pipermail/x.
09:17:10<@JAA>The CDX API data has a lot of noise, but I left everything that was workable in the list, so that gets some 404s.
09:20:33APOLLO03 quits [Ping timeout: 272 seconds]
09:25:00lennier2 joins
09:25:36APOLLO03 joins
09:27:14lennier2_ quits [Ping timeout: 256 seconds]
09:35:07nathang2184 quits [Ping timeout: 272 seconds]
09:42:48nathang2184 joins
09:53:47<cruller>I've also checked the 6 things on 2026-01-01. It seems none have been archived yet except for channel attitude.com.
09:57:43<@JAA>PairLists and PE-Community are both running through AB.
09:59:20<cruller>Yeah, I forgot to check the dashboard...
10:03:36<cruller> I just saw a job for quantum-mirror.hu. Thanks.
10:07:13<cruller>When running noscript, https://www.pe-community.eu/ displays the message “JavaScript ist deaktiviert. Für eine bessere Darstellung aktiviere bitte JavaScript in deinem Browser, bevor du fortfährst.” However, at first glance, it seems to be working fine.
10:12:19<@JAA>Yeah, XenForo works fine without JS.
10:16:08Dada joins
10:22:12Wohlstand quits [Quit: Wohlstand]
10:32:54archiveDrill quits [Quit: The Lounge - https://thelounge.chat]
10:35:41gosc quits [Quit: Leaving]
10:38:26<klea>pabs: can you check if the SPN blocklist is for /generate_204 directly, iirc google has other domains that also generate 204s
10:38:33<h2ibot>Cruller edited Deathwatch (+184, The Berean Test cancelled its planned shutdown.): https://wiki.archiveteam.org/?diff=59065&oldid=59062
11:01:04<klea>i'm going to try to setup a phorge instance to toy with it, if it becomes more production desired use, i'll probably ask for a subdomain for it, so it's not relying on a third party i'm not entirely sure i trust to keep paying a domain :)
11:14:16<pabs>not easily, I only saw the error in my SPN email response
11:19:59<klea>thanks
11:25:54<cruller>https://support.google.com/chrome/a/answer/6334001 These "generate_204"s are also blocked.
11:34:55<cruller>Ah yes, generate_204 in any domain or directory is blocked. (Even if it's example.com)
11:35:53<cruller>It's a very simple blocking rule.
11:40:41<h2ibot>Cruller edited Internet Archive/Save Page Now (-27, /* Blocks */ Any generate_204 is blocked): https://wiki.archiveteam.org/?diff=59066&oldid=59059
11:42:06<cruller>Incidentally, https://example.com/generate_204/a.txt isn't blocked.
11:43:32PaiMei quits [Quit: Ping timeout (120 seconds)]
11:48:27PaiMei (PaiMei) joins
11:50:05Dada quits [Remote host closed the connection]
11:54:54croissant_ joins
11:57:37croissant quits [Ping timeout: 272 seconds]
12:00:02Bleo182600722719623455222 quits [Quit: The Lounge - https://thelounge.chat]
12:02:45Bleo182600722719623455222 joins
12:03:26lennier2_ joins
12:06:29lennier2 quits [Ping timeout: 272 seconds]
12:10:51Wohlstand (Wohlstand) joins
12:19:21T31M quits [Quit: ZNC - https://znc.in]
12:21:13T31M joins
12:26:48<h2ibot>Manu edited Discourse/archived (+93, Queued forums.fast.ai): https://wiki.archiveteam.org/?diff=59067&oldid=59056
12:29:27<c3manu>lucky coincidence, https://forum.posit.co/ has a notice at the top about sunsetting bookdown.org
12:29:48<h2ibot>Manu edited Discourse/archived (+93, Queued forum.posit.co): https://wiki.archiveteam.org/?diff=59068&oldid=59067
12:31:50Dada joins
12:33:01<c3manu>https://posit.co/blog/bookdown-org-sunset/
12:37:49<h2ibot>Manu edited Deathwatch (+192, 2027: bookdown.org): https://wiki.archiveteam.org/?diff=59069&oldid=59065
12:38:04Dada quits [Remote host closed the connection]
12:38:28<c3manu>it’s only taken down end of Jan 2027, but the source files won’t be available starting Jan 31 in 2026 already
12:38:56<c3manu>also some books listed in the archive https://bookdown.org/home/archive/ are hosted on custom domains, like https://r-graphics.org/ for example
12:39:31<c3manu>not sure whether the source files are public or only accessible to the author/uploader
12:40:32<c3manu>^ does it make sense to create small wiki pages for as little information as that?
12:42:30Dada joins
13:09:49TheEnbyperor quits [Ping timeout: 272 seconds]
13:10:54<h2ibot>Manu edited Discourse (+385, Known Victims: Add discussions.udacity.com): https://wiki.archiveteam.org/?diff=59070&oldid=58834
13:11:04TheEnbyperor_ quits [Ping timeout: 256 seconds]
13:11:54<h2ibot>Manu edited Discourse/active (-62, Udacity Discussion Board no longer active): https://wiki.archiveteam.org/?diff=59071&oldid=58835
13:13:54<h2ibot>Manu edited Discourse/archived (+99, Queued forum.torproject.org): https://wiki.archiveteam.org/?diff=59072&oldid=59068
13:16:55<h2ibot>Manu edited Discourse/archived (+95, Queued devforum.zoom.us): https://wiki.archiveteam.org/?diff=59073&oldid=59072
13:22:37TheEnbyperor joins
13:25:37TheEnbyperor_ (TheEnbyperor) joins
13:31:01<h2ibot>Manu edited Discourse/archived (+100, Queued community.toradex.com): https://wiki.archiveteam.org/?diff=59074&oldid=59073
13:38:23sec^nd quits [Remote host closed the connection]
13:38:48sec^nd (second) joins
13:46:55TheEnbyperor quits [Read error: error:0A000139:SSL routines::record layer failure]
13:48:27TheEnbyperor_ quits [Ping timeout: 272 seconds]
13:50:10nine quits [Ping timeout: 256 seconds]
13:52:16nine joins
13:52:16nine quits [Changing host]
13:52:16nine (nine) joins
13:52:19TheEnbyperor (TheEnbyperor) joins
13:55:03TheEnbyperor_ joins
14:01:52gosc joins
14:02:33<gosc>it's normal for some wayback pages to be excluded right? I saved this page three times and 2/3 of the captures have vanished from wayback: https://madoka-magica-cafe-girlsparty2025.theme-cafe.jp
14:02:53<gosc>I saved it sometime in dec, then on december 23, both of those captures are gone now
14:03:50<gosc>dec 26* my bad
14:24:19<klea>gosc: does it explicitly say it's excluded?, if not, it's probably an indexing issue
14:24:25<klea>also, #internetarchive
14:24:45<gosc>oh okay; to both messages lol
14:24:57<gosc>yeah, it doesn't say excluded
14:28:19Dada quits [Remote host closed the connection]
14:28:31Dada joins
14:34:42gosc quits [Client Quit]
14:44:10nathang2184 quits [Quit: Ping timeout (120 seconds)]
14:44:25nathang2184 joins
14:45:02Dada quits [Remote host closed the connection]
14:59:24corentin quits [Quit: The Lounge - https://thelounge.chat]
14:59:33corentin joins
15:06:33<nstrom|m>fyi arkiver I think we can shut down ktoon archiver, just getting 302s and redirects to shutdown notice now
15:14:47corentin4 joins
15:16:52corentin quits [Ping timeout: 256 seconds]
15:16:52corentin4 is now known as corentin
15:18:23nexussfan (nexussfan) joins
15:21:16<klea>lol, phorge seems to have full fledged code review, and wikis and lots of stuff, not sure if that could be helpfull or not
15:24:01<klea>you can disable most stuff i believe, but i'm trying to figure out how to bork the files part, as we already have transfer.archiveteam.org
15:24:03<klea>aaa
15:24:07<klea>transfer.archivete.am
15:25:13<klea>POST /file/upload/ oh, i guess just bork that endpoint via reverse proxy
16:19:25<h2ibot>OrIdow6 edited Better Tracking for Deathwatch (+464, Move MW-with-extensions to its own sections, a…): https://wiki.archiveteam.org/?diff=59075&oldid=59063
16:26:34<@OrIdow6>klea: Surprised there's no cleaner way to disable them
16:26:49<klea>OrIdow6: most things there's a cleaner way but not for files
16:27:29<klea>> This application is required and cannot be disabled.
16:33:02<@OrIdow6>I guess it's used internally for image uploads and the like?
16:33:46<klea>ye
16:34:02<klea>OrIdow6: if you want to play with it: http://linkbird.iwnp.org:9080/
16:36:03<klea>btw, that's a test instance running on my laptop, so data will likely be deleted if/when i decide to move it to more prod like setup (i'd need a container somewhere preferably)
16:36:16<kiska>At some point I am going to migrate my influxdb machine to another thing, so those who are using it for the graphs will experience some period of no data cause I am moving the database
16:36:30<klea>ack
16:50:48<TheTechRobo>Phorge does indeed seem pretty heavyweight for what we'd be using it for. I'm not really an important figure in AT, so take this with a grain of salt, but I can't see there being much use of the additional features that an issue tracker would provide. Most discussion is going to be on IRC anyway, so all the discussion features will probably go
16:50:48<TheTechRobo>unused
16:51:10cyanbox quits [Read error: Connection reset by peer]
16:51:45<@OrIdow6>klea: I am example@example.com
16:52:06klea agrees with TheTechRobo
16:52:09<@OrIdow6>TheTechRobo: Yeah "heavy" is my impression to browsing around this
16:52:29<@OrIdow6>I could see everything whatsoever being integrated into this but that seems like way further than we're talking
16:53:04<TheTechRobo>about Phorge specifically, there's a lot of clicks to get around to basic functionality we'd need like "Open tasks", and although we could probably fix that with custom navigation etc, *starting out* a project with duct tape is probably not a fantastic idea :P
16:53:11<@OrIdow6>And having a single service run by a single person for everything seems risky in a somewhat decentralized organization
16:53:38<TheTechRobo>Tbf, that's currently the wiki, but yeah, reducing the centralization is a big factor
16:53:57<TheTechRobo>s/reducing/not increasing/
16:54:06croissant_ is now known as croissant
16:54:38@OrIdow6 laughs at the nick change
16:54:38<klea>what wikimedia seems to do is make custom forms: https://phabricator.wikimedia.org/ shows links to forms which are somewhat limited
16:55:23<klea>i agree at not increasing centralization
16:55:46<klea>tho afaik DPoS relies on another single server, h2i is another single server, AB is another single server
16:56:04<TheTechRobo>I think if we're going to use a forge, it should be the Gitea we're already using (and open up registration there), *or* we should move from Gitea to Phorge. But I'm not sure we really need a forge
16:56:28<klea>yea
16:56:33<klea>we could disable the phorge feature
16:56:58<klea>s/phorge/forge/
16:57:00<klea>aa
16:57:02<TheTechRobo>To fix the "new accounts" issue, it'd be cool if the wiki could be integrated so you log in with your wiki account
16:58:00<klea>i believe you can but from what i saw on the WMF phabricator, the first time you have to input an email if you haven't configured one on the wiki
16:58:07<klea>well, and if you have too
16:58:13<klea>but it's just filled in iirc
16:58:13<TheTechRobo>klea: Sorry, by "not sure we really need a forge" I should have said "not sure we really need a fully-fledged issue tracker"
16:58:23<klea>yeah true
16:58:37<klea>unless we want to do everything in phorge but that's centralizing AT to a single service :(
16:58:44<TheTechRobo>Yeah
16:58:50<@OrIdow6>One thing it absolutely needs is custom fields
16:58:56<klea>i believe you can add
17:00:11<klea>https://we.phorge.it/book/phorge/article/custom_fields/
17:05:02<TheTechRobo>My current preference is the Semantic MediaWiki or Cargo approach. Nothing new to host, no new accounts, everything's in a similar place, and we can (presumably? I've never used those extensions before) make pages with custom queries so people can have their own dashboards if they want to. OTOH, I can see there being issues with having one wiki
17:05:02<TheTechRobo>page per item, and I don't even know who has server access to the wiki (is it just Jason Scott?)
17:07:36<TheTechRobo>Re assigning people to an issue, isn't that kind of thing what these extensions are designed for? to be able to put a schema on a set of wiki pages and run queries on it? Or am I misunderstanding?
17:07:38<klea>TheTechRobo: from what i understand JAA has access to the wiki, since i asked in #wikiteam to add dumps that only contain the last revision and they seemed to do it
17:09:40<klea>i also believe the files thing is used internally by phorge itself to store it's own image files: http://linkbird.iwnp.org:9080/F1
17:16:22<@JAA>Yeah, I'm not a huge fan of Phorge's interface, but then again, I haven't used it much either, and Bugzilla's UI only grew on me after I did (but is *definitely* overkill for here).
17:17:49<@JAA>That said, we have Gitea, which is to be improved very soon now that the blockers are gone. We already need and use that anyway, and its issue tracking is probably sufficient for this use case.
17:18:27<@JAA>TheTechRobo, klea: Correct, I have full access to everything wiki-related.
17:18:55<TheTechRobo>Would Gitea be made open-registration then?
17:24:34<h2ibot>Manu edited Anubis/uncategorized (+27, git.hacknology.de deploys Anubis): https://wiki.archiveteam.org/?diff=59076&oldid=58267
17:29:53<@JAA>TheTechRobo: Details TBD; we wouldn't want to invite spammers. But yes-ish.
17:35:47<@OrIdow6>On https://wiki.archiveteam.org/index.php/Better_Tracking_for_Deathwatch, alright if I reclassify Phorge as #1? At least my takeaway here was that there's a difference between dedicated issue trackers and software that do more things
17:36:18<@OrIdow6>JAA: Why is Bugzilla overkill? Haven't used it too much
17:36:35<@JAA>Having to run an additional thing is a significant difference.
17:41:48<@OrIdow6>Any big issues with the interface/the like?
17:41:50<@JAA>The main features on Bugzilla that come to mind as being overkill is the classification/product/component system and the numerous fields you can set.
17:42:12<@JAA>Not sure if you can configure it to hide all of that though.
17:44:23<@JAA>I'd rather thing about it the other way around: is there something we need that the Gitea/Forgejo issue tracker *can't* do?
17:44:28<@JAA>s/thing/think/
18:06:13<klea>so i'll kill the test instance then now that we know it's not needed
18:07:58ScenarioPlanet quits [Quit: meow meowy meow]
18:07:58Pedrosso quits [Quit: Leaving]
18:07:58TheTechRobo quits [Quit: Leave message goes here]
18:08:05<@JAA>I mean, the question whether it offers something additional that we need is still open. I don't think there is anything, but maybe others disagree.
18:10:08<klea>a i did it too soon.
18:13:18<klea>gitea gives calendars?
18:13:37<klea>but tho it's not very usefull
18:16:01<klea>it has a feature to make #urlteam happy, https://phabricator.wikimedia.org/phurl/
18:27:58<@JAA>Not sure about a calendar, but due dates exist (and can be sorted by), which is probably sufficient?
18:29:56<klea>yeah
18:44:39<@arkiver>nstrom|m: thank you, paused it
18:49:56Pedrosso joins
18:49:58ScenarioPlanet (ScenarioPlanet) joins
18:50:12midou quits [Remote host closed the connection]
18:50:15midou joins
18:50:19TheTechRobo (TheTechRobo) joins
19:00:51<@OrIdow6>Maybe we should add a "wishlist" of stuff to the wiki page
19:01:03<@OrIdow6>Like, fields to be tracked, notifications that would be nice to have etc
19:01:05<@OrIdow6>THen pare that down
19:02:43<klea>yeah
19:03:16<klea>i'm trying to think of things gitea doesn't have, are issues that are childs of other issues implemented?
19:17:32<@OrIdow6>*does* Gitea/Forejo do custom fields?
19:18:00<@OrIdow6>I'm finding stuff that talks about issue templates but some people complaining that that doesn't work as well as Jira custom fields. But haven't used Jira
19:22:12<klea>https://codeberg.org/forgejo/discussions/issues/368 V
19:22:14<klea>https://github.com/go-gitea/gitea/issues/8665
19:25:20<nicolas17>pls archive https://news.ycombinator.com/item?id=46443077 post got flagged and may be deleted
19:25:56<nicolas17>I'm afk
19:27:21<@OrIdow6>nicolas17: Ran it with a quick !ao
19:28:02<nicolas17>thx
19:46:50leo60228 quits [Read error: Connection reset by peer]
19:46:53leo60228 (leo60228) joins
20:08:01<h2ibot>Pokechu22 edited Mailman/2 (+87, /* Not yet archived */ 2 from https://w1.fi/): https://wiki.archiveteam.org/?diff=59077&oldid=58251
20:24:03<h2ibot>KleaBot edited Discourse/archived (+0, Reordered websites): https://wiki.archiveteam.org/?diff=59078&oldid=59074
20:24:04<h2ibot>KleaBot edited Main Page/In The Media (-39, Updated from [[In The Media]]): https://wiki.archiveteam.org/?diff=59079&oldid=59024
20:24:19<klea>ok now it only reordered urls
20:24:21<klea>good bot
20:45:35<c3manu>ugh
20:46:53DogsRNice joins
20:47:23<c3manu>is it really that important to sort those forums alphabetically for each day? what do other people think?
20:49:42<c3manu>i don’t want to be the only voice in the room on that, but i’m feeling like someone else is trying to clean up my room (someone who’s not using it themselves)
21:15:19<c3manu>JAA: apparently the German govt is trying to move towards a common '.gov.de' domain scheme, making it easier to see which wegbsites actually are government websites, and which aren’t. they’re gonna move slow, but i’d bet a at least a few of them will be scrapped and/or rebuilt at that opportunity
21:15:43<c3manu>JAA: via https://fragdenstaat.de/artikel/exklusiv/2025/12/geheimsache-domains/ and it’s many links, like https://bmds.bund.de/service/digitale-dachmarke
21:15:52<c3manu>only skimmed it myself so far
21:17:24lukash984 joins
21:37:39<@JAA>c3manu: Oh, I like that, but yeah, we should probably grab everything before that happens then.
21:38:04<masterx244|m>related: https://media.ccc.de/v/39c3-verlorene-domains-offene-turen-was-alte-behordendomains-verraten (talk has a english audio track, too. powered by volunteer translators at the conference itself)
21:39:50<c3manu>c3lingo++
21:39:51<eggdrop>[karma] 'c3lingo' now has 1 karma!
21:40:10<c3manu>haven’t watched it myself yet. maybe they have a list or something ^^
21:40:36<FireFly>c3manu: nice they're finally doing that
21:40:49<FireFly>now I only need sweden to follow suit >.>
21:40:55<c3manu>the decision seems to be from some time in 2024 ^^
21:41:33<c3manu>March 2024: https://www.digitale-verwaltung.de/Webs/DV/DE/aktuelles-service/digitale_dachmarke/digitale_dachmarke-node.html
21:55:18<klea>ig i should manually look for which pages where updated and when the bot ran and only run the bot every week or so
21:57:21Webuser218223 joins
21:57:43Webuser218223 quits [Client Quit]
22:01:40<c3manu>klea: i really don’t mean to come across as mean or anything, but that would make it even worse ^^ now it’s not just putting things another place than where i left it, but also does so at random times
22:03:35<c3manu>klea: why are you reording them in the first place? was someone having trouble finding something in a list or sth like that?
22:05:27<klea>c3manu: i'll remove that file, i was sorting them to keep them ordered, i thought it was a good idea to do it similar to how wbmexclusions is sorte
22:08:51<c3manu>klea: that was meant as a genuine, open question. if it serves a purpose it could be worth to keep reordering it regardless of what i think about it ^^
22:10:28<klea>i also don't mean to come off as mean, from what i remember i think i only made it because i thought, if Wayback Machine's exclusions' lists are sorted why not also order other lists from the wiki
22:21:20Island joins