[07:23:29] Related to this thread, is it alright to make a PR to set `$wgHiddenPrefs[] = 'realname';` on LocalWiki.php? [07:25:36] [1/2] I've been trying to investigate what makes the MediaWiki footer icon capable of resizing itself in small window or screen sizes (displaying resources/assets/mediawiki_compact.svg) but getting frustrated by the lack of documentation on the mediawiki website of this and it doesn't seem to be in the mediawiki MainConfigSchema either despite specifying the defaults for that footer butto [07:25:36] [2/2] n [07:26:19] I was interested in making a pr for the miraheze footer icon to allow it to display compactly like the mediawiki one can but I do need to know what specific settings actually define that behavior [07:37:59] doesn't sound ideal. it should be added to managewiki directly (already a task [[phab:T15239]]) [07:38:00] [07:39:53] gee thanks that's why I'm asking in this channel in the first place [07:44:50] It's in ManageWiki [07:45:22] Unless I missed something if so I apologize [07:45:50] oh wait I think wr purposely exclude it for some reason [07:46:01] Let me find why [07:46:41] But the answer is no, it being in LocalWiki will have no affect. [07:46:59] Because it's in ManageWiki it will just get overwritten. [07:47:28] i see, that's understandable [07:47:42] I will look into why it doesn't appear in ManageWiki [07:48:13] I'm trying to see if there's at least a config value that can prevent the real name from being outputted on the user pages in the mean time [07:48:27] or hide it using RenderBlocking (not a good solution but [07:51:09] [1/2] Where does it appear? That is a privacy issue all around I think. I would actually like some input from @notaracham on this as well. I guess if they provide it in preference that might be own disclosure which is fine, but it being in preferences is not going to always be understood that it is on-wiki also. I think there was something about this before but I may be misremembering [07:51:09] [2/2] . [07:51:40] We can probably patch something to prevent this if necessary and get a config upstream for it also if one doesn't exist. [07:51:53] i think it's reminded on the register form [07:52:09] [1/2] Timeless [07:52:09] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1555849928192823436/Screenshot_2026-10-02_120243.png?backend=b2&ex=6ac205a9&is=6ac0b429&hm=5c1cdb21b627947b1bd4f2965ca39fb0ec8b98401731e3836e60cccfc30f85a8& [07:52:10] > If you choose to provide it, this will be used for giving the user attribution for their work. [07:52:11] https://cdn.discordapp.com/attachments/1006789349498699827/1555849936698867792/image.png?backend=b2&ex=6ac205ab&is=6ac0b42b&hm=861acba412405e9333acdf389dbae998b7af8a2acd3f42f82fa51567491c2e62& [07:52:24] this is a upv2 feature [07:53:14] That should be possible to turn off if it isn't already IMO. [07:53:44] real name is never intended to be a private config in preferences, same as gender [07:55:12] [1/3] It is considered PII though. And the handling of PII has to be taken with care. Gender is also considered PII. [07:55:12] [2/3] I still would like an opinion from NotAracham on it but yeah we probably don't need to do anything here because they disclose it themselves still. [07:55:12] [3/3] Back to the original topic I will get it added to ManageWiki probably tomorrow. [07:55:29] [1/2] Ah there was no config to stop this from being outputted [07:55:30] [2/2] https://gitlab.com/telepedia/extensions/userprofilev2/-/blob/main/includes/UserPage.php?ref_type=heads#L158 [07:55:56] I might as well ping @originalauthority [07:55:56] @originalauthority is this something you may be interested in adding? [07:56:14] oh whoops double ping [07:56:21] Sorry about that. [07:57:43] there are also some other exts that may output realname, such as myvariables and newusermessage [07:57:46] the original concern was that underage users would enter their real names without understanding the risks of disclosing their personal information [07:58:50] as for gender, more things can output it, including citizen's user page and the bulit in`{{GRAMMAR:}}` parser func [07:59:41] i think both places that accept real name input (createaccount form and preferences) have tips on it may be shown publicly. but yeah ppl can just ignore it and go on [08:00:11] what i mean is mediawiki is not designed to show the option only to the account owner [08:00:47] and upv2's design to show realname there is same behavior as fandom too [08:04:07] UpV2 showing the user's real name "the same as Fandom" just reflects poorly on both 😭 [08:05:04] (obviously it's not the only ext to output realname tho) [08:15:50] [1/2] oh the core also outputs realname actually. i've been using the page https://vocaloidlyrics.miraheze.org/wiki/%E6%9A%AE%E4%BA%91%E7%94%9F%E6%B8%AD%E5%8C%97_(M%C3%B9y%C3%BAn_Sh%C4%93ng_W%C3%A8ib%C4%9Bi)?action=credits to test bc the image shows emily set realname field tho i've been wondering why it outputs username. seems it's already removed so i set the field f [08:15:50] [2/2] or me to test. you can see i set my realname as 'test' in this link [08:17:01] https://cdn.discordapp.com/attachments/1006789349498699827/1555856185918234664/image.png?backend=b2&ex=6ac20b7d&is=6ac0b9fd&hm=3170882e04d925fadd330968c6c814a97560734964d3be214f7f52580f8f9fb3& [08:18:29] so no extension is to blame. the field is intended for attribution [08:20:51] the operation to override this default behavior on `?action=credits` of the core is to set `$wgActions['credits'] = false;` but obviously from the mw-config repo i see no wiki has requested to do so [08:24:40] ofc it's all the same a good idea to allow `$wgHiddenPrefs[] = 'realname';` in managewiki, but this won't remove the column from the user table in the db so unless you also set `$wgActions['credits'] = false;` real names will still appear on `?action=credits` [08:33:29] [1/2] Tested it on local `$wgHiddenPrefs[] = 'realname';` does hide the realname from credits [08:33:29] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1555860329676935209/image.png?backend=b2&ex=6ac20f59&is=6ac0bdd9&hm=67a6480e1e833a54d7280a28531042320734794fb97b8e3452080e6d1889eb86& [08:34:07] [08:34:26] that's good to know. how does it affect the behaviors of realname extensions? [08:38:44] [1/2] no [08:38:45] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1555861651884998746/image.png?backend=b2&ex=6ac21094&is=6ac0bf14&hm=e7ace2e8c35b6aaca3e13024bf99e54e2654cb7f02c88cfd85e503dc9f0a5d67& [08:40:26] i expected so [09:18:59] [1/2] I've made a n MR to UserProfileV2 if that's okay @originalauthority [09:18:59] [2/2] https://gitlab.com/telepedia/extensions/userprofilev2/-/merge_requests/15 [09:20:32] i set it as a test to confirm that that was in fact what was showing up on the "aka [name]" bit for socialprofile [09:21:27] but yeah we ideally we should have the option to hide it. i can kind of see the point of it for certain wikis, but imo it's a risk for wikis like ours which spans a wide age range, and i can't think of any reason why our wiki would ever want it displayed [09:33:05] [1/3] bumping this [09:33:05] [2/3] The MW icon is a `` as opposed to MH's `` [09:33:05] [3/3] https://cdn.discordapp.com/attachments/1006789349498699827/1555875324909326416/image.png?backend=b2&ex=6ac21d50&is=6ac0cbd0&hm=216c1d86a38700d5a3f58c2dad1d0e2b33e7c31eb8426e00348177c16c417a40& [11:40:53] [11:42:31] idk if there's a way to manually add stuff to `$preferences` there, but if `getDefaultOptions` isn't enough that might be the best option [12:41:03] merged ty [16:02:41] @rlin0781 think I found it [16:02:51] [1/19] ```php [16:02:51] [2/19] if ( isset( $wgFooterIcons['poweredby'] ) [16:02:52] [3/19] && isset( $wgFooterIcons['poweredby']['mediawiki'] ) [16:02:52] [4/19] && is_array( $wgFooterIcons['poweredby']['mediawiki'] ) [16:02:52] [5/19] && $wgFooterIcons['poweredby']['mediawiki']['src'] === null [16:02:53] [6/19] ) { [16:02:53] [7/19] $compactLogo = "$wgResourceBasePath/resources/assets/mediawiki_compact.svg"; [16:02:53] [8/19] $wgFooterIcons['poweredby']['mediawiki']['sources'] = [ [16:02:54] [9/19] [ [16:02:54] [10/19] "media" => "(min-width: 500px)", [16:02:54] [11/19] "srcset" => "$wgResourceBasePath/resources/assets/poweredby_mediawiki.svg", [16:02:55] [12/19] "width" => 88, [16:02:55] [13/19] "height" => 31, [16:02:56] [14/19] ] [16:02:56] [15/19] ]; [16:02:57] [16/19] $wgFooterIcons['poweredby']['mediawiki']['src'] = $compactLogo; [16:02:57] [17/19] $wgFooterIcons['poweredby']['mediawiki']['width'] = 25; [16:02:58] [18/19] $wgFooterIcons['poweredby']['mediawiki']['height'] = 25; [16:02:58] [19/19] }``` [16:03:41] This snippet is present in `includes/SetupDynamicConfig.php` in Wikimedia's deployment [16:05:47] There's more too it I'll look for but the idea seems to be checking if there's no source set for the mediawiki badge, set the compact one with settign the width and height [16:05:58] Of course the "media" param is undocumented [16:07:19] actually wait this is core, mhm, wikimedia's badge is somewhere else probably [16:08:58] okay the media param is passed straight to html [16:09:09] https://cdn.discordapp.com/attachments/1006789349498699827/1555975003256651776/image.png?backend=b2&ex=6ac27a25&is=6ac128a5&hm=084223364f228f50c5c874b8d521a99dfde817d8235f0d8f563ac34cd34d5a96& [16:10:48] wikimedia why are you loading your footer icon as the copyright badge you fools [16:12:39] I- is Wikimedia changing the file they serve from the same path [16:12:59] [1/2] https://cdn.discordapp.com/attachments/1006789349498699827/1555975964897452082/image.png?backend=b2&ex=6ac27b0a&is=6ac1298a&hm=38ed47470558d92136e9852f2f433285db1805ac7ad983a3fd807b9f99722747& [16:12:59] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1555975966361387059/image.png?backend=b2&ex=6ac27b0b&is=6ac1298b&hm=9ce5c1f0a44b8c3ff3df7dc112b3183f90b5c61f1a208cb31c11aaa5a0b7b958& [16:16:03] [1/17] ```php [16:16:03] [2/17] $wgFooterIcons['copyright']['copyright'] = [ [16:16:04] [3/17] 'url' => 'https://www.wikimedia.org/', [16:16:04] [4/17] 'src' => '/static/images/footer/wikimedia.svg', [16:16:04] [5/17] 'sources' => [ [16:16:05] [6/17] [ [16:16:05] [7/17] 'media' => '(min-width: 500px)', [16:16:05] [8/17] 'srcset' => $wmgWikimediaIcon, [16:16:06] [9/17] 'width' => 84, [16:16:06] [10/17] 'height' => 29, [16:16:06] [11/17] ] [16:16:07] [12/17] ], [16:16:07] [13/17] 'width' => 25, [16:16:08] [14/17] 'height' => 25, [16:16:08] [15/17] 'alt' => 'Wikimedia Foundation', [16:16:09] [16/17] 'lang' => 'en', [16:16:09] [17/17] ];``` [16:16:10] okay I think I'm starting to get it [16:17:43] So! [16:18:13] The 'sources' key is adding an HTML source element, which allows for alternative media sources to be applied to a tag, (img in this case) if the browser supports it [16:19:52] [1/7] ```html [16:19:52] [2/7] [16:19:53] [3/7] [16:19:53] [4/7] Wikimedia Foundation [16:19:53] [5/7] /picture [16:19:54] [6/7] ``` [16:19:54] [7/7] In this case, it's coming with a media selection parameter, so that source will only be used (and therefore the small badge icon will only be showed) if that media param is true, in this case the min-width beign below 500px [16:29:48] havent been able to get it work in dev tools yet, feel free to mess around, may revisit later [17:14:19] what's the differences between github and gitlsb [17:15:22] they're both Git repositories, so the differences aren't so important if you're not a coder/engineer [18:41:04] is it possible to restrict who can edit a user page? I ask because the practice review tool I'm making asks users to load my userspace javascript and trust it, so I'd like to restrict people from making edits to it [18:41:47] you can protect it so that only admins can edit it [18:42:03] this is on meta [18:42:07] ahhh [18:42:39] in that case keep in mind that your personal .js and .css subpages of your userpage can only be edited by you or meta admins [18:42:54] @jenny_on_wiki [18:42:56] so they're already protected from just anyone editing them [18:43:02] they aren't my personal ones, just in my userspace [18:43:30] I meant pages under your User: page [18:48:47] Is it a JS page under your user page [18:48:57] yes [18:49:03] Should be fine then [18:49:05] cool [18:49:09] wish that was clearer though [18:49:12] Try to edit [[User:PixDeVl/common.js]] [18:49:12] [20:22:44] well, after the release party I was inspired to dust off my mad skillz with the mw-config repo (and fix a bit my old SSH config) and I got this, good old adding settings to mw-config like the old times: https://github.com/miraheze/mw-config/pull/6578 [21:06:29] Just a tip if you Add Bug: Txxxx it will auto attach the PR to the task or if you do Fix(es), Resolve(s), etc... Txxxx e.g `Fix T16083` in PR description or title it will auto close once merged also. Thanks a lot for the PR though, I can get to it shortly also. [21:07:47] huh, I was wondering how that GithubBot worked, thanks for the tip, I was wondering why it wasn't commenting [21:13:10] [1/2] I intentionally only made it under certain keywords like to avoid accidental false positives or something. I plan to write some documentation on keyword triggers for it also. And no problem. GitHubBot is just a Phorge application that has a transaction, UI, comments and webhook logic, that allows GitHub to send to the webhook which it then parses, but I [21:13:10] [2/2] didn't want it just match tasks directly without some intentional activation also otherwise I thought it may have false positives, or accidentally attaching the wrong tasks to it. [21:14:36] It also works if you edit the PR description though, so if you edit the PR description to add the keywords it will attach as well. [21:18:06] [1/2] It can also automatically assign the task to the Phorge user of the GH user who had their PR merged if that merge closes the task, if they have their GitHub account authenticated to Phorge. and there isn't already an assignee when closing. It just helps some repetitive actions of merging then closing, or manually linking PRs etc... plus that way tasks can also more often track PR [21:18:06] [2/2] s actually done for them. [21:19:00] well this is way better than that pull request ready tag I made back in the day [21:24:37] I think we should make it be complementary to that actually. Maybe we should have it automatically add that tag when a PR is open and removed once the PR is closed (even if the task isn't automatically remove it when no open PR for the task) that would also allow us to search for tasks with open PRs as well. [21:26:11] The per-wiki CSP was mentioned in the 1.46 update today. Is there anything I can do to help move it forward? [21:26:16] switch to gerrit and use gerritbot 🙊 [21:27:22] @bluemoon0332 wgVisualEditorTabPosition needs added to LocalSettings.php also I think btw. Unless I missed it somehow it isn't already there. [21:27:38] will add [21:27:42] Thanks! [21:34:21] Thanks again for the PR! Deployed now. [22:37:01] [1/5] It mostly depends on when I pick it up again, and there were some small issues in the existing implementation as well. You can find them on https://issue-tracker.miraheze.org/T15205#318414 (where I complain about the long text in the mutli-select combobox) and the [PR](https://github.com/miraheze/mw-config/pull/6520), which contains some unresolved rev [22:37:02] [2/5] iew questions whose solution I am not certain about. [22:37:02] [3/5] If you can give suggestions that might help resolve some of them. For example, I sort of want to move the URLs out of the combobox labels and into a wiki page linked from the setting. It will be harder to know which URLs are added to the CSP because it requires another click, but it'll make the form cleaner. Not sure about whether we should take this t [22:37:02] [4/5] rade-off. [22:37:03] [5/5] Also feel free to nudge me to work on a feature if you really need it. Usually tech gets annoyed when pushed this way but personally I'm very willing to hear feature suggestions from someone I know who is making good contributions.