[00:00:07] Actually. Looks to be the revision that was assessed? [00:00:17] No timestamp is logged for when it was actually assessed [11:33:29] i'm on mw 1.31 and i want to move to 1.34. is parsoid still required for 1.34? [11:34:57] ? [11:35:26] Parsoid has never been required unless you’re using certain extensions [11:40:48] Reedy: i mean if I want to keep the visual editor [11:40:58] i read that parsoid will soon be deprecated [11:46:30] So how do I get myself added to the oathauth-tester global group? :-) [11:54:09] bootc: It needs very hard testing [11:54:34] k-man: Parsoid as a node service will be, in 1.35 it'll be included as a PHP library [11:55:43] ah right. so just stick with parsoind in 1.34. thanks [11:56:52] bootc: What's the reason? [11:57:00] (and onwiki username) [11:57:39] Reedy: honestly, because 1password says I should be able to enable 2FA but I can't otherwise (and Bootc) [11:57:47] heh [12:01:55] bootc: Should be done [12:02:27] Reedy: shiny, thanks [12:04:14] (neat: that also enables WebAuthn, just like on wikitech) [12:04:49] Yeah.. There be dragons with webauthn though on other wikis [12:05:04] Just be aware you need to sign in on the same wiki every time [12:05:17] *shrug* I can have a play with it at least - I'm not exactly a prolific wiki user :-/ [12:05:27] I'm just saying incase you get caught by it :P [12:05:35] We need to work out how we're gonna handle/work around that workflow [12:06:33] presumably always redirect to one particular location to do the webauthn check and redirect back - like an OpenIDC/SAML endpoint or whatever [12:08:24] Indeed, at least for the "centralauth" wikis [12:08:49] Just the extension doesn't support that (and questionable if MW does).. So we need to do something thinking and possibly architecting for it too [13:34:33] Hi guys, I installed Flow on my mw and now I want to deactivate it. But when running convertToText.php I get "PHP Notice: Undefined index: flow in ..." [13:34:44] How can I disable Flow? [13:43:19] tim9917: a PHP Notice usually it's not an error. Does it prevent the script from running? [13:43:40] yes, I can't deactivate Flow [13:44:02] How do I disable it Vulpix [13:44:13] Do you know it? [13:44:26] I don't know. Maybe the extension page gives more information [13:44:28] !e Flow [13:44:28] https://www.mediawiki.org/wiki/Extension:Flow [13:44:50] No, it doesn't :( [13:44:54] I already read it [13:45:04] it doesn't help [13:45:19] https://www.mediawiki.org/wiki/Extension:StructuredDiscussions/Turning_off_all_StructuredDiscussions [13:45:37] If you wish to stop using StructuredDiscussions on your wiki, the recommended approach is to convert the StructuredDiscussions boards to text with convertToText.php [13:45:41] I did that [13:45:55] and it's not working like they say [13:46:01] that's my problem [13:46:12] that was the first thing I read [13:58:58] I don't have experience with Flow, sorry [14:08:46] No problem Vulpix. Maybe someone else knows [15:39:05] we had a massive spam posting last week, more than 3000 accounts were created spamming the place all over [15:39:22] but... I didn't find any good ways to get rid of them [15:39:45] https://www.mediawiki.org/wiki/Extension:BlockAndNuke looks promising, but doesn't work on newer MediaWiki instances [16:51:04] is anyone interested in helping me start a wiki hosting service? [16:59:23] Examknow: sure if you bring the know-how, capital and hard work P-; Why do you want a new one? Aren't the existing ones any good? [17:00:07] I'm kinda on the look for a more automated way of delivering Mediawikis and Wordpressen, than hosting on own VPS [17:03:50] jukebohi: I am thinking of making a way to have users able to create their own wikis via an extension [17:03:57] similar to the way farmer used to do [22:08:58] How do I remove a watchlist entry from a user without changing anything else about them? [22:09:40] our instance auths via AD and a former user had a watchlist set up, resulting in bounces now [22:11:43] gloin: do you have database access? [22:11:50] ToBeFree: yes [22:12:17] I have not tried this, am not a developer and you might have already thought about this, but my first idea would be removing the row from the watchlist table [22:12:59] to my understanding, there's nothing more than one row to be deleted [22:13:12] the username is part of the row, making a search easy [22:13:19] will chase [22:15:38] No it's not [22:15:46] * ToBeFree looks again, sorry [22:15:47] it isn't [22:15:52] You need the username from the user table, to get the user id, and then use that ont he watchlist table [22:15:57] And then do the same for the page table [22:16:00] exactly [22:16:04] was just getting there :) [22:17:18] ah, heh. Of course mine contained my username. But yes. [22:17:48] Oh, page title and NS are already in the table [22:18:01] ^ and that's all I saw :) [22:18:14] fixed, man this guy had tons on watchlist [22:18:17] 3832 rows [22:18:26] People on Wikipedia have 100K+ [22:18:35] * ToBeFree hides [22:18:57] I believe it. [22:21:01] at ~250,000, PHP memory errors occur when managing it [22:21:33] You of course know this only theoretically... ;) [22:21:51] I've heard that somewhere of course [22:22:15] anyhow, thanks! Issue is resolved, delete from tw_watchlist where tw_user = NNN; [22:22:38] Query OK, 3832 rows affected (0.04 sec) [22:22:42] pfft [22:23:04] you're welcome :) [22:24:01] Coworker warned me about the dangerous complexities I was going to face but the structure is really simple (if somewhat denormalized lol). I should have just gone after the database to start with. [22:24:43] actually not even really bad normal form [22:24:46] * gloin shrugs [22:25:45] they have recently changed the structure to make it more... normalized? reasonable? https://www.mediawiki.org/wiki/Actor_migration [22:28:51] nice. hairy project [22:34:22] actor id in watchlist vs a user id in watchlist isn't really any different :P [22:37:14] Makes sense. I need to bow out now and return to some eye-watering (because there isn't any other kind) work on SNMP parsing. Later!