[01:16:22] Yeah, they're going downhill quickly. [01:16:54] Which is why people are using ForgeJo, Gitea, Gogs, GitLab, GitBucket, and others. [01:27:50] Single point of failure is bad for any key infrastructure [01:28:49] GitHub as a code history/deployment tool is unfortunately pushing that direction, though not there yet [01:53:44] It's definitely wise to have a main repo and a mirror, which is what WMF does if Gerrit goes down, but I don't think their GitHub mirrors are directly committed to. [04:01:51] Nah man doesn't look like it works [04:01:57] oof [04:03:06] Maybe it wasn't done correctly, or it doesn't work as you might assume? I am not actually certain what it's supposed to do with Discord lol, I just merged as code wise it seemed fine. [05:14:43] Shiiitttttttt 💔 [05:14:58] @whostacking you added this to your wiki, can you help? [05:49:09] gitlab's database incident in 2017 put me off them and there's no better alternative to github so sticking with the devil seems to be the method right now [07:45:40] I mean, yes there are no literal comparable companies, but the others aren't a bad choice. [07:45:56] Yeah, you don't get GitHub pages, or repo apps etc. [07:50:08] Although, there is git-pages, which is an alternative for GitHub Pages. [09:23:05] codeberg, gitlab with its as far as I can tell improved stability over the years are the managed options I'm aware of [09:23:36] although codeberg I think has specific no ai provisions that may inconvenience the oasis case [09:29:48] gitlab never strikes me as overly virtuous but its not overly hard to exceed github there [09:30:03] [1/3] One of the main motivations was to prevent random projects from consuming server resources with their complex CI/CD pipeline, which has been the main issue plaguing GitHub's infrastructure. Microsoft can't ban AI-only projects since it goes against their marketed goal, but Codeberg can. I think as long as Zippy doesn't consume an unreasonable amount of res [09:30:03] [2/3] ources his projects will likely survive fine. Plus the new rule only targets projects that [09:30:04] [3/3] > mostly consist of code written by "generative AI"-tools [09:30:37] zippy will have to comment if the last one applies but I would think oasis as usage goes would not be radical [09:30:59] both in what oasis would use and the fact oasis is actually used [09:33:39] course, github x whatever else is probably not the current top of the oasis fix-things list as I'm sure zippy will attest [09:37:21] looping into relevance here the two things I'd like to see pursue are greater integration with miraheze testing and a fairly complete audit of oasis structure [09:38:26] I think projects that are large enough with sufficient contributors and financial resources or small enough to not care about external contributors are the ones best positioned to make a move. At our size we hit a lot of the downsides without too much gain. [09:39:06] yeah figuring out how to depose the evils for miraheze is kind of tough and some of the extents we do go for that kind of push sustainability as it is, I gather [09:41:08] It was really nice to hear temp account experiences from Zippy. I think it was a good example of Oasis trying new things first and helping Miraheze. If MH can submit some temp account fixes upstream based on Zippy's test results that'll be even better. [09:41:13] my big want for mira right now is basically the community survey [09:41:31] but yeah that kind of testing I think is a good niche for oasis to fill [09:42:22] you see the tech end, I get a feel for how that would play out on the community end too. On the community side there are only a few niches where I think temp accounts would create significant operator inconvenience [09:42:57] the only present major one would be the ukranian lta who would be mildly more irritating depending what level temp ip visibility is set to [11:41:38] I've never had any issues with GitLab TBF and they are really generous with giving out subscriptions for OSS - although it was a couple years ago when I last took up that offer so I'm not sure if it's still around [11:52:53] If you read any of the repos on WikiOasis' GitHub that might answer the latter 😶‍🌫️ [14:46:46] [1/2] submitted another pr: https://github.com/miraheze/mw-config/pull/6557 [14:46:46] [2/2] got some help from stackd from this: https://gist.github.com/whostacking/1d2460d83d623dbc2b5f87308acfeda7 [14:47:06] HOPEFULLY it works [14:47:09] hopefully............................ :3 [15:05:41] :3 [15:17:02] I will look in a couple hours. [15:17:07] Maybe less [15:17:12] But busy right now. [15:18:13] https://klipy.com/gifs/ryan-gosling-real-1 [15:59:04] @jenny_on_wiki Any thoughts on https://github.com/miraheze/mw-config/pull/6483#issuecomment-5560798666 ? Someone asked about upgrading Citizen again and I thought we should merge this PR first. [15:59:57] I think you should be able to edit the PR? [16:00:30] maybe it could remove both of the config options that you mentioned [16:01:19] I'll do that then [17:09:11] tbh I wouldn't hate gitlab but I'd only really see the benefits of the self hosted version [17:09:24] although tbh I think gitlab have an oss/npo program [21:09:53] with 1.46 around the corner, what to do about configuration/managewiki [23:05:31] Amazing, every time I see that Claude logo, I see it as something that sums the entire thing up. [23:06:56] maps extension [23:21:34] Huh? [23:34:05] all recent commits to that extension are co-authored by claude. coincidentally that extension is globally disabled for security reasons [23:35:26] Amazing, maybe we should just uninstall it then. [23:42:58] We might if they can't address our security concerns. [23:43:33] Guess I can't trust ProfessionalWiki extensions anymore either. [23:44:23] But it is one of the few extensions we have ever disabled that has seen some real push back or status update requests for when it will be back. I have gotten numerous DMs + tech Noticeboard requests for it to be re-enabled, but if course security comes first. If security can't be addressed it will remain disabled (or eventually removed) indefinitely. [23:45:19] Similarly to how people asked about getting Widgets back? Which of course is a hard no, security before anything else. [23:45:59] Yes similarly [23:46:41] Anyway I'm stepping away for a bit again now [23:47:06] Alrighty, bye Bye, have fun with whatever you're doing.