[00:15:16] What site is this? [00:26:50] hi [00:26:56] how do i install twinkle as a gadget [00:26:57] how do i install twinkle as a gadget [00:26:58] how do i install twinkle as a gadget [00:26:59] how do i install twinkle as a gadget [00:27:00] how do i install twinkle as a gadget [00:27:01] how do i install twinkle as a gadget [00:27:01] how do i install twinkle as a gadget [00:27:02] how do i install twinkle as a gadget [00:27:03] how do i install twinkle as a gadget [00:27:04] how do i install twinkle as a gadget [00:27:05] how do i install twinkle as a gadget [00:27:06] how do i install twinkle as a gadget [00:27:07] how do i install twinkle as a gadget [00:27:08] how do i install twinkle as a gadget [00:27:09] how do i install twinkle as a gadget [00:27:10] how do i install twinkle as a gadget [00:27:11] how do i install twinkle as a gadget [00:27:12] how do i install twinkle as a gadget [00:27:13] how do i install twinkle as a gadget [00:28:33] yes [02:04:17] Calm [02:04:33] Special:Preferences? [02:04:39] But not need to flood [02:26:46] Since when has Agent had op access/ [08:24:33] Since they became a member of staff [08:50:17] sees the word 'staff' 😠 [08:50:30] I employed by Miraheze :P [08:50:39] Don't forget my $400K salary [09:10:13] I still have no idea what the collective term is, its just easier to say that [09:24:37] let's invent new term [09:25:09] I keep thinking "staff" but always struggle w/ alternative [09:25:43] and just end up w/ sys/high admins [09:25:59] The term "staff" is a mess [09:26:09] SRE is best [09:26:13] [[Staff]] explains who some consider to be "staff" [09:26:13] https://meta.miraheze.org/wiki/Staff [09:26:13]

https://meta.miraheze.org/wiki/Staff [09:26:14] [url] Staff - Miraheze Meta | meta.miraheze.org [09:26:23] The term staff is awful [09:27:36] it doesn't stick nor explains anything to newbies [09:30:29] "admins" seems more meaningful but easily blends w/ local admins [10:47:46] If the people with op access are not staff what is the name? [10:48:27] That means "engineer" [10:49:14] 🤷‍♂️ [10:50:33] Like Legroom i struggle too with the name. People who makes announcements but are not engineers could be announcers 😄 [10:57:28] keep in mind that the community is international too [11:23:26] I try to use 'global operatives' or 'officials' as terms, not that they're much better depending on the context [11:24:43] And inevitably people will fall back on staff as a simple catch-all that's ubiquitous and does suit the function, even if in many cases the staff are simply elected volunteers, but clearly saying 'volunteers' lacks stick and also uselessly overlaps with cases where a volunteer cannot technically do something that someone is looking for, and [11:24:44] requires... "staff" capabilities [11:37:30] not to mention that people coming from FANDOM bring the term here [11:40:33] Oh yes, it's a paradigm that's hard to drop [13:22:36] Global operatives sounds like they are inside Call of Duty, Raidarr [13:22:49] Call of Duty: Miraheze [18:04:25] Battlefield Miraheze [18:07:59] Miraheze - The awesome project nobody knows how to pronounce. (tm) [18:09:14] miura-hizi [18:09:48] Mir-uh-heez [18:09:55] is how I say it [18:10:00] +1 [18:10:06] you need to make an .ogg file, a 2 second audio where a "neutral" voice speaks the name and upload it to wiki. like they do en wiktionary.org pages [18:10:27] RfC: Establish official prononciation for Miraheze [18:10:37] ;) [18:10:42] Agent: Never! [18:10:55] but you know what.. I have the answer [18:11:12] first step is you need to break it down into its parts, mira and heze [18:11:25] then you find out those were server names at wikimedia once [18:11:33] then you find out the naming policy they had back then [18:11:38] and that tells you these are star names [18:11:47] now you lookup the Wikipedia articles with the lists of stars [18:11:50] RfC: deliberately keep it as vague as possible [18:11:58] and find them.. and then from there you link to Wiktionary page for the word [18:12:09] and if you are lucky, it already has the .ogg [18:12:19] but as a minimum it has the "pronounciation code" thingie [18:12:27] and then you combine the 2 again.. and there you go [18:12:29] :p [18:12:31] raidarr +1 [18:15:47] pronunciation of Miraheze [18:15:48] https://cdn.discordapp.com/attachments/435711390544560128/938860336797339709/Normale_03_02_2022_1515 [18:20:04] Мирахэзе 👀 actually the last part does sound funny for Russian lol [20:30:34] mutante: the old star names were nice [20:30:46] A fair few special names still exist [20:31:37] mira was the codfw deployment host [20:32:01] heze was a bacula storage server [20:32:39] Star names were codfw [22:35:30] RhinosF1: yes, the "misc" names are going extinct. everything is supposed to be a cluster of at least 2 hosts now, (i mean, that [22:35:39] 'ts true, a single server is usually bad [22:35:53] but that also means then the names becomes service1001 [22:36:00] and no more fun names [22:36:19] bacula is also backup1001 now and so on [22:36:29] and mira is deploy1002 [22:36:49] so if you were to create this project again today, it would be called "backup1001deploy1002.org" [22:37:51] I introduced the star name convention once because there is not such a low limit as "chemical elements". we ran out of chemical elements in the other DC [22:40:09] mutante: yeah, redundancy is great [22:40:16] But I like cool names too [22:46:33] I agree with that :) [22:46:49] nothing keeps you from having "mira" and "heze" and still do HA-failover [22:47:00] 2 servers for one service though