[10:19:02] @Site Reliability Engineers any chance we knock out some of the phab import requests? [11:20:47] Anyone have any idea why it says module:Sidebar doesnt exist, when it does? https://meta.miraheze.org/wiki/Template:MediaWiki_releases [11:25:52] page model is CSS <:ThinkerMH:912930078646730792> [11:26:18] What should it be, I can fix it [11:27:01] i dunno [11:27:16] why it has to be done in the first place [11:28:00] Ill just switch the model back and see what else I can break [11:28:11] fun <:EpicFaceMH:912930767972225095> [11:29:47] Well now its a new error 😂 [11:30:09] Imma just go “borrow enwiki’s module” [11:31:44] yeah [11:31:57] it was probably fixed several times since tho [11:32:13] might lead to another error lol [11:32:27] But that will have to wait til after I get home from work around 5PM, I don’t have time to do it rn before I leave, and it doesnt appear to breaking anything important (yet) [14:18:54] is it possible to at least limit task title and description to creator and admins? [14:42:32] manually reverted descriptions, can't fix projects from mobile tho [14:46:39] Uh someone locked some of the projects to certain perms [14:46:59] and i have no idea how to revert because "admin" is a super power user lmao [14:47:55] how tho [14:48:10] damn [14:53:45] [1/2] block on mira [14:53:46] [2/2] [14:54:18] was he CU'd and IP banned tho? he keeps making new socks [15:06:42] ok fixed [15:25:50] you can do `./bin/policy unlock TXXX --edit paladox` or whatever username [15:26:05] which will give the `paladox` account edit rights for that task [15:26:06] Yeh realised it’s the hashtag that’s the object [15:26:15] Wasn’t clear but digging I found that out [15:26:45] Also realised the edit perms were set to the configuration/extension projects so I could have just joined them [15:28:22] https://we.phorge.it/book/phorge/article/unlocking/ [15:28:27] this is the full docs [15:32:35] trusted contributors acl would stop project vandalism [15:33:38] still a few (https://phabricator.miraheze.org/project/manage/15/) that need policy unlock [15:35:56] btw the miraheze.org cert expires in 17 days, and it was reception who had access to generate the certs that we had bought [15:36:33] not sure if anybody else was given access [15:41:38] @paladox https://phabricator.miraheze.org/project/manage/15/ needs policy unlocked via cli (only the vandal can edit) [15:43:25] What’s the hashtag [15:43:34] I carn’t unlock it without that [15:49:08] @paladox I would run "SELECT phid FROM project WHERE name="MIRAHEZE IS NO LONGER MANAGED IT HAS BEEN ABANDONED LEAVE NOW QUICKLY"" on the phabricator_project db and used the PHID that you get [15:52:03] Fixed [16:05:32] [1/2] bump [16:05:32] [2/2] there's possibility of new wave of forks coming on mira too [16:13:46] MacFan4000: Regarding the cert I sent it to Paladox around two weeks ago [20:47:25] I've created a Trusted Contributors group on phab similar to how WMF does it, and I've restricted editing of projects to require membership in this group. Going to set most tasks to this as well soon. Should limit disruption. [20:51:21] Default edit policy is already limited in this way [20:52:52] If anyone needs (or even just wants) access, please let me (or any other current member of the group) know and we can add you. [21:29:25] Edit policy for all publicly editable tasks has been updated now as well [21:33:27] + me plz [21:50:48] done [23:10:50] Could you add me? [23:17:15] 👍