[00:11:17] hang on for a second I'm confused [00:11:29] what is Nale requesting that raidarr be revoked from on SN [00:11:43] because as far as I know, he holds no rights other than autopatrolled on the wiki [00:23:24] <𝕮𝖍𝖆𝖗𝖑𝖎e#1132> Hiii [00:23:45] hello [00:24:09] <𝕮𝖍𝖆𝖗𝖑𝖎e#1132> I put in that request for permissions thing earlier [00:24:36] GSysOp, but that's a global perm [00:24:55] <𝕮𝖍𝖆𝖗𝖑𝖎e#1132> And also found a little worm sockpuppeter who is prob trying to sneak onto the real AVID, so I gotta stop him! [00:24:57] Can't be revoked by Stewards though except in emergencies... [00:25:14] unless Nale wants his autopatrolled right gone? [00:26:43] It just makes no sense [00:37:07] they do have global sysop [00:37:45] so that could be it, but yeah autopatrolled is up to meta admins and not stewards [00:37:46] im gonna be the first one to say it [00:37:51] but i actually like nale :p [00:38:09] <:ThinkerMH:912930078646730792> [00:38:24] that's a.....view [00:39:32] the most view of all time [00:39:45] who on earth even knows tbh [00:39:58] it's a petty reaction to being called out and he doesn't even remotely try to do it right [00:40:18] I am confusion, America explain [00:40:18] @Orduin any chance it can just be closed because it's not physically possible [00:40:26] like there's nothing to remove.... [00:40:34] oh no me autopatrol [00:40:38] ¯\(ツ)/¯ [00:40:59] holdup I gotta laugh for a minute [00:41:16] kind working on something else at the moment, but yea, will comment in a bit [00:41:43] it's really not priority especially with actual tech things that are an issue [00:41:47] that is true [00:41:58] no rush, none of us are going anywhere lol [00:42:42] just for saying that im probably on some miraheze watchlist [00:42:55] 📸 [00:43:34] you're already on the cabal's secret bluelist, you've only purchased seats to the ultra secret 'lock when nobody looking' blacklist megathread of Enemies against teh State™ [00:44:46] I know there's a certain number of people who do stand or like nale, though after recent events I think that number has diminished somewhat [00:45:12] debating with him right now on SN [00:45:18] I don't hate him, I really don't [00:45:22] but I hate what he's done to MH [00:45:27] you pretty much concluded the thread and there is little to continue [00:45:38] 'what rights' and when he had the opportunity to reply he completely avoided it [00:45:43] [1/3] ```sql [00:45:43] [2/3] DROP TABLE WHERE user_name = 'Bukkit' [00:45:44] [3/3] ``` [00:45:46] so that's just an admission of no case [00:45:47] or smth idk sql tbh [00:45:52] oh mb RfS [00:45:54] oops we lost the user table [00:45:54] not SN [00:46:03] seeya [00:46:08] Bukkit goes poof [00:46:22] Bukkit died, Brandon lied 😔 [00:46:35] hehehe [00:46:35] the old boy's club sends its regards [00:46:46] and the one female who slipped in* [00:46:52] huh [00:47:25] I do appreciate how Nale has escalated from PITA to actively disruptive behaviour <:pupCoffeeMH:766487840694599711> [00:47:33] ¯\(ツ)/¯ [00:47:49] (╯°□°)╯︵ ┻━┻ [00:47:53] ┬─┬ノ( º _ ºノ) [00:48:03] I believe in every user's liberty to make themselves a rope [00:48:43] watch that message be added to another reason on your SN thread [00:48:47] Hole-digging will continue until morale improves [00:49:06] he's currently banned [00:49:09] till April 16 [00:49:18] archive logs exist [00:49:42] anything said here can be published wherever [00:49:43] true but he probably won't check [00:49:48] he will eventually check [00:49:49] and if he does it doesn't matter [00:49:52] mfw naleksuh gets banned in https://wm-bot.wmcloud.org/logs/%23miraheze/20230405.txt [00:49:57] as there's nothing to revoke 🙂 [00:50:15] we probably shouldn't carry on with the subject though, bit crude to be going on and on [00:50:24] true [00:50:34] it's done, there it is, opine on the SN if you haven't and move to more productive things [01:19:08] well [01:34:54] The reason why Cargo-reliant pages still look fine is because they're cached, correct? If so, when do these versions of pages expire? [02:23:22] <𝕮𝖍𝖆𝖗𝖑𝖎e#1132> Something just happened. I just got logged off of every Miraheze wiki I have been too (only 3 wikis) [02:24:23] Yes that was done as a precaution due to a security vulnerability with the Cargo extension [02:24:28] there is a site notice [02:24:58] <𝕮𝖍𝖆𝖗𝖑𝖎e#1132> Oh ok [02:31:47] just fyi it’s “precaution” [02:33:57] We've got a fix in the works for typos already, thanks for the heads up. 🙂 [02:42:59] I keep getting logged out. I logged back in and 30 seconds later got logged out again, this has happened about 15 times that I keep trying, can't even make one action. [02:43:44] the script is still running [02:44:34] What script??? Can't you just change the config. [02:44:48] resetGlobalUserTokens [02:45:02] Why can't you just change the config version that invalidates them? [02:45:04] yeah resetGlobalUserTokens.php [02:49:56] we did change it - apparently last time we had to do this both were done [02:50:21] I did it last time, and I did not do both. [03:03:59] can I get a quick refresher on why semantic mediawiki is bad, its potential addition to our wiki was denied in the past [03:04:15] How big is your wiki? [03:04:33] Might be good to note in the banner that user sessions may be repeatedly invalidated. [03:04:40] the sagan 4 beta wiki was less than 100 pages at the time, right now it's somewhere less than 2000 [03:05:43] sagan 4 alpha wiki has somewhere nearing 6000 pages that would likely be storing data, fewer that would be querying it [03:08:11] a lot less than the spore wiki which seems to do fine with using smw everywhere [03:11:25] both sagan 4 projects are expected to continue to grow...not sure what we'll do when they grow too big for cargo if we stick with it [03:11:56] you should be fine then [03:11:59] storing and querying data was The big solution to make growth more feasible in the first place as it allows custom navigation stuff [03:12:33] what would the limit be before saying no [03:14:01] I know there's a note on Cargo about 50,000 pages [03:21:26] script is now finished [03:22:58] Cool, my current re-updated session survived! [03:35:56] okay, so how do I go about swapping cargo for semantic mediawiki? I've been given the okay to test it on the third and smallest Sagan 4 project, Mason, which is on hiatus and therefore won't be disrupted by the change [03:41:51] you should request SMW be enabled on your wiki on the SN's restricted settings change section [03:42:36] What is a better alternative to use besides cargo for now? [03:43:58] no idea how Wikibase compares to it [03:44:22] a WMF maintained solution would be best as they tend to be the sturdiest [03:51:11] [1/2] just looking at this article, https://professional.wiki/en/articles/managing-data-in-mediawiki# [03:51:11] [2/2] it seems wikibase will definitely not support our needs [03:52:29] inline queries are vital [03:54:23] SMW might. But it can have some issues on Miraheze as well. [03:55:25] I'm switching to semantic mediawiki specifically because I know it will suit Sagan 4's needs and be better suited to fulfilling them overall than cargo [03:55:59] SMW is better than Cargo if you know how to use it, but it can also get more complex. [03:56:05] and it's more intuitive for people who don't know sql but do know their way around wikis, which we're more likely to have in 2033's team [03:56:40] I'm hoping we'll be able to get Cargo up and running again tomorrow. Will need to do some wizardry to do what needs doing though. [03:57:01] the data storage is like categories and let's just say I had to make custom templates to make querying cargo work like smw and be less of a pain [03:58:21] and using smw may also allow us to ditch dynamicpagelists instead of juggling it and cargo together to get smw-like results [03:58:43] Yeah SMW is useful. [03:59:59] But not to easy to switch and has more risk of intermediate downtime if cache or server deploys gets mixed up on Miraheze. It is the disadvantage of a multi-server cluster like Miraheze, that SMW wasn't 100% designed for. [04:03:11] Wonder if that's something we could improve at all [04:04:18] Probably can someway. [04:29:22] how often is intermediate? what does it look like on other wikis on miraheze that use smw? [04:30:24] Every once in a while all SMW wikis go down and when it does a script has to be ran to fix it. Hasn't happened in a while afaik, but more downtime during MediaWiki upgrades, etc... [04:31:09] I think we can survive that with just a heads up to users [04:34:13] is the script run automatically? [04:34:55] (just curious at this point) [04:41:23] I am preparing to mark all the pages that need to be marked for translation. So if you need, please let me know. Just ping me. [04:56:24] Manually [04:59:03] Wonder if that is something we could automate? Like, check for missing or failed setup somewhere and run script depending on output. [04:59:07] If it is run without needing to be ran it breaks things also. It is very fragile. [04:59:47] So that has the potential of causing other issues as well. [05:00:27] We might be able to change things, using ObjectCache, similar to how ManageWiki cache is done. [05:01:00] it is a .smw.json file stored in the /srv/mediawiki/w/extensions/SemanticMediaWiki directory. [05:02:10] But it is only updated on a random server that the job runs scripts on, which is why it has an issue sometimes. [05:03:07] What about an automatic ping to people who can run the script if it thinks it needs to be run [05:05:51] I'll have to take a closer look at how it works later. Really feel like that's something that could be improved. Best option honestly might just be do something like making the directory the file goes in a mounted network directory so all servers are working on the same copy. [05:05:58] Anyway, it's late and I need to sleep [05:06:05] Translation of Cargo to smw? [05:07:06] (I'm tired and need sleep) [05:13:24] Is that worth it for an extension used on less than 10 wikis? It is only enabled on 8 wikis right now. [05:13:34] (re mount) [05:14:12] That seens like it would complicate things. [05:21:07] convinced a creator of a upcoming roblox game to use miraheze instead of fandom, its been working nicely [09:11:13] Does anyone have a link to the cargo bug report? Trying to find it on phabricator to follow when it might be fixed [09:15:27] [1/2] Error 503 Backend fetch failed, forwarded for 2402:800:6312:2262:e921:9b79:b7b0:5086, 127.0.0.1 [09:15:28] [2/2] (Varnish XID 247752628) via cp23 at Wed, 05 Apr 2023 09:14:59 GMT. [09:23:18] hmm, is it possible to delete IRC log? [11:06:51] [1/2] Not sure what is your use case, but I have been using JSON in my own Wiki, implementing the necessary queries in Lua modules. [11:06:51] [2/2] I've never even heard of Cargo, MediaWiki, Wikbase, WikiDB, etc. until now. [11:11:31] Lua is an actual programming language so it's much harder to learn than Cargo or stuffs like that [11:12:26] Yeah, but a lot of people who own a Wiki will probably write their own modules for Scribunto anyway. [11:14:00] [1/2] yep [11:14:00] [2/2] If people knows how to use Lua then Lua perform way faster than Cargo + don't have such thing as query restriction [11:14:32] I wish I know how to learn Lua the easiest way [11:14:41] 😭 [12:27:45] Miraheze should work on smaller banners 😄 [12:34:35] hm? [12:35:07] the banners can definitely be optimized [12:35:40] but realistically someone is going to need to make that their priority, otherwise they tend to be a one-and-done thing with little innovation except correcting errors or adjusting text [12:35:45] you meant language translation, I guess, but you said that in the middle of database extensions talk [12:38:02] Yes [12:38:45] I can help mark pages for translation [12:46:21] tbf, it is kinda rare for there to be 2 global banners/notices at once, and they are meant to be noticed afterall. And with a single banner it is really not that bad [12:56:20] I think it is still bad with a single banner. They are bigger than article text in the default skin, but usually are not that important. [12:56:42] Wikimedia projects also have banners, but they are not as big as ours. [12:57:54] I mean most of them are dismissable as well, so once you see them, you can't just dismiss them and the same one shouldn't show up again [12:59:10] I do think the way the banner works can sometimes be a problem [12:59:16] for example it looks horrific on citizen dark theme [12:59:20] That requires user to take an action, which many won't. And a random viewer is still going to see a banner with 16px text. [12:59:48] there's room to improve but it's all volunteer driven and someone needs to make it their thing [12:59:55] There's no reason why at least font size couldn't be closer to article text font size. [13:00:26] cc @Agent maybe we can consider font size tweaks and try it out on different skins? [13:00:57] wouldn't be top thing to do obviously but it wouldn't hurt to give it a look [13:01:58] I can suggest improvements if needed. [13:03:03] feel free to compile a list, and it can be a solid thing we note/take on at a given time [13:03:55] Well, I don't know where those banners come from, since [[Special:CentralNotice]] does not feature this one, but I can say what will be a bit better here. [13:03:55] https://meta.miraheze.org/wiki/Special:CentralNotice [13:03:55] [13:06:35] [1/5] Something like this, for example. [13:06:35] [2/5] * `font-size: 120%` to `font-size: 1.1em` [13:06:36] [3/5] * `padding: 10px 15px;` to `padding: 1em` [13:06:36] [4/5] * `padding-top:0.3em; padding-bottom:0.1em;` deleted [13:06:37] [5/5] * `padding-bottom: 15px; font-size: 13pt;` to `padding-bottom: 0.5em;` (delete the font size) [13:10:36] Would be also good to have dismissable button inside the banner. [13:16:29] Hello, sorry for the big images [13:17:43] Anyone knows why this doesn't code (fig. 2) does not display (fig. 1) as my expectation of a template navbox (ie. )? [13:18:06] Looks like you don't have Template:Navbox at your wiki. [13:18:23] That's on the same page [13:18:33] OH ok [13:18:37] I'm ultra dumb [13:23:16] I got template loops : [13:26:04] real would be a basis, like infobox template from Wikipedia [13:26:13] [1/2] I made a page called Template:F [13:26:13] [2/2] I made a page called anything [13:26:34] in the end of "anything" source code what should I put to "call" the Template:F [13:26:44] like just {{F}} ? [13:26:44] https://meta.miraheze.org/wiki/Template:F [13:26:45] [13:26:49] this is not real template code, you are calling a base template to create another template [13:27:17] you looking at Wikipedia navboxes? [13:27:31] https://en.wikipedia.org/wiki/Template:Gaichi)? [13:28:06] So I would have to create a page called Template:Gaichi [13:28:27] [1/9] with like [13:28:27] [2/9] ```` [13:28:27] [3/9] {{Navbox [13:28:28] [4/9] | name = Gaichi [13:28:28] [5/9] | state = {{{state|{{{1|autocollapse}}}}}} [13:28:28] https://meta.miraheze.org/wiki/Template:%7bstate [13:28:28] [6/9] | title = Former external territories (''gaichi'') of [[Japan]] [13:28:28] https://meta.miraheze.org/wiki/Japan [13:28:28] [7/9] | listclass = hlist [13:28:29] [8/9] etc. [13:28:29] [9/9] ``` [13:28:32] [1/2] yeah, so if you want them to work like that you'll need to import the whole thing w/ all included templates and modules [13:28:32] [2/2] and there's no guarantee it will go smoothly [13:29:13] I'm telling you again - this template depends on another template which is the real navbox [13:29:38] where is it then? [13:29:58] [1/4] if something starts w/ `{{` it's [13:29:58] [2/4] - a template [13:29:58] [3/4] - a magic word [13:29:59] [4/4] - a parser function [13:30:58] [1/3] I guess [[w:Template:Infobox]] [13:30:58] https://en.wikipedia.org/wiki/Template:Infobox [13:30:58] [2/3] it needs to be exported/imported w/ all included templates and modules [13:30:58] [3/3] but expect errors in the end, could be a big problem [13:30:59] [13:31:26] I suggest to make an easy table or use FANDOM's navbox builder module [13:31:36] instead of taking from Wikipedia [13:32:44] mediawiki's version of navbox should't have a huge dependency chain [13:33:08] on mw.org? [13:33:15] Ok interesting [13:33:38] yes [13:34:07] Why is it so complicated ^^? [13:34:27] code bloat would be my guess [13:34:37] a neat thing is added that leads to another neat thing that has 5 dependencies.... etc [13:35:53] requires arguments module (which is super convenient for lua anyway), navbar module (which is nice to the v / t / e links), and template styles extension [13:36:15] Navbar requires tabletools module and that's the end of your dependencies [13:36:56] Or you can choose to omit navbar altogether by commenting it out from navbox [13:45:31] There are explanatory pages on mediawiki.org: https://www.mediawiki.org/wiki/Help:Contents [13:45:40] Using templates from Wikipedia is like moving to hell [13:45:54] If you are struggling with understanding that `{{Navbox` is a call to Template:Navbox, that's probably a good place to start. [13:46:57] I want to create one, not importing them [13:48:48] Even copying them requires multiple steps, I think the one on Fandom is super simplified. [13:49:26] Aand you can straight up import from them without much problems [13:50:38] https://dev.fandom.com/wiki/GlobalLuaModules/Navbox [13:54:08] [1/2] Following the tutorial () [13:54:08] [2/2] I created a page: wiki/Welcome [13:54:43] Should probably copy that over to https://dev.miraheze.org/wiki/Category:Templates [13:54:57] With attribution of course. [13:55:14] Wait qe can import fandom infoboxes into miraheze? [13:55:58] No one said anything about infoboxes 🙂 [13:56:13] What am I doing wrong [13:56:19] {{subst:Welcome}} [13:56:19] https://meta.miraheze.org/wiki/subst:Template:Welcome [13:56:20] [13:58:12] [1/2] {{Welcome}}/nowiki [13:58:12] https://meta.miraheze.org/wiki/Template:Welcome [13:58:12] [2/2] {{user github|account=karpathy}} [13:58:13] https://meta.miraheze.org/wiki/Template:user_github [13:58:13] [13:58:40] The user github template does not work tho [13:59:25] `{{Welcome}} ` must be in code editor mode [13:59:25] https://meta.miraheze.org/wiki/Template:Welcome [14:00:32] visual editor treat that thing as normal text, not codes [14:01:48] The problem is in the fact you have `` [14:03:07] You really should read up on the link I've sent you before, not just the Templates page. [14:39:39] [1/2] you trying to use template w/o actually having it [14:39:39] [2/2] you should first make a `Template:Welcome` page w/ all the code stuff like HTML, welcome text itself, etc [14:40:08] and ^ [14:51:48] does MH use `$wgCSPHeader`, seems to, but can't see the config in LS.php on GitHub? [15:11:17] if it's not in LS.php I don't think so no [15:12:12] We don't use wgCSPHeader [15:12:31] The actual CSP header is set at the webserver level, higher up the stack [15:12:31] We set it in the headers [15:17:41] is it on github? [15:17:48] yes [15:18:01] gimme a sec [15:18:20] https://github.com/miraheze/puppet/blob/4c3e56f2a5a461d7ef0be3bb6e142169c51f48a1/modules/varnish/data/csp.yaml [15:19:13] cheers 🙂 [15:26:55] why did MH just sign me out.... [15:27:05] #announcements [15:28:07] Goodnight! [15:29:38] Well, there is a kind of blue Miraheze thing on the "Global Interwiki Administrators" role so... [16:09:28] yikes [16:09:34] another cargo exploit? [16:10:00] another one [16:12:18] and that's part of why we're switching to smw [16:13:43] well, I can't access the logs on WMF Phabricator (they're restricted it seems), but I guess the issues are all related [16:15:16] I'd expect a security issue that requires everyone to be logged out as a precaution is probably bad enough that they don't want any random joe to be able to see it and use it [16:16:32] i'm afraid this new exploit might not be prevented by logging out users, because it can be used by anyone visiting the wiki I think [16:16:59] (if the cause of this issue is what I've seen on another private server, that is) [16:17:59] Well the disabled cargo entirely across the farm, and logged everyone out [16:18:25] [1/2] 🤔 [16:18:26] [2/2] i think this should be done to other non-MH wikis using Cargo as well [16:19:26] Well MH can't exactly control non-MH wiki's [16:28:32] hey guys, I am new so sorry for a dumb question, but why can't I see the Timeless skin in my list of skins? I think it was there.. and now I can't get it to work [16:28:43] this [16:32:18] how do I turn off new registrations for my wiki, is that by ticking "close" on Special:ManageWiki? [16:33:22] Close is not for that, it literally closes the wiki, in that it starts the process for it to be deleted per the [[Dormancy Policy]]. [16:33:22] https://meta.miraheze.org/wiki/Dormancy_Policy [16:33:39] why would you want to do that? Maybe there's another way to do what you want to do [16:34:05] No, that makes it so you can't even edit [16:34:12] so only I can edit it [16:34:30] is my goal [16:34:31] temporaily [16:34:42] Revoke the edit right from the `(everyone)` and `Users` group [16:34:51] thanks [16:34:53] in Special:ManageWiki/permissions [16:35:26] do note though that people with user accounts on other Miraheze wikis can also use their account on your wiki [16:35:37] hence why you have to revoke editing privs from users too [16:35:46] got it, thanks [16:40:11] that got rid of my ability to edit unfortunately, I know how to reverse it, but if anyone knows how to restrict editing to administrator let me know [16:41:05] Give administators the edit permission [16:41:44] oh duh, thanks [16:42:00] no problem [16:43:02] I can see the skin in my personal preferences but can't make it default for my wiki [16:43:28] Also you probably want to do the same with the createpage right as well (edits controls editing existing stuff, createpages allows to well create new pages) [16:44:11] yea was messing with that option too and other, thx [16:48:28] and I think while it does work on some pages, it doesn't on the others. Like. one page will look great and the other will have no skin at all, just plain txt. How can that be? [17:02:19] Examples? [17:04:28] Go to Special:ManageWiki/settings, then to the "Styling" section and change $wgDefaultSkin. [17:04:39] Cargo has a number of issues. They are varying in severity. [17:05:03] But some seem to indicate fairly fundamental flaws [17:05:38] Did Bawolff happen to look into it? [17:06:18] NVM. [17:08:44] Does this Cargo exploit effect those who weren't using Cargo or does it effect everyone? [17:08:54] umm, Cargo is suddenly missing from my wiki https://spcodex.wiki . Any ideas why this happened? It's still enabled in Special:ManageWiki [17:09:29] Cargo was disabled for security vulnerabilities [17:09:32] it was disabled [17:09:34] oh I see, reading up [17:09:35] yeah [17:09:40] this is a problem [17:09:48] my wiki 100% relies on Cargo [17:10:01] https://meta.miraheze.org/wiki/Tech:SRE_noticeboard [17:10:43] I'm guessing this is about https://phabricator.wikimedia.org/T331362 [17:11:22] dont have access to that task but im assuming yes [17:13:00] musikanimal: please PM [17:15:06] i use a vpn and it looks like im blocked from editing meta even when logged in [17:15:16] is there anyone that can allow me to edit? [17:16:16] Oh that phab task is private, no wonder why I couldn't find it [17:18:28] Please DM me your IP, that shouldn't be the case [17:18:33] Rarely do we hard block an IP [17:29:47] [1/2] @musikanimal depending on how you are using cargo, if you want to do so, it may be possible to switch to semantic mediawiki; I'm currently rewriting basically all of Sagan 4's cargo stuff to use semantic mediawiki and so far it's proving...surprisingly easy? but as someone else mentioned before, the way sagan 4 was using data storage/queries was more suited to smw anyway [17:29:48] [2/2] (though, literally all queries were running through a few templates that basically make cargo queries work more like semantic mediawiki, because of course we were, which also made everything easier because after updating all the infoboxes all we had to do was update said templates) [17:30:09] nah, it will take ages to migrate from Cargo [17:30:22] my wiki is dead without Cargo, plain and simple [17:30:27] damn [17:32:53] unrelated-related I kinda want the Semantic Result Formats extension (which adds more results formats to semantic mediawiki; I mostly want it for the gallery format lol) but it is not listed on the page for managing extensions [17:34:47] meanwhile, I'm filling up tables on my music wiki manually 😅 [17:35:56] I looked at your wiki as example at first, because there isn't many such organized music related wikis [17:35:59] I'm lucky bc I learned how to use smw when I was active on the spore wiki years ago [17:37:05] and going back to it I still find it more intuitive than cargo 😛 [17:39:13] maybe cargo is better for things I never use it for [17:40:26] Wonder if you can temporarily replace cargo with external data but I think that’s a one way data flow though… [17:49:34] yes the thing is, some of my pages look fine, and some look like this [17:56:10] same. In case of our wiki, it would take weeks of developer's work to make it non-reliant on Cargo [17:56:12] and the alternative to Cargo would be having 50000+ bot-updated templates [18:11:11] Is there a chance that Semantic Scribunto will be considered again even with how it interacts with composer? [18:13:36] Anyway, is requesting an extension that isn't listed a thing? Bc I want Semantic Result Formats [18:13:58] I think so if we install it via Git and not composer as it suggests [18:19:49] That looks like only the sidebar was rendered. Can you provide links to the pages were this takes place (unless your wiki is private)? It might be too much CSS refusing to load. [18:32:51] sorry it is private yes. Everything is rendered. Even more, it stopped working today, everything was fine before [18:45:09] I'm hoping to try setting something up today so we can run cargo despite the risks. [19:25:10] ? [19:25:39] You can submit requests for new extensions to be reviewed and potentially approved, yes [19:26:16] See https://meta.miraheze.org/wiki/Extensions#Disclaimers for details [19:26:59] let me check, I believe SRF has already been requested [19:28:30] yes, it has been [19:28:36] it's a currently active process [19:29:33] Looks like SRF ran into some install compatibility issues that remain open. [19:30:08] [1/2] Ticket in question: [19:30:08] [2/2] https://phabricator.miraheze.org/T9287 [19:30:55] yes [19:37:50] whenever the Cargo issues get resolved and the extension enabled again, would be nice if there was also a warning telling that the extension might be disabled at any time due to security issues [19:39:59] Any extension can be disabled without notice [19:40:10] I don't intend to enable Cargo until I can confirm that these types of security issues are technically mitigated by our setup. Such a warning would then be unnecessary (ideally). [19:40:16] We can’t predict when a security issue will happen [19:40:40] yes but I think with Cargo this can impact much more, as wikis tend to be more reliant on it [19:40:42] The extension has some severe bugs that make it possible to read databases [19:40:54] so it's either we let people read passwords and sessions or disable it [19:41:07] That applies to many extensions [19:41:22] TemplateStyles would be another [19:41:52] at the moment my only "crude" alternative (other than SMW) I can think of is using PageForms to make it write stuff into a page with JSON content model, then read from that with Scribunto [19:42:01] probably not best choice [19:42:03] Cargo seems to have issues perennially [19:42:10] which is unfortunate [19:42:14] an alternative should exist [19:42:16] it's practically inline sql, isn't it? [19:42:35] like just sql on a wiki page [19:42:50] Yes [19:43:17] it's unfortunately kinda expected that ways to fuck up sql databases could be found in it [19:43:19] [1/2] afaik, the Cargo Queries are parsed through Parsoid then sent to the database [19:43:19] [2/2] but I imagine that could be easily exploitable to make direct SQL calls [19:44:43] actually, there's also wikibase as an alternative, but I don't like it [19:46:05] It also requires an entirely new wiki [19:49:29] Anyone have thoughts on the Nale situation? Not trying to pile on here, just want to gather info on who believes he's right with this. [19:49:37] On the issue overall. [19:51:10] Happy to explain if needed. [19:53:02] honestly rather it don't spread to the discord too tbh [19:53:31] +1 on that. [19:53:46] it's like 3 different things at once and it's already virtually impossible to track on-wiki without putting in work [19:54:57] Not here please [19:57:26] I disagree with the decision but okay [20:35:49] I'm still actually surprised how fast I was able to switch the mason wiki to using smw instead of cargo. Though it's mostly thanks to basically everything going through one template that made queries less of a pain to type out [20:36:40] I think it fixed itself? looks good now [20:38:42] ugh, mbf is still asking to be unblocked on AYTW [20:41:42] I'd shut him down completely at this point if it's the exact same as before [20:42:35] yep, pretty much: a closure, a 'no' and a word from aytw admin telling him to drop it for good is what I would advise [20:42:45] just checked it [21:21:10] Congrats on your (presumptive) promotion to bureaucrat! I did a bit of cleanup on the template used in your post to the Stewards' Noticeboard to assist once a steward is able to close the election for you and assign rights. [21:23:43] same, that wiki has needed work for some time now [22:06:17] <𝕮𝖍𝖆𝖗𝖑𝖎e#1132, replying to NotAracham#0009> Thanks! I couldn't have done it without you guys! [22:07:12] <𝕮𝖍𝖆𝖗𝖑𝖎e#1132> Woah! Being a steward must me an awesome job. I might apply in a couple of years [22:13:13] I assure you it is not what it is cracked up to be [22:19:46] <𝕮𝖍𝖆𝖗𝖑𝖎e#1132> Why is that? [22:20:01] I hate to ask but does anyone have any skinning experience? [22:20:26] Any solution on how to unlink the two red elements so they don't share the same color? [22:23:43] Might need to be a little more specific on which elements you are talking about [22:26:09] The two elements which are red. Essentially the search bar and top in red share .color1 [22:27:37] if thats the case, then itll have to be brought up to the maintainer of the skin? im not 100% sure though :p [22:29:06] it is the front line of disturbing, demoralizing and at times simply difficult to contend with content and situations [22:29:16] a certain temperament is needed for it [22:30:59] It was Universal Omega, I don't know if he's still here anymore. [22:34:15] He is here, @CosmicAlpha [22:35:51] <𝕮𝖍𝖆𝖗𝖑𝖎e#1132, replying to raidarr#6550> Oh [22:36:20] There's probably some css wizardry to fix it, but I wouldn't be able to try for a while [22:39:04] do they have other classes or ids that you can reference? if so you can make a new rule referencing one of them individually in common.css or the css for that skin and itll override the red [22:46:28] So how would I go about modifying that div? [22:46:54] did you find if it has an id? [22:46:59]