[00:02:01] [discord] I'm interested in the idea, but the generated list either needs to be able to distinguish between exceptions such as what Agent suggests with t-mobile or be reasonable to manually check out even if it's just by the ASNs to sverify that they're clear cut proxies that we'd typically block anyway [00:02:09] [discord] I'm interested in the idea, but the generated list either needs to be able to distinguish between exceptions such as what Agent suggests with t-mobile or be reasonable to manually check out even if it's just by the ASNs to verify that they're clear cut proxies that we'd typically block anyway (edited) [00:02:33] edits just pop in as new messages now, fair enough [00:03:34] re Naleksuh. But outside of the above two I'd have to confer with Void and John, both more qualified than me on IP work even if I've successfully gotten the principles of dealing with proxies in general [00:06:22] Yeah, I can check what they are [00:06:30] Good to see you raidar,, yeah we'll see what John and Void have to say [00:48:36] Hello [00:50:23] Can someone please delete my TestWiki user page? Thank you. [00:50:27] https://publictestwiki.com/wiki/User:ApexAgunomu [00:50:28] [url] User:ApexAgunomu - TestWiki | publictestwiki.com [00:53:13] [discord] ApexAgunomu: done [00:53:25] Thanks [00:53:45] [discord] np [00:56:56] [discord] if im gonna be honest the only reason i requested to be unlocked was cuz of raidarr's rfs iirc [02:12:24] [discord] It seems Vector 2022 removes a wiki's logo image and replaces it with a "wordmark". Since I still have bureaucrat permissions on `massivestardatabasewiki`, I set the existing logo image as the wordmark to test this. The result doesn't look good, but I can't unset it. If I try to, I get this message: [02:12:24] [discord] https://cdn.discordapp.com/attachments/435711390544560128/984641148712783922/unknown.png [02:27:42] [discord] Miraheze Meta's wordmark is just the word "Meta" (https://commons.miraheze.org/wiki/File:Meta-wordmark.svg), but the Miraheze logo is displayed next to it. How does that work? [02:27:44] [url] File:Meta-wordmark.svg - Miraheze Commons | commons.miraheze.org [02:28:38] Hmm, I can't even use the new Vector skin https://meta.miraheze.org/wiki/Special:RecentChanges?useskin=vector-2022 [02:29:45] [discord] Oh I see, that's another field in ManageWiki, "Icon". [02:30:32] [discord] Now how do I remove the wordmark image? [02:31:20] [discord] should work [02:31:21] [url] Meta | meta.miraheze.org [02:34:31] [discord] Via Graylog, I see that you got this error: `Actor ID is null for SevenSpheres and 7` [02:34:43] [discord] would require further analysis from a systems administrator [02:34:58] [discord] @CosmicAlpha thoughts? ^ [02:35:42] Is it a brand new account? [02:36:28] [discord] I've had this account since 2020 [02:37:41] Naleksuh: it doesn't exist yet like that, vector-2022 is added only in MW 1.38. The modern vector used up to now as been experimental, and only with 1.38 is it officially supporting third party installations. [02:39:06] Hmm, then actor ID being null shouldn't be, and maybe been a one time thing. I doubt it's related to wordmark images, I don't understand the problem. Actor ID has nothing to do with wordmarks. [02:39:23] @Agent ^ [02:41:17] [discord] CosmicAlpha: Graylog tells me that that's the error causing ManageWiki to not save. I also see this error too: `Failed to instantiate RC log entry performer`. Perhaps the issue is that ManageWiki can't generate a log entry and errors out. [02:42:53] @Agent if that were the cause I'd assume not even login would work. I'm mobile right now. I can check the database for the actor ID when I'm on my PC. I'm semi-away until Saturday though. [02:54:09] [discord] I tried unsetting the wordmark while also changing another setting (icon). The change goes through, but the wordmark image is still there. [02:59:16] [discord] Can somone help me [02:59:16] [discord] I want to make a wikipedia style infobox [02:59:17] [discord] I have tried using the code module but the result is that the infobox has a bug [02:59:19] [discord] so how to solve it [02:59:20] [discord] in the meantime I'm using an old template code I got from one of the wikis [02:59:21] [discord] https://tampvan.miraheze.org/wiki/Templat:Infobox [02:59:22] [url] Templat:Infobox - Tampvan Wiki | tampvan.miraheze.org [02:59:23] [discord] and this is the code of the module I'm using, but if I use it it causes a bug [02:59:24] [discord] https://tampvan.miraheze.org/wiki/Modul:Infobox [02:59:26] [url] Modul:Infobox - Tampvan Wiki | tampvan.miraheze.org [03:02:11] [discord] @ChioGaming2007 what is a bug? [03:11:17] @SevenSpheres oh, it might be caching, we may need to purge it from our end. It happens sometimes. [03:33:29] [discord] did you imported all used templates and modules? [03:44:43] [discord] I don't know which template/module I should import [03:44:44] [discord] the questions are many and not necessarily related to the infobox template [03:53:09] Cosmicalpha : Personally I prefer the old vector [03:53:26] Also, there was never any consensus for the new vector, a few people just decreed to make changes to it and it happened [03:53:39] I didn't complain about it because I use Monobook anyway, but I hope other people don't mind as much [03:56:26] Naleksuh: that's understandable. When we switch the default to vector-2022, I am planning to make the transition as easy as possible, by publishing a sort of guide on meta, with how to revert back to the old vector version if they wish, as I understand that alot of users could be uncomfortable with such a sudden and drastic change, so want to make sure they know how to revert back. I'll probably post the link to the meta page on the [03:56:27] post-upgrade site notice also. [03:56:43] Wait, Miraheze was planning to switch? [03:56:52] Yes. [03:58:02] [discord] I will be keeping vector alive even if it stops being maintained, I have plans to fork it myself the second EOL for old vector is announced (if ever) [03:58:42] That wouldn't help much though as skins are backend [03:58:52] When legacy vector is removed, chances are it'll be split off to another skin by the WMF, or someone else who wants it. [03:58:54] What would be good is a style you can put in your common.css to make vector-2022 look like vector [03:59:04] [discord] No. [03:59:10] [discord] I can fork the backend code [03:59:16] [discord] It’s open source [03:59:18] Yes, but you can't load that code onto Wikimedia [03:59:20] So doesn't help you [03:59:34] [discord] I never said anything about wikimedia [03:59:47] Okay, but then how would people use old vector elsewhere? [03:59:50] [discord] Wikimedia has no plans to discontinue or remove old vector from wmf [04:00:38] I thought they did within the next 3-4 years? Or at least split it into another skin. [04:00:40] I was under the impression it was being removed eventually. Though, there was never any real RFC about this change in the first place so who knows [04:00:51] [discord] I personally don’t care about elsewhere, on wmf 99% of userscripts depend on vector, some require old vector so i don’t see it going away on wmf for the next decafe at least [04:01:08] [discord] Decade* [04:01:21] [discord] From what I've heard, Legacy Vector will be removed in 1.43 but I'm guessing WMF will fork it off into a separate skin [04:01:23] [discord] hopefully [04:01:28] What userscripts depend on Vector? [04:01:28] I've only had one issue with userscripts that was different on Monobook and Vector [04:01:39] Much less Vector and vector-2022 [04:01:50] [discord] Half of my userscripts on enwiki depend on old vector [04:01:59] [discord] The userscripts i use i should say [04:02:08] Agent : I mean, `?useskin=vector` still takes you to "legacy vector" [04:02:30] It might be split into another skin, but I do think they planned on removing by 1.43, or if thats not the next LTS, then the next LTS after 1.39. [04:03:12] [discord] They may plan, but doubt it would happen, unless they plan on dealing with tons of angry userscript devs [04:03:21] That's true also. [04:03:50] They've been "planning" parsoid for a very long time but it never makes it in as planned. 1.39 seems to finally be it though. [04:04:04] That already happened with deprecating old tokens [04:04:10] Wasn't Parsoid added in 35?\ [04:04:35] [discord] Parsoid been around since ve, maybe a bit before [04:04:52] Parsoid was rewritten, and the new version was included in 35 [04:05:08] Naleksuh: for VisualEditor, yes, but the parsoid in 1.39 replaces the MediaWiki built in Parser eventually, breaking almost all parser extensions eventually. [04:06:10] Uh-oh [04:06:17] https://www.mediawiki.org/wiki/Reading/Web/Desktop_Improvements?useskin=vector [04:06:25] This page says new vector is default on all Wikimedia wikis in July 2022 [04:06:35] Yes. [04:07:11] [discord] Idc about defaults [04:07:27] [discord] Theres alot of us on wmf who are stubborn and want to keep old vector, im not worried [04:07:29] Also, this page is using "editors" as a stand-in term for "registered users" [04:07:48] Yet another example of being out of touch with the community [04:08:07] [discord] Because thats how wmf has always referred to the community [04:08:18] [discord] They’ve called the community editors probably since 2001 [04:08:20] I like vector 2022 better than legacy. [04:08:37] @Zppix No, "editors" as a stand-in term for "registered users" [04:08:41] [discord] Set mode +b cosmicalpha [04:08:42] Implying IPs are not editors [04:08:54] Lol zppix. [04:09:19] [discord] Naleksuh, i’m telling you they’ve done that practically since 2001 [04:09:46] [discord] Editors is a term that includes anyone that makes an edit to a project [04:09:55] Uh-huh [04:09:59] [discord] Simply being registered does not make you an editor [04:10:23] But this page is implying that people who aren't registered are not editors; which is false because IPs can edit on all Wikimedia wikis but two [04:10:56] I understand what you're saying, but I think you are talking about something different than what I am talking about [04:11:13] [discord] They never imply ips aren’t editors [04:11:19] They do [04:11:24] [discord] Where [04:11:35] Instead of saying "only registered users can opt-in" they say "only editors can opt-in" [04:11:52] [discord] That doesn’t imply ips arent editors… [04:12:16] It does, because they're using "editors" to refer to registered users only, when really it means ALL users who edit, registered or unregistered [04:12:27] IP RIGHTS https://en.wikipedia.org/wiki/Wikipedia:IP_editors_are_human_too [04:13:23] [discord] They don’t infact i’m 99% sure ip editors can opt in this as well [04:13:51] [discord] Regardless like I said WMF has always referred to things like this, this way [04:13:52] Only by using `useskin` which doesn't count [04:13:59] This page wasn't written by the WMF [04:14:04] It's written by the idiots making this skin [04:14:17] Actually it was written by the WMF, ignore that [04:14:59] [discord] The reading team is a WMF team [04:15:00] [discord] https://cdn.discordapp.com/attachments/435711390544560128/984672001383891024/IMG_3467.png [04:15:40] Yeah, anyway, I don't know, English Wikipedia usually has it under control but they've killed a lot of stuff I liked [04:15:48] They made a change to diffs in May 2020 that you had no way of opting out of [04:16:13] Also, keeping it around doesn't mean maintaining it. Monobook is falling apart and most of the bugs are reported by me :/ [04:16:20] Anyway, I have to go now. Please keep Vector 2010 alive [04:16:39] [discord] Monobook is 21 years old. [04:17:06] [discord] Monobook almost 21 years old. (edited) [04:17:11] [discord] Is almost* [04:24:31] [discord] https://tampvan.miraheze.org/wiki/Pengguna:ChioGaming2007/bak_pasir [04:24:32] [discord] this is an example [04:24:32] [url] Pengguna:ChioGaming2007/bak pasir - Tampvan Wiki | tampvan.miraheze.org [05:14:36] Zppix : Is it borrowed from UseModWiki ? [11:30:15] [discord] Looks like the infobox works fine? [11:30:15] [discord] The text that you have used to call the infobox template is what is shown. [11:30:17] [discord] Are you creating another template that would create the infobox? [11:30:18] [discord] I believe since you are creating this template not under the template namespace, your {{{ }}} parameters get parsed literally as text [11:30:18] https://meta.miraheze.org/wiki/Template:%7b_ [11:30:27] [discord] @ChioGaming2007 [11:31:09] [discord] Nope [11:31:10] [discord] I change it [11:31:11] [discord] You can see in Templat:Infobox/type2 [11:32:36] [discord] There you created just an empty infobox without anything.... and so it is empty [11:32:45] [discord] Wait [11:32:49] [discord] https://cdn.discordapp.com/attachments/435711390544560128/984782184139341854/unknown.png [11:32:51] [discord] https://cdn.discordapp.com/attachments/435711390544560128/984782192683143188/unknown.png [11:33:38] [discord] Yeah i used module infobox [11:34:07] [discord] Yes, you have invoked The Infobox module and the infobox function [11:34:17] [discord] but without any text or anything [11:34:43] [discord] you have not invoked the infobox module with the infobox title [11:36:02] [discord] what? [11:36:02] [discord] Okay.. but try to check this [11:36:04] [discord] This is the bug I mean [11:36:05] [discord] https://tampvan.miraheze.org/wiki/Pengguna:ChioGaming2007/bak_pasir [11:36:06] [url] Pengguna:ChioGaming2007/bak pasir - Tampvan Wiki | tampvan.miraheze.org [11:36:15] [discord] sandbox [11:36:56] [discord] Like i said, it works? [11:36:57] [discord] https://cdn.discordapp.com/attachments/435711390544560128/984783221264900126/unknown.png [11:37:13] [discord] {{{NAMA1}}} is not parsed as an input parameter [11:37:13] https://meta.miraheze.org/wiki/Template:%7bNAMA1 [11:37:26] [discord] work yes [11:37:27] [discord] but the shape doesn't fit properly [11:37:33] [discord] since its under the sandbox namespace and not under a template namespace [11:37:34] [discord] Only test [11:38:16] [discord] Ok what shape doesn't fit properly? [11:40:18] [discord] the location of the template should be on the right [11:40:19] [discord] there are no borders or colors in the infobox [11:40:20] [discord] the placement of the text is not neat [11:40:59] Hello Tengen|zzz! If you have any questions, feel free to ask and someone should answer soon. [11:41:07] [discord] it should work like this [11:41:08] [discord] but why not on my wiki [11:41:09] [discord] even though I have imported the module [11:41:11] [discord] even those related to the infobox [11:41:12] [discord] https://cdn.discordapp.com/attachments/435711390544560128/984784272986603550/unknown.png [11:44:12] [discord] Ok, looking why the default styles dont apply [11:46:49] [discord] Copy styles from https://template.miraheze.org/wiki/MediaWiki:Common.css From line 355 to 461 [11:46:49] [url] MediaWiki:Common.css - Template Wiki | template.miraheze.org [11:47:16] [discord] to your wiki common.css [11:47:21] [discord] right [11:51:27] [discord] okay [11:51:28] [discord] it works [11:51:29] [discord] thanks [11:51:35] [discord] @Kozd [11:51:47] [discord] np [12:12:55] Hello Guest71! If you have any questions, feel free to ask and someone should answer soon. [12:19:44] Hi, [12:19:44] Wanted to ask, if I import a Wiki page (with contributions from 'User A', 'User B' etc.) into my Miraheze wiki. [12:19:45] Then, if I create new accounts with the same names 'User A', 'User B' in my Miraheze wiki, [12:19:45] will these new user accounts get associated with the ones from the imported Wiki page contributions or not? Or, in other words, will the imported Wiki page come up in the new user accounts contributions page? [12:21:23] [discord] It depends on when the user accounts are attached to the wiki. So let's say you create User A and User B on the new wiki before you request the import. In that case, edits are normally assigned. However, if you create User A and User B after the import is done, edits won't be automatically assigned. [12:22:56] Guest71 Agent has a point. I do this quite a lot. [12:23:27] Thanks.👍 [12:23:28] I was just about to import, but now I will make the user accounts first. [12:23:38] :thumbsup: [12:29:46] [discord] Naleksuh just saw your msg; i went to bed, what are you asking about when you ask is it borrowed from usemodwiki? [12:42:21] Another question, am I right in assuming that user accounts from an external Wiki cannot be directly imported into a Miraheze Wiki? [12:42:21] And that the accounts will have to be manually created locally? [12:44:12] [discord] Yes, you cannot "import" a user account from another wiki [12:45:09] 👍 [14:15:56] In my new Miraheze Wiki, I wanted to create new user accounts, 'User A' and 'User B', so that when I import an article which has been edited by 'User A' and 'User B', their contributions can be properly assigned. [14:15:57] However, two of the usernames are already in use on meta.miraheze (but don't appear in my wiki's Special:ListUsers). [14:15:57] Q1: The first user should be the same as the one whose edits I'm trying to assign, so will their contributions get automatically assigned even though they don't show up in my wiki's Special:ListUsers? [14:15:58] Q2: The second user is different, since I can't create an account with this exact username on my wiki, is there any other way to assign this user's contributions to them? [14:15:58] Perhaps, in the old wiki, changing username through Extension:Renameuser will work? [14:19:50] [discord] Guest71: Re: Q1: If a user doesn't show up in Special:ListUsers, that's because their account isn't locally attached. Have the user visit your wiki while logged in and our login system will create a local version of the account which will show up on ListUsers. Otherwise, their edits won't be assigned. [14:19:51] [discord] Re: Q2, if their username is already taken on the new wiki, that's fine. We can manually assign this user their edits. [14:22:09] The already taken username is the restricted name "WikiSysop", would that be a problem in the manual assignment? [14:22:35] [discord] No, it wouldn't. [14:22:51] 👍 [19:25:06] Zppix : Monobook