[00:44:06] Only transition weather I particularly don't care for is snow, but not quite melted or slush [00:44:18] in other words an inevitable morning of ice or several [00:44:45] dmehus You can disregard the question I left on the #cvt channel. [01:46:29] Never knew @k6ka was an English Wikipedia admin [01:51:12] https://cdn.discordapp.com/attachments/615786602454581249/929552858217594910/IMG_7344.png [01:51:24] He has the weirdest statuses [01:52:12] Ahh, I've been making a mockup of my wiki site [01:52:17] https://cdn.discordapp.com/attachments/615786602454581249/929553128586625104/unknown-24.png [01:52:26] I think its turning out good so far [01:52:32] ๐Ÿ˜„ [01:55:44] @Bukkit, yes and @MJL is a Scots Wikipedia administrator :) [02:02:30] MJL? Ah yes, I've seen him lurking on the Wikimedia server. [02:04:08] https://cdn.discordapp.com/attachments/615786602454581249/929556112993304658/Screenshot_20220108-230245-984.png [02:04:10] Very clear the scope. I accept. [02:06:10] Doug, I sent you a friend request on discord therefore you are not really active [02:08:08] :DoneMH: Accepted perfect; clear scope [02:09:26] Request approved. Pretty good. Purpose and description are a bit vague, but there is nonetheless a clear enough purpose, scope, and/or topic here. Please be advised this approval does not preclude other wikis from being approved and created that share this topic, provided they aren't 95-100% content forks of your wiki. Please ensure your wiki complies with all aspects of Content Policy at all times. [02:25:52] Looks like Agent Isai declined it? [02:25:58] looking [02:26:11] It's a perfect request! [02:26:13] /s [02:26:35] yeah no idea why Bukkit said that :P [02:26:56] dmehus: joke I'm guessing [02:27:00] Jooking doug [02:27:34] oh [02:27:45] @YellowFrogger, but is AmongUsYellow your alt? [02:27:50] Agent: oh [02:28:29] no no [02:29:20] Among us is a game, hence the character colors [03:21:33] oh [03:26:26] Doug, can you explain more in depth why my edit set itself to peanut [03:35:05] @YellowFrogger, well, for one thing, it wasn't "vandalism," but also, you don't really need to parrot something I've already said. Not sure if [[w:WP:PARROT]] exists, but if it does, it could be more that than WP:PEANUT [03:35:05] https://en.wikipedia.org/wiki/WP:PARROT [03:38:16] I'll probably try to improve so I don't make these types of comments again. [03:43:56] @YellowFrogger, yeah, that's great. ๐Ÿ‘ [18:14:23] dmehus You around for something? [18:15:36] ๐Ÿค” anyone else think the James Webb telescope has the miraheze logo in it?๐Ÿ˜… [18:16:09] O.o [18:17:53] DarkMatterMan4500, sure, can you go on IRC when you're around? [18:18:23] I'll be home soon, so I might not see the message when I hop on. [18:21:39] Also dmehus, I came to tell you that I have filed another report, and it's about The Parkee, again. [18:30:14] once you remove the second layer of petals....๐Ÿ˜† [18:30:14] https://cdn.discordapp.com/attachments/615786602454581249/929804272244244520/James_Webb.png [18:37:35] the Miraheze telescope :surprised: [18:39:08] dmehus I'm on IRC now. [18:39:08] [tell] darkmatterman450: 2022-01-09 - 17:21:16UTC tell darkmatterman450 DM me when you're around [18:47:43] Miraheze logo is a honeycomb [18:48:56] @Mystic NASA stole our copyright! We should sue for like 10% of their budget in damages ๐Ÿ˜„ [18:49:51] There are another 50,000 honeycombs in the world, this form is very common. [18:54:11] https://meta.miraheze.org/wiki/User:YellowFrogger/Miraheze_staff_by_number_of_edits [18:54:15] [url] User:YellowFrogger/Miraheze staff by number of edits - Miraheze Meta | meta.miraheze.org [18:54:36] Am I right? Are these all the staff? [18:55:32] Historically speaking, Staff = all SRE members so you'd need to include everyone in this page: [[Staff]] [18:55:32] https://meta.miraheze.org/wiki/Staff [18:55:36] https://meta.miraheze.org/wiki/Staff [18:55:36] [url] Tech:SRE Volunteers - Miraheze Meta | meta.miraheze.org [18:55:55] When the term Staff was used, it never included Stewards/Global Sysops [18:56:04] but the term isn't used anymore to refer to SRE [18:57:56] Damn it. I had even added their home country flags [18:58:50] I mean, you can rename it to say "Miraheze Stewards, Global Sysops and SRE members by number of edits" [19:00:14] that's what i'm going to do, but only admins can move it without creating a redirect [19:03:33] The term staff isn't used because we aren't staff [19:03:52] Also that's an EU flag [19:04:00] UK long left the EU [19:04:29] @YellowFrogger [19:05:49] I know, I'm inclined to move this page [19:14:22] sadly ๐Ÿ˜ฆ [19:45:59] dmehus Do you have time to check your PMs at this very moment? [20:03:31] darn, I'm not a staff :p [20:12:54] darkmatterman450, sure will do [20:13:48] Staff is a horrible term, and I will likely update that to replace it with a disambiguation page that points to relevant pages [20:14:02] Thank you, as I've been trying to point you in the direction of The Parkee on the `closinglogosgroupwiki`. [20:14:14] darkmatterman450, ok [20:14:31] The details can be seen on #cvt anyway. [20:15:33] Hey [20:16:08] @Hypercane Hi there. [20:17:46] Staff is unfortunately a popular term, especially for people unfamiliar with how Miraheze tries to detach itself from it [20:18:07] Yeah unfortunately [20:19:22] And in some cases to try and dissociate can be a bit of a problem, ie, literally anyone can be a volunteer, but obviously when one volunteer has jurisdiction to be an arbiter on any wiki, another is a technical manager, another is the treasurer for the platform/trust and safety (a traditionally staff role and in our case still fully appointed/largely non public in its details), one creates wikis and most cannot do any of [20:19:22] those things and maybe just volunteer a bit of time on Meta, it can be a bit confusing., [20:20:21] If anything Miraheze may have decentralized too far, where there are many groups to perform staff-y tasks but insist on a strong division that results in people being bounced between 'departments' (another 'staff-y' paradigm) and a line of ambiguity between the random volunteer and someone with jurisdiction to do what is needed. [20:20:48] If the intent is to be fully communal in focus and operation, Miraheze has some distance to go; at the same time it must avoid hurting usability in its efforts to decentralize. [20:22:08] Agreed, just consolidate all power in SRE and disband Stewards/CVT, all Meta roles including sysop and wiki creator and T&S/Board :P [20:22:12] that'll fix everything [20:22:25] Sometimes I wonder if I was more active and had more free time here would I have been like a global sysop by now. And the answer, was probably yes. [20:22:40] probably tbh [20:22:51] I'm sure anyone could be if they fulfilled the right conditions to be one [20:22:54] It's not too late, I just don't know where to start. [20:23:03] sometimes [20:23:20] Agent If that was for real, that would potentially destroy what Miraheze is valued for. [20:23:32] Yeah [20:23:42] darkmatterman450: Do remember that I'm sarcastic 90% of the times :) [20:23:45] so that was a joke [20:24:01] lol, getting rid of all the other roles [20:24:14] fun [20:24:16] Agent, I knew you were joking. I most of the time take some jokes like it's actually going to happen. [20:24:26] Great! [20:24:52] Personally, my approach is to somewhat detach from GS/previously CVT's exclusively CVT qualification, and focus on the GS capacity for global outreach and crisis resolution - largely leveraging the position as a forward responsibility. So where you may not catch much for CVT, you can still act in a global operative way (finding wikis and attempting to resolve issues as a user), getting the trust of the Meta community and [20:24:52] portions of the global one, and using that to leverage a request to become GS. [20:25:26] Ah okay [20:25:29] I think that's the underexploited aspect of what a GS can be; aside from just performing locks they have a jurisdictional responsibility to lighten the workload of Stewards, and in my own interpretation to also reduce the need for them to be involved in the first place. [20:26:11] I know I have the experience of a local admin, heck I've been one for 8 years now on one wiki. [20:26:28] The mechanical aspect of a GS isn't much really [20:27:02] true [20:27:07] like anything I guess [20:27:37] It's the trust of basic competence + trust in crisis handling; one's your ability to be a good GS in routine and the other is where you're actually tested, when the unexpected happens. So becoming one is getting faith for those things, staying one I think is being open to both avenues [20:28:19] Interesting, that does make sense honestly. [20:32:06] I know rights are not everything, and I learned that a long time ago. But that does not mean I can't have goals for myself. [20:35:41] There's nothing wrong in aspiring to have hats if you actually plan to use them and desire to truly help others [20:36:03] From my perspective, I would enthusiastically endorse @Hypercane for Global Sysop tomorrow. He's trusted, competent, shows incredible capacity for learning, strong analytical skills, and been around here along time. His chief drawback is his relative inactivity, globally and on Meta [20:36:22] so I would suggest re-engaging on Meta as a patroller or as a wiki creator [20:36:46] Thanks, that is actually a good idea too Doug. [20:36:56] np :) [20:37:57] Eh, I might re-request WC only when I engage in some relative time as a patroller first. [20:38:06] I think it would fail right now otherwise. [20:38:29] Yeah, it probably would [20:38:54] I was once a pretty good WC when I handled the requests, so I know have the capability at least. [20:38:54] We have many new users who do not know of your track record so lack of recent activity would SNOWball your request [20:39:31] True, they would accuse me of likely hat collecting, even though that wouldn't be the case. [20:39:36] Regardless [20:39:40] I will help in some other way for now [20:42:25] Imo rights are all about what they do to compliment what you would already do [20:42:48] in that respect I sometimes question the function of patroller as a unique 'hat' and function when its principles can be accomplished by any user [20:43:33] I think engagement globally, particularly for developing or problematic wikis would be a very strong aspect for any new global sysops to develop [20:48:54] The ability to patrol others edits used to be part of the autopatrolled toolset before being split into a new group: https://meta.miraheze.org/wiki/Requests_for_Comment/Autopatroller_group_split [20:49:00] [url] Requests for Comment/Autopatroller group split - Miraheze Meta | meta.miraheze.org [20:49:24] I remember that happening. [20:49:42] Honestly, I guess it made sense [20:58:18] Patrol marks imo are a very, very minor function [20:58:52] Perhaps I'm inaccurate, but it's my experience between myself and other users that things tend to be inevitably checked out anyway by various regulars, and what one patroller says okay for another might disagree with [21:05:54] Hopefully the 14th of this month comes soon. [21:07:04] Should arrive in roughly 5 days :p [21:07:05] I'm even requesting renounce [21:07:16] Let's pray [21:07:22] lol [21:07:40] Really [21:07:48] I do not entirely dismiss the possibility of a time warp of course [21:08:14] Very slow server, 10 minutes to load [21:08:18] Hm? Sorry if I did something wrong. Just trying to contribute to the conversation. [21:08:32] To load what? [21:08:42] All requests should timeout after 1 minute [21:08:46] s'all good [21:09:16] s'all, new word to add to my dictionary :P [21:09:17] 10 minutes is a stretch, but I have had some fairly routine tasks take long enough that I just decided to multitask tabs again >.> [21:09:35] Playing with my barrier? [21:09:38] Yeah it did a 502 when trying to publish my edit. [21:09:40] Probably not good for stability to tell the server to do 6 things at once instead of 1, but meh [21:09:49] It still went through somehow [21:09:51] what barrier? [21:10:00] Usually when that kind of error turns up the content isn't actually lost [21:10:06] Ah [21:10:09] It's only in the most recent spell I've had it actually wipe data [21:10:11] my language [21:10:18] language [21:10:25] ouch [21:10:41] That would suck, especially if you made a large edit. [21:10:42] no, not at all [21:10:48] I've long learned from forums that anything worth saving should be pasted in a doc before committing anyway ๐Ÿ˜› [21:11:00] That's a smart idea honestly [21:11:12] just play russian roulette and hope that refreshing does the trick [21:11:13] lol [21:11:35] might as well just queue up several edits at once [21:11:44] then when the server catches up it'll probably do them all finally >.> [21:12:40] I'm not sad about life [21:13:44] have you tried creating accounts "forcibly" from a wiki? [21:13:46] it's cool [21:13:50] wot [21:13:50] and relax [21:14:07] Can't say I've had the experience of forcing accounts out of wikis [21:14:14] he means force attaching CentrlaAuth accounts by assigning imported edits [21:14:21] Import wikipedia pages with full history, hence if you see account creation log it creates multiple accounts automatically [21:14:23] I [21:14:40] I think [21:14:41] idk [21:14:47] Easy way to unnecessarily clutter up your ListUsers :P [21:14:58] another reason why I prefer to homebrew things rather than import them from a conglomerate that's usually much too big for what I actually need [21:14:58] yeah [21:15:01] YellowFrogger, that should generally not be done unless you have a legitimate need for that template [21:15:10] Spambots did this without the owners' permission [21:15:15] Spambots did this without the owners' permission [21:15:21] Very unfortunate, then [21:15:39] It's one reason why having `centralauth-local` be an unrestricted user right post MW 1.36 did not make sense, to me [21:15:49] There's even ClueBot on my wiki, wtf [21:16:03] probably someone created a local ClueBot account :) [21:16:14] not necessarily the operator of ClueBot on enwiki [21:16:23] The glitch of import. doug [21:16:42] Ah, the English Wikipedia - one wiki I can honestly say I'm intimidated by [21:16:49] You might accidentally frame yourself in CheckUser if you import and assign edits to accounts so do be careful :P [21:16:59] oh dear [21:17:10] uh yikes [21:17:13] Me? [21:17:24] See, that can get ugly very quickly [21:17:28] Agent, yep that's true :) [21:17:45] dmehus, when you get the chance could you please check your PMs [21:17:51] Anyone who imports and assigns edits gets their IP attached to the user account the edits were assigned to [21:17:57] if no local account exists [21:18:00] Hypercane, yeah, sorry, will do, sorry for my delay in replying :) [21:18:05] You're fine [21:18:06] looks for the Phab task [21:18:12] Xaosk laughed at this [21:18:15] YellowFrogger, it wouldn't be a glitch in the import if ClueBot existed locally and you assigned edits locally [21:18:54] But there is a way to do this by importing. And I don't think there should be a punishment for users who use multiple imported accounts [21:19:05] and nino [21:19:11] Hypercane, yeah enwiki editors can be a bit BITEy to newcomers and they have a lot of policies, some of which conflict with each other [21:19:32] not sure what you mean, YellowFrogger [21:19:35] Hypercane, ty :) [21:19:37] Not only that, I'm afraid a simple mistake would be the end [21:19:38] lol [21:19:40] ร”nibus Wiki, Doug [21:19:44] maybe exaggeration [21:19:46] but still [21:20:01] The raw scale of wp policies is why I'm pretty much completely anti that scale of policies or direct imports/attempts to clone and/or rival wikipedia scope [21:20:04] https://phabricator.wikimedia.org/T191709 [21:20:05] [url] โš“ T191709 Checkuser logs SUL attachings caused by page imports under importer's IP/UA | phabricator.wikimedia.org [21:20:24] You could frame yourself accidentally if you cause a CA account to attach to your wiki so be careful [21:20:27] They're the organic growth of a decentralized expansion that is completely inappropriate for any other wiki and even for itself is not ideal [21:21:17] I feel like WP has so many policies it could be an encyclopedia in itself honestly [21:21:25] What exactly do you mean by "frame" [21:21:54] Your IP could come up in CheckUser if a Steward checks someone who you assigned edits to [21:21:55] You could be mistaken for one of those long-term abuse accounts [21:22:03] idk [21:22:08] nvm [21:22:12] YellowFrogger, edits imported by you for other users are associated to your IP. It's a CheckUser extension oddity [21:22:32] It's been a reported bug since 2018 so I doubt it'll get fixed any time soon [21:22:33] and thus it was discovered that raidarr is actually the civil alias of the noncyclopedia lta [21:22:45] Agent, oh wow? since 2018!? :) [21:22:51] Raidarr = LTA confirmed? :o [21:22:52] @raidarr lol [21:22:52] Ah, 2018 [21:23:02] raidarr = final boss of the lta [21:23:04] That was one of the darker times in one of my wiki's history [21:23:09] I kept getting vandals [21:23:12] And LTAs [21:23:12] The task to implement global blocks has been open since 2008 so... [21:23:13] lol [21:23:19] * dmehus wishes he knew Raidarr spoke Italian :P [21:23:29] Le croissant [21:23:31] 2008? [21:23:32] that's Italian, right? [21:23:33] I wish I spoke italian tbh [21:23:35] dmehus I've been meaning to ask about that. If I imported something over to another with the users being assigned to said edits, would the IPs pick them up? [21:23:36] Dang, I was young then [21:23:41] Damn, I hope that doesn't happen, because I love doing it, and I've done it several times: https://onibus.miraheze.org/wiki/Especial:Lista_de_usu%C3%A1rios I would never hurt Miraheze like that. And maybe I would explain it to me, if possible. [21:24:12] [url] Lista de usuรกrios - ร”nibus Wiki | onibus.miraheze.org [21:24:16] I know I imported a page with an odd 800 revisions yesterday, oops :p [21:24:48] I've recently been importing pages with users being assigned to the edits. [21:24:59] dmehus, I didn't realize, but that one user's wiki is not private. [21:25:03] darkmatterman450, if users' accounts are attached locally to your wiki when you import the page(s) and choose to assign edits locally, they'll be attributed, correctly, publicly to the users, but the private technical details will be attributed to you, yes [21:25:07] yes [21:25:09] Eh, my point still stands [21:25:13] yes [21:25:25] my private wiki is only semi private :p [21:25:34] Semi-private? [21:25:35] But it is not possible to edit the wiki of fictia [21:25:37] dmehus Oh. And sorry if I'm bugging you about what I wrote on the #cvt channel. [21:25:39] Interesting [21:25:44] Miraheze users can view. [21:25:57] Heck, they can use talk pages as they like. [21:26:03] but bear in mind, for the most part, this is not a big deal, as (a) Stewards are not robots and can use their analytical skills to see this and (b) the data is not retained for a long term (see [[Privacy Policy]] [21:26:03] https://meta.miraheze.org/wiki/Privacy_Policy [21:26:31] Lmao, I know the Stewards aren't robots. That would be silly. [21:26:41] I still think blocking users in private wikis is pointless. [21:26:44] Dougbot [21:26:47] idk man, sometimes they act like bots [21:26:49] Hypercane, yeah, I agree [21:26:52] Agent, lol [21:26:55] mass blocking IPs under the guise of using "scripts" [21:26:57] <.< [21:26:57] Raidarr, lol [21:27:07] @Agent: "Le croissant" is French [21:27:09] And just unnecessarily giving people block records [21:27:12] We already have Voidbot, so it's not a stretc to say that is true void [21:27:18] Tintle: lies, it's Spanish [21:27:24] Agent, MassGB.js is broken right now since the MW 1.37 upgrade :( [21:27:25] Block records are treated rather callously depending on the community [21:27:28] no, it isn't [21:27:30] so I haven't been able to use that [21:27:31] I remember when the one private wiki's admin blocked me [21:27:33] dmehus: oh, that sucks :( [21:27:38] Luckily it wasn't indefinite [21:27:49] Glad that after I created a page calling admins "staff", rating their edits, they created a page about "staff", including even wiki creators. Nice. [21:27:50] I was just on one wiki that transferred to Miraheze and made a practice of blocking any unknown usernames because on the last solution they used, unknown = spam [21:28:20] I just hated having it on my record [21:28:20] It was amended to say that you could be talking about them but that we have no Staff [21:28:33] raidarr, yeah, that's something I want to engage with new wikis about, so if you want to assist with this (a local talk page message would be good), that'd be super appreciated :) [21:28:55] Let them know how CentralAuth works, how private wikis work, and what the Code of Conduct means, essentially [21:28:57] imo, there should be a global policy against banning users where they've done nothing other than visit the wiki so that they can be overturned if needed [21:28:58] The incident I refer to was resolved quite amicably as I was able to find their discord server and discuss it with the local administration [21:29:03] We don't have "staff", but the stewards, gs, wiki creators, interwiki/translation administrators, must be a staff [21:29:11] All about interfacing and communication for the most part [21:29:13] This honestly, @Agent [21:29:33] I mean, there's no rule saying you can't block someone for any other reason. [21:29:42] It made me have a record when I did nothing so lol [21:29:44] Agent, technically, we have Code of Conduct, but I do prefer engagement first, but we do have the capability to overturn local blocks, including GS, tbh, if delegated to do so [21:30:16] If specifically solicited to in any case, what a local wiki does with blocks is otherwise more or less their business [21:30:48] Raidarr, are you agreeing or disagreeing with me? I'm confused :D [21:30:50] Part of the problem with QP's blocks is that it was traditionally operated like an interlaced network before it even had a central wiki [21:31:28] dmehus: where in the CoC does it say bans can be overturned if handed without reason? [21:31:30] Raidarr, well yes, but in the past specifically, many GP blocks and their sysops' failure to assume good faith were themselves CoC violations [21:31:31] Qualitipedia shouldn't even block a user on all their wikis because he was blocked on one wiki, Wikimedia doesn't even do that [21:31:49] It only generates complaints [21:32:01] Indeed, Wikimedia doesn't hand out global blocks easily as it believes in fresh beginnings [21:32:05] Agent: Not specifically, but blocking without cause and failure to assume good faith may constitute a CoC violation [21:32:15] Pretty sure my record on CA is clean now [21:32:22] Thankfully [21:32:28] exactly [21:32:45] I usually would block someone on inappropriate behavior of if they are a sockpuppet of a certain banned editor. [21:32:55] by the way, while we're in an editing spree [21:32:55] dmehus: Can you edit the CoC to remove any mentions of the CoCC? [21:33:50] Agent, possibly, but do note that the CoCC's functions have been fulfilled by Stewards, so Stewards can be convened to serve as a final appeal venue or arbitration/dispute resolution body [21:34:14] Speaking of sockpuppet, dmehus did you get a chance to see the #cvt channel yet? (I'm surprised you haven' [21:34:30] *haven't answered my question on that yet.* [21:34:43] Damnit, I typed too quickly. [21:34:47] Try searching for a dash " - " without Database error [21:34:48] darkmatterman450, ack (and I mean like "ahhh!" not "acknowledged!") [21:34:51] dmehus, I would say I was adding to it; from the GS perspective at least I would have to be directly solicited 'by the community' (in practice that's a high bar for me preferably deferred to stewards) and even then it's more about informing them best practice and giving them the chance to reverse course; unless a direct global policy violation is committed there should be a minimal interference, even if there is an arguable [21:34:52] I'll get to it shortly [21:34:52] possible CoC violation ie, an excessive block. As for QP, indeed the nature of the blocking has historically been quite atrocious and even now I would humor old 'black sheep' making an appeal to me since in many cases they were actually antagonized by the management of the time. QP's blocks are a very crude form of 'local lock', whereby activity on one wiki is considered for the user's presence across the 'platform', which is the [21:34:52] dmehus: yes but the CoC already says "Stewards/Code of Conduct Commission" so referencing a body that doesn't exist anymore alongside the body that does is a bit strange [21:34:53] jurisdiction of that particular QP admin (usually one of the admins who end up promoted everywhere because they're well known and considered a 'default' to promote). Likewise many of the admins who were promoted were appointed with similar logic; regardless of local activity, some promotions would replace demoted/retired users even if the promoted users were never active on certain wikis. [21:35:17] lol [21:35:17] https://cdn.discordapp.com/attachments/615786602454581249/929850842494926878/unknown.png [21:35:28] big lag [21:35:45] @raidarr, oh, reading your reply that Agent posted in the screenshot [21:35:52] When going through QP admin ranks I encountered quite a few examples where admins either never contributed locally or made very few edits, in either case nothing to warrant an admin title. In certain cases even a standing bureaucrat could be considered. [21:36:01] >  darkmatterman450, ack (and I mean like "ahhh!" not "acknowledged!") >  I'll get to it shortly That's good. [21:36:02] and fair enough, yeah [21:36:36] Privileges could be like that, except for blocks, because a second chance is better. Did you see that guy: Mariobobfan? [21:36:49] I'll be unblocking his cross-wiki blocks. [21:36:59] MarioBobFan was already handled. [21:37:00] I will admit I used to not recognize when people meant ack as an onomatopoeia vs ack as in "acknowledged" :P [21:37:14] A user should only be blocked on all wikis when he commits Cross wiki block [21:37:42] Yeah, but I'll delete most of his blocks until it goes down to just one. [21:37:57] Wait, hold up. [21:38:00] MBF also has a bit more of a problematic nature; he did invoke ire from the community on multiple wikis, not just one. [21:38:13] Oh yes, that. I forgot about that. [21:38:14] Good, I want to see what he'll do after this, after spending two months begging for an unlock [21:38:17] Raidarr, that's good [21:38:35] how [21:38:42] He also doesn't have the scenario Bluba had of being unfairly antagonized by standing admins; MBF does have an unfortunate strong CIR streak that must be considered, making his case somewhat less good than Bluba's. [21:38:45] I'd suggest the QP wikis need to update their Main Page to explain in bold text to use edit summaries when making bold changes [21:38:51] so as to avoid blocks [21:39:05] and also they need to stop the practice of immediately revoking the user's talk page access [21:39:07] in FANDOM? [21:39:07] That's a good suggestion. [21:39:11] but they are doing better [21:39:17] Edit summaries are referenced in a dramatically trimmed version of the rules I produced on my CGW sandbox, I'll find the link. [21:39:29] raidarr, that's good :) [21:39:30] okaey [21:39:33] Allistayrian will sometimes overexaggerate the block reasons. [21:39:33] It's open to anyone's input; since it's just a trim of existing rules, it's still somewhat of a mess and needs clarity fixes. [21:39:46] I almost always leave an edit summary now-a-days anywhere I go [21:39:49] Alli needs a few paradigm changes. But I digress. [21:39:57] Though when I was newer I didn't do that [21:40:11] He's a consequence of a far harsher form of administration that was endemic from earlier times, particularly early 2021. [21:40:14] Hypercane, same. very rarely do I not use an edit summary (inserting or removing a line break is one exception) [21:40:33] who? I'm losing the conversation here [21:40:40] Drafted CGW revision, retaining the gist of rules I felt were worth in some form keeping, while dumping all that were redundant, unnecessary and so on. https://crappygames.miraheze.org/wiki/User:Raidarr/sandbox [21:40:44] I guess I can say I've learned a lot in the past 8 years [21:40:49] [url] User:Raidarr/sandbox - Crappy Games Wiki | crappygames.miraheze.org [21:40:51] almost 9 [21:41:14] a [21:41:28] Hypercane, wow 8-9 years? [21:41:30] Allistayrian, a prolific administrator on the game wikis who's unquestionably the best in terms of using his powers to administrate, but needing work on discretion and proportionate response. [21:41:35] does that include your Fanom period? [21:41:40] it does [21:41:54] I joined my home wiki all the way back on May 18, 2013. [21:41:58] Allistayrian is an excellent content contributor, and one of the better sysops, but yeah he does revoke TP access too quickly [21:41:59] There's a few conversations going on here, easy to get lost >.> [21:42:12] how'd this even start lol [21:42:16] I would definitely prefer him to MarioMario456 :P [21:42:21] It will be like that in July. It started back in July of 2013. I wasn't around when it was created. [21:42:29] Hypercane, ah [21:42:41] Tbh, Mario for his flaws did do a few things on the managerial side that I thought were preferable to fellow oligarchs of his era [21:43:07] Oligarchs is about right [21:43:23] In particular when I quite literally blasted qualitipedia management when I first entered, he was the first one to respond with statements and acts of actual change [21:43:29] and yes he did do a lot of mopping...perhaps a bit much in some areas [21:43:39] Also his questionable behavior in July was when it caught Trust & Safety's attention. [21:43:52] Minor, in the bigger picture of what he did and how he did it [21:44:08] That incident was symptomatic of how he approached things in general, often with good intention but problematic execution [21:44:20] yeah, I'd agree with that [21:45:03] He was also more likely to consult with the community before making a substantial change in content or policy, something I cannot say for his comrade [21:45:21] do you mean DeciduousWater534? [21:45:40] Nah, frankly Deciduous was a bit of a passive figure in terms of policy and content decisions [21:45:54] if so, yeah, I agree, though DeciduousWater534 was usually more forgiving, they did have a fairly inconsistent approach to blocking [21:45:56] Rather I mean Duchess, the 'first among firsts' leader when I joined. [21:45:57] oh [21:46:01] yes [21:46:02] MarioMario had a foul mouth. [21:46:04] DuchessTheSponge yeah [21:46:25] He said "shit" in everything [21:46:33] jajaja / ahhaha [21:46:37] Deciduous most prolific changes I have come across are mainly minor, but often decent tweaks at a policy level and his management of inactive users/redundant rights [21:46:48] But of course, deciduous is still in power, just under a different name :p [21:46:57] yeah [21:47:16] I'm lost in the conversation, sorry [21:47:26] speaking of which, I've not seen or heard from sephspacewiki much lately [21:47:28] Now I'm basically talking about QP top management politics [21:47:40] From what I heard that wiki combusted, haven't followed up though [21:47:47] or Inkster/Inkster socks, for that matter [21:48:01] Doug, do you think humor wikis can do articles about other wikis? [21:48:14] laughing / mocking [21:48:24] YellowFrogger, yes that's fine [21:48:29] we have some of those [21:48:36] I imagine inkster moved on [21:48:39] but just be mindful of Content Policy [21:48:42] As long as it doesn't devolve into personal attacks then it's fine [21:49:51] Going over QP comments with a comb and eliminating less tasteful ones is going to need to be one thing once comments are restored >.> [21:49:52] @raidarr, looks like it's in deleted wikis, https://meta.miraheze.org/wiki/Special:ManageWiki/core/sephspacewiki [21:50:00] and create a wiki mirror of encyclopedia dramatica? [21:50:05] Yeah, the wiki went under as I recall [21:50:11] [url] Manage this wiki's core settings - Miraheze Meta | meta.miraheze.org [21:50:12] is fine? [21:50:27] YellowFrogger, Encyclopedia Dramatica, oh no [21:50:34] A mirror of ED implies a content scope that definitely violates content policy in several aspects [21:50:40] Grounds to decline immediately [21:50:58] we've had wikis that were closed and is one of the main reasons we have Content Policy [21:51:05] yes, it's basd [21:51:27] https://meta.miraheze.org/w/index.php?title=Template:Partly_done&action=history [21:51:28] [url] Revision history of "Template:Partly done" - Miraheze Meta | meta.miraheze.org [21:51:29] vandalism [21:51:38] the reception wikis do have a few community ties with ED [21:52:09] Previously the management we discussed above overlapped with membership of ED, and Mario has been an admin for ED long into his time as a bureaucrat on QP [21:53:09] @Agent, what's your computer? You was supposed to have left the vandalism for me to reverse. slow server๐Ÿ˜ ๐Ÿ˜ค [21:53:31] Ed is an outlaw wiki [21:53:43] My computer is a bit overpowered to be quite honest [21:53:45] and for no reason [21:54:15] Now, why do these guys keep adding pictures of pen1s to the pages? Do they like one? [21:54:44] they're probably in school, bored and don't like miraheze very much [21:54:55] on a Sunday? [21:55:12] in school in the broader sense [21:55:20] ah [21:55:29] or someone who wants to make fun of it inside an cyber cafe [21:55:44] I was about to say, someone must be really borned in Sunday school in order to be doing that while in school [21:55:51] Not impossible [21:56:11] I imagine people 'in school' is where a majority of less desirable edits let alone vandalism are from [21:56:22] The server is very slow. [21:56:23] for me [21:56:43] extremely, yes [21:56:44] I feel like this comment is a case of 'you need a different phrase here' [21:56:45] https://cdn.discordapp.com/attachments/615786602454581249/929856241910575114/unknown.png [21:56:52] Raidarr beat me to an edit even though I used Twinkle :P [21:56:56] even test3 is having a hard time [21:57:11] It's "smart" people who do this offline at school, they don't even show their personal ips [21:57:14] Agent has a modern sniper rifle and I'm using a well maintained musket [21:57:36] after refusing a respectable winchester (rollback) :p [21:57:52] I went to revert the editing of this ip, when in fact I hadn't saved any edits, I hadn't understood anything, so I went to see that it was you who had reverted [21:59:01] And @dmehus all these important pages should be partially protected [21:59:13] chesterfield [21:59:39] I was thinking about that, autopatrolled for voting templates and other commonly used ones [21:59:50] it's [22:00:05] Even just 'logged in users' would be a very reasonable step [22:00:07] The unprotected Support and Oppose presets could not, [22:00:17] That wiki has since been closed and deleted. [22:00:19] because they are very used [22:00:48] to be quite honest, the entire Template namespace should be protected to requiring "editsemiprotect" which all autoconfirmed users have [22:00:51] dmehus: ^ [22:01:03] At barebones least logged in users [22:01:32] In which case, AP for key templates such as support, oppose and so forth [22:01:39] I think even the noticeboards, in my opinion [22:01:40] autoconfirmed to prevent IPs from making throwaways to vandalize :P [22:01:49] Noticeboards are more tricky [22:02:15] Yeah I agree [22:02:19] Autoconfirmed is still reasonable of course, but IP editing does seem to be desired traffic to keep open in good faith - but it certainly doesn't need access to templates and the like [22:02:33] But if a user wants to report it, just create an account, it's very easy [22:02:42] Not always :p [22:03:03] Agent, I did wonder about that yeah [22:03:06] Then again, often when it isn't it's because the IP was struck by some block or another anyway [22:03:06] 90% of IP edits are vandalism [22:03:13] easy change via ManageWikiNamespaces [22:03:32] Wikipedia had the same question a while ago, and from what I recall a majority of IP traffic was not vandalism [22:03:34] this i think [22:03:36] Different contexts though [22:03:52] And IPs can never be blocked indefinitely because this [22:04:19] I've never considered them a very reliable metric anyway tbh, at least whenever determination is involved [22:04:53] There are many accident cases where an innocent person has his ip blocked [22:05:13] and open proxy has to be blocked for a long time, just [22:05:59] Earlier community experience with heavy handed IP blocks that didn't solve the actual problem but frustrated legitimate users gave me a pretty long term grudge against them, though the way they work on Miraheze (soft blocking with open contact) is a different matter [22:06:54] https://ipcheck.toolforge.org/index.php?ip=76.115.13.40 It's not a school IP, according to this. [22:06:55] [url] Log in - Meta | ipcheck.toolforge.org [22:07:14] Command sent from Discord by YellowFrogger: [22:07:15] , and IPs, owners may be different (change) [22:07:28] ISP is Comcast Cable. [22:07:36] This guy is crazy then, to edit with his own IP [22:08:18] The problem with that is, anybody could be using that IP range for about any type of nonsensical vandalism you could ever think of. [22:09:43] I've just locally soft rangeblocked it for now [22:09:51] To some extent I've loosened on IPs particularly with regards to isolated cases; they can be a useful deterrant [22:09:57] but do advise if you see that IP vandalizing other wikis :) [22:10:10] ok ๐Ÿ™‚ [22:10:10] and Raidarr or I (or another Steward/GS) can take care of it [22:10:17] Speaking of which, you have a job to do, right? [22:10:18] And often playing whack a mole is probably better than 'well it's an ip, gotta let it go' [22:10:28] DarkMatterMan4500, yep :) [22:12:38] dmehus Well then, I suppose my CLG report from today could use some looking at. [22:45:20] * RhinosF1 has to attend a 2.5 hour relationships & consent talk tomorrow [22:57:38] RhinosF1, oh guessing it's a mandatory school lecture [23:04:14] Yes