HomeSearchPrevious dayNext day

00:02:34Guest58 quits [Quit: My Mac has gone to sleep. ZZZzzz…]
00:03:27Guest58 joins
00:03:45Guest58 quits [Client Quit]
00:25:28Guest58 joins
00:43:38Guest58 quits [Client Quit]
00:44:32Guest58 joins
01:20:29Guest58_ joins
01:21:19Guest58 quits [Ping timeout: 272 seconds]
01:38:35irisfreckles1 joins
02:06:40Guest58_ quits [Client Quit]
02:17:41Guest58 joins
02:56:57irisfreckles1 quits [Read error: Connection reset by peer]
03:29:37Guest58 quits [Client Quit]
03:59:26cyanbox_ quits [Read error: Connection reset by peer]
04:30:33Guest58 joins
04:39:53cyanbox joins
05:05:08n9nes quits [Ping timeout: 256 seconds]
05:07:06n9nes joins
05:15:11sec^nd quits [Remote host closed the connection]
05:15:23sec^nd (second) joins
05:49:37nexussfan quits [Quit: Konversation terminated!]
06:09:35fuzzy80211 quits [Read error: Connection reset by peer]
06:10:43fuzzy80211 (fuzzy80211) joins
06:10:47fuzzy80211 quits [Excess Flood]
06:12:54fuzzy80211 (fuzzy80211) joins
07:08:36<@arkiver>yeah, little project selection coming up :) will be very simple with no major changes on the tracker side
07:09:06<@arkiver>something like PROJACTA=0.7;PROJECTB=0.1;PROJECTC=0.2, then it choses one of these according to the fractions.
07:09:20<@arkiver>it will then make a decision again if the config changes, so it will not be switching all the time
09:41:07mrminemeet_ joins
09:42:17mrminemeet quits [Ping timeout: 272 seconds]
09:48:28@rewby quits [Ping timeout: 256 seconds]
09:50:30rewby (rewby) joins
09:50:30@ChanServ sets mode: +o rewby
09:55:29fuzzy80211 quits [Read error: Connection reset by peer]
09:56:25fuzzy80211 (fuzzy80211) joins
09:56:32fuzzy80211 quits [Excess Flood]
09:57:30fuzzy80211 (fuzzy80211) joins
09:57:32fuzzy80211 quits [Excess Flood]
09:58:35fuzzy80211 (fuzzy80211) joins
09:59:39irisfreckles1 joins
11:16:10Shard11 quits [Quit: Im doing something rq. Il brb]
12:00:03Bleo182600722719623455222 quits [Quit: The Lounge - https://thelounge.chat]
12:00:41irisfreckles11 joins
12:02:56Bleo182600722719623455222 joins
12:04:47irisfreckles1 quits [Ping timeout: 272 seconds]
12:04:47irisfreckles11 is now known as irisfreckles1
13:44:11<klea>2026-01-20 07:09:06 <@arkiver> something like PROJACTA=0.7;PROJECTB=0.1;PROJECTC=0.2, then it choses one of these according to the fractions. <- does this change the prefered field on the tracker, or add a new field or smth?
13:44:42<klea>i'm thinking on how to best modify my bot's code for archiveteam's choice thingy for the wiki
14:10:28cyanbox_ joins
14:13:59cyanbox quits [Ping timeout: 272 seconds]
14:29:11irisfreckles1 quits [Ping timeout: 272 seconds]
15:30:08PredatorIWD250 joins
15:33:47PredatorIWD25 quits [Ping timeout: 272 seconds]
15:33:47PredatorIWD250 is now known as PredatorIWD25
15:40:35<@arkiver>klea: i think it would simply changes the "auto_project" on the tracker, instead of the current "telegram", we would have a string like the above
15:40:41<@arkiver>or i might do & instead of ;
15:41:07<klea>oh, for backwards compat, i'd preffer if it added a different option, having old workers still work;
15:46:58<@arkiver>true
15:47:14<@arkiver>i'll write a message here when the update is in
15:50:00<klea>thanks :)
15:50:10<klea>all those numbers should add up to 1 right?
15:50:53<klea>also, i wonder, if you're going to be doing such a thing, why not use the fact you're already writing to json and write [ { "project": "PROJECTA", "likelyhood": 0.7 }, [...] ]
15:51:17<@arkiver>klea: well yeah, but i'll normalize them anyway
15:51:41<klea>i mean to be able to later in the future be able to add more fields lol
15:51:43<@arkiver>likelihood, but yes we can do that. but still have to see
15:51:49<klea>oh ok.
15:52:09<klea>> klea: well yeah, but i'll normalize them anyway <- i'm thinking making the bot update main projects with the default project, and the other projects and percentages.
15:54:18<@arkiver>klea: i don't get that last one
15:56:28<klea>arkiver: for <https://wiki.archiveteam.org/index.php/Main_Page/Current_Warrior_Project> i'd have the bot instead show, ArchiveTeam's Choice: $X (For Warriors before $X version)<br>[for project in projects: "\(.project) \(.likelyhood*100)<br>"]
15:58:19<@arkiver>klea: right! sure yes i'll do my best to keep it normalized
15:58:27<klea>thanks
15:58:30<@arkiver>or is it easy for you to normalize anyway when pulling it?
15:58:36<@arkiver>i can't promise mistakes will never be made
16:00:32<klea>normalize what?, i suppose likelyhood will sum to 1, if you want me, i could make it not suppose that, and do shitty math, but that's annoying, and might cause issues if you do that to whatever handling logic
16:04:55<@arkiver>klea: i will anyway normalize the values in the warrior, to make sure things keep running even if a mistake is made and they don't add up to one
16:05:13<@arkiver>but i think it's not a big problem if that mistakes also shows up on the wiki (and can be easily noticed that way)
16:05:25<klea>oh then i won't normalize it so it'll be noticed :p
17:37:56cyanbox joins
17:39:03cyan_box joins
17:40:30cyanbox_ quits [Ping timeout: 256 seconds]
17:40:50DogsRNice joins
17:42:59cyanbox quits [Ping timeout: 272 seconds]
18:08:50DogsRNice quits [Ping timeout: 256 seconds]
18:12:57DogsRNice joins
18:25:37irisfreckles1 joins
20:07:24cyanbox_ joins
20:11:11cyan_box quits [Ping timeout: 272 seconds]
20:22:57cyan_box joins
20:26:23cyanbox_ quits [Ping timeout: 272 seconds]
23:02:36nexussfan (nexussfan) joins

HomeSearchPrevious dayNext day