[09:48:31] !log tools deploy builds-api 0.0.78, ci rebuild [09:48:33] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools/SAL [14:54:38] mmhh sal.toolforge.org is 500ing for me, known? [14:56:55] !log tools.sal restart to fix 5xx errors [14:56:57] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.sal/SAL [14:57:23] seems to happen from time to time (see sal SAL) :/ [14:57:37] thank you Lucas_WMDE / lucaswerkmeister ! can confirm turning it off and on again worked [16:50:43] bd808 sa3 Yes, it's abandonware essentially... superseded by the IP Info tool from AHT https://meta.wikimedia.org/wiki/IP_Editing:_Privacy_Enhancement_and_Abuse_Mitigation/IP_Info_feature [16:51:09] I offered to fully takeover ipcheck and maintain it, but SQL declined [16:52:01] Kinda sad because IP info hasn't reached Miraheze so I still use ipcheck [16:53:26] Last time I tested it worked fine [16:53:28] Though [16:53:54] Yeah 1 provider is down but that's that provider banning bots [16:54:52] It is sad! I guess SQL felt left out when AHT built the IP Info tool that was clearly based off of his work... though I recall AHT saying they tried to include him. I don't know :( [16:56:59] musikanimal: *coughs loudly and points at bullseye* [16:58:40] (bullseye.toolforge.org) [16:58:42] yeah Bullseye basically does the same things right? [16:58:56] I thought it even used the ipcheck API at some point [16:59:00] it does a lot of similar things and actually hits the ipcheck API [16:59:07] yup [16:59:16] GenNotability: cool! [16:59:29] yeah, so we want to keep ipcheck up and running, then. I am committed to that at least [16:59:51] Bullseye has the greatest logo of all time, by the way [16:59:52] it doesn't _need_ ipcheck, just uses it as one of many data sources [16:59:53] :D [17:00:05] the most useful data sources IME are Shodan and Spur [17:00:18] yeah, Spur is basically the only thing I use these days [17:00:28] but I should be using Bullseye [17:00:31] GenNotability: I just tested it [17:00:33] That's cool! [17:01:05] bullseye ties in shodan and spur - if you don't qualify automatically for them (they're restricted to...CU/steward, I think?) I can manually grant you access [17:01:48] I am not CU/Steward [17:02:01] I don't have CU/steward anymore [17:02:13] I'm still sort of on a hiatus from counter-vandalism [17:02:31] just a mo... [17:03:19] okay, you're both now in the "trusted" group and have access to all data sources [17:04:15] (the restriction is because shodan and spur are both paid and have a query limit / month, we're nowhere near the limit but I don't want to open up a DoS vector by handing it out to just anyone) [17:04:47] awesome, thanks! [17:05:00] yeah I understand [17:05:21] Can see it now [17:05:36] Slow to load but I blame the temp wifi connection [17:05:46] patches and feature requests welcome [17:05:46] New flat doesn't have internet yet [17:05:59] https://github.com/GeneralNotability/bullseye [22:19:23] on a different topic, what do folks think about migration away from GitHub, since (i was a bit shocked to learn) it’s owned by M$? (who uses it to exploit, ofc). [22:19:48] I was thinking of Forgejo / framagit [22:20:29] for toolforge/Cloud VPS projects, https://gitlab.wikimedia.org/ isn't a bad option [22:21:29] who owns gitlab? (lmao if it turns out to be AWS or some other big tech, pick yer poison) [22:22:09] they're independent [22:22:19] but that instance is operated by the Wikimedia Foundation [22:22:31] oh [22:22:32] wait [22:22:51] gitlab software itself is f(L)oss?? [22:22:57] ehhhhhhhhhhhhh [22:22:59] it's open core [22:23:04] we use the open bits [22:23:13] hah [22:23:15] nice [22:23:33] hm well [22:23:52] (specifically mostly MIT license) [22:24:11] has wm done a lot of mod/hacking of the core? to make it work better for wm-dev? [22:24:20] gotcha [22:24:48] no, which is why most actual development is still on https://gerrit.wikimedia.org/ [22:25:54] the whole idea was that GitLab would replace the home-assembled CI stack without signficiant customization [22:26:06] unfortunately that didn't happen [22:31:04] … because it’s too much work? [22:31:09] (in a nutshell) [22:31:32] ((incl i.e. being a wicked problem)) [22:33:29] BTW— “Using Free Software to develop Free Software [22:33:29] Forgejo development happens on Codeberg, which is itself running Forgejo and Woodpecker (for continuous integration). By “dogfooding” our code, we aim at being close to our users and serve them better.” [22:34:02] https://forgejo.org/faq/ [22:35:09] Forgejo [22:35:09] Beyond coding. We forge. [22:35:09] Forgejo is a self-hosted lightweight software forge. [22:35:10] Easy to install and low maintenance, it just does the job. [22:35:11] Brought to you by an inclusive community under the umbrella of Codeberg e.V., a democratic non-profit organization, Forgejo can be trusted to be exclusively Free Software. It includes and cooperates with hundreds of projects (Gitea, Git, ...) and is focused on scaling, federation and privacy. [22:38:57] sa3: info dumping on git hosting options is probably off topic here. [22:40:14] sorry. thanks. [22:41:11] what is a good place to discuss git hosting? [22:41:37] (and i hear you re: infodumping regardless) [22:45:20] !log tools reboot tools-sgebastion-11 (dev.toolforge.org) to recover from stuck NFS client causing a high load average [22:45:22] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools/SAL [23:00:29] sa3: I think asking about git things related to the movement here is fine. The info dumping is, well you know. :) For in depth git conversations in general I don't have any great suggestions. There is the #git channel where folks get different kinds of help with git.