[01:10:57] https://twitter.com/sanbedoyapardo/status/1469109434286850048 [01:10:57] [Twitter] Santiago Bedoya Pardo (@sanbedoyapardo): En 🇬🇧, es probable que en las semanas por venir, los Conservadores reemplacen a Boris Johnson como premier. Una serie de escándalos han llevado a que el partido enfrente un mal desempeño en las encuestas, cosa que probablemente lleve su salida de No. 10 Downing Street. 2/? | 0 RTs | 2 ♥s | Posted: 2021-12-10 - 00:59:18UTC [16:47:30] new poll out has labour at a 8 point lead :O [17:12:03] heh I wouldn't be surprised considering the revelation about the parties [17:12:21] I don't know enough about UK politics but I don't see how Boris can survive as PM after this scandal [17:41:18] does anyone know how to contact the devs from Semantic MediaWiki? [17:41:29] I'd like to ask why they have not made a version for 1.36 and 1.37 [18:13:53] @Lake: it does work for 1.36 now, but not 1.37, they usually don't get to adding new stable support for a but after release. [18:14:54] CosmicAlpha: hmm, sad, I think we will never have SMW on Miraheze then :( [18:15:59] @Lake: looking at it now, it looks like it might work on 1.37, just not officially. It might be something we can really look into I guess. [18:16:47] interesting, but well, I would look if there is any possible security exploit [18:18:36] Actually, nope it won't: https://github.com/SemanticMediaWiki/SemanticMediaWiki/pull/4949 @Lake [18:18:37] [url] Maintenance: replace Revision by RevisionRecord by Seb35 · Pull Request #4949 · SemanticMediaWiki/SemanticMediaWiki · GitHub | github.com [18:19:03] It would definitely be broken until that is done. [18:20:24] Although actually it looks like that was still done just not through that PR. [18:21:29] interesting, but well, you decide, not really something I want right now :P [18:21:42] In fact it looks like they are already implementing some support for 1.38. [18:22:04] Its already approved from a security perspective also. [18:22:14] @Lake: ^ [18:23:14] oh, that's good i guess, if you want to try (if you have any time) [18:23:51] If SRE agree I could try to install the submodule, and only do configuration to enable it on test3 for now, that way way can extensively test it first. [18:24:03] Reception123, RhinosF1: ^ [18:25:18] https://github.com/SemanticMediaWiki/SemanticMediaWiki/commit/d2d941d5e5c6f87b44c589d380af19eb12336e01 does indicate 1.38 support also. [18:25:19] [url] Fix: AbstractContent::getParserOutput was deprecated in MW 1.38 · SemanticMediaWiki/SemanticMediaWiki@d2d941d · GitHub | github.com [18:27:49] Also before we go installing some probably high-intensive extension (which if installed I definitely want to be restricted/request-only at least for awhile) in production I want to figure out whatever the recent performance issues we've already been having are. [18:32:16] CosmicAlpha: I don't have any objections but in terms of priority I'd rather we first deal with all High priority issues related to 1.37 before starting a SMW project [18:34:50] Reception123: I agree, I actually just mentioned that also at https://phabricator.miraheze.org/T7000#170012 when reopening the task. [18:34:51] [url] ⚓ T7000 Reconsider implementing Semantic MediaWiki | phabricator.miraheze.org [18:35:19] CosmicAlpha: yeah.. let me know if I can help in any way with the three open issues [18:35:24] as we really do need to get those done [18:37:22] Reception123: yeah, I'll be on PC in ~2 hours and can look at resolving those. You can update Preloader though if you'd like, as that is one of the issues that should be fixed with it. Otherwise I can in a bit. [18:44:35] ok, let's see then [20:58:57] @Reception123 a task that was filed on phab, it's normally a technical issue, but it was later resolved probably by a means that's more advanced than on-wiki, how would you close such phab task? invalid? or resolved? [21:27:18] https://meta.miraheze.org/wiki/Special:RequestWikiQueue/21831#mw-section-request Before anyone asks me this: "Why did you add "Declining per Content Policy provision, "A wiki must not create problems which make it difficult for other wikis." Thank you for understanding?" Well, I was a tad bit concerned about Content policies involved with this person. One thing on the contrary would be the concern of seeing [21:27:18] unsourced references. [21:27:19] [url] Wiki requests queue - Miraheze Meta | meta.miraheze.org [21:27:58] It's not the easiest call, I can understand [21:28:11] It's one of those topics that makes me wish for a proper WC channel to discuss requests >.> [21:29:35] Yes. I wasn't just about to blindly accept it without even looking at the description or stuff like that. [21:30:57] Otherwise, that would go against everything I've worked for as a wiki creator. [21:33:06] What I mean in particular is that ideally, more complicated scenarios can be quickly brought to the eyes of multiple wiki creators who are online or available at once for collaborative input, rather than someone essentially being forced to take a choice.