[00:26:32] at least this issue isn't bad as db141 [00:27:03] i remain hopeful that the images will soon be fixed [00:27:15] same here [01:07:13] It's not as bad as the db141 debacle if there is no data loss. Data that is safe but inaccessible is better than data that is gone forever. [01:15:02] Does anyone know the answer to this question here? [01:15:20] True. [01:28:53] Don't know, sorry. [01:30:47] yeah, you'd specify the name [02:50:58] how can i post a server invite [02:52:22] This might be of some help to you. @Indy [02:53:28] epic [02:53:36] Indeed so [03:16:57] Any updates, fellas? [03:21:23] nioe [04:22:06] Unfortunately nothing new just yet to report. [04:57:28] Hello I come from fandom, they deleted and blocked me and my fandom wikis. [05:18:53] Me and my friends [05:19:20] and you want to create wiki on Miraheze? [05:20:26] as long as it doesn't violate Miraheze's content policy and other rules you'll be fine [05:21:47] if you managed to save wiki dumps from FANDOM you can import them to Miraheze [05:38:02] Okay but they’re gone gone [05:40:28] that sucks, sorry man [07:20:01] Yeah [07:21:57] Yeah, Fandom is getting crap. But if your wiki doesn't break any rules, we'll gladly accept you on Miraheze. [07:36:14] It really doesn’t I was inspired by someone. I always put the characters to the owners and such. [07:36:51] Other Characters and Media are put to their rightful owners [07:44:09] Hi all, I'm a moderator on AVID, figured I'd join here to keep up to date with the Cloud11 issues [07:46:18] Welcome! [08:03:29] [1/2] > getting crap [08:03:30] [2/2] > getting [08:03:34] it IS [08:06:41] I credit to all the owners of media and cartoon characters I use. [08:17:10] Hello 🙂 Where might I direct my request regarding a URL change of my Wiki? [08:17:22] [[Phabricator]] would be the venue [08:17:22] https://meta.miraheze.org/wiki/Phabricator [08:17:23] [08:22:51] Yeah, I admit it, it's unrecoverable. [08:36:36] Just wanted to share my knowledge and ideas [08:50:52] Of course. [09:06:50] And some more [09:07:57] Proof I’ll never be liked there [09:08:17] Why don't you create a wiki on Miraheze? [09:08:38] Okay [09:09:23] What subject would you like to create a wiki on? [09:09:45] No sure [09:10:23] On what theme then? Entertainment? [09:11:18] What was your fandom wiki about before? [09:21:04] Cartoons [09:21:27] All the cartoons or one in particular? [09:25:32] All cartoons [09:27:51] Yes, so Fandom must have considered that the topic was too general, and duplicated all the wikis specialized in a single cartoon. [09:28:02] Hm [09:28:25] But Miraheze will accept the topic and allow you to create your wiki, the rules are more flexible. [09:35:33] Thanks [09:37:07] @AlienMoth Here for request: https://meta.miraheze.org/wiki/Special:RequestWiki [09:37:18] Thanks [09:56:54] The announcement of allying with Wikiforge is interesting [10:53:21] so uhhh, what is that wikiforge thing? [10:55:32] some wiki farm or something [10:55:43] im not really sure [10:57:08] you can check out #miraheze-meetings cuz they're talking about that there [10:57:14] thanks [10:57:17] #miraheze-meetings [10:57:23] oops, forgot command [11:00:46] [1/3] The announcement tells something about the wiki. Also there is this Request for comment. [11:00:47] [2/3] The vote section is at the bottom of the page: [11:00:47] [3/3] https://meta.miraheze.org/wiki/RequestsforComment/Premium_offerings [11:01:28] Also in the channel #meetings you can meet and talk about the annoucement [11:02:42] Seems like the RfC is still a draft, so can't really comment there for now [11:05:32] Just read it, I can't say I like that idea [12:32:24] Orange_Star: anything in particular you don't like? [12:34:54] I mean, there's not really anything wrong with the service itself, I can see businesses appreciating being able to use their own SSO logins and things like that [12:36:42] My concerns are that this goes against what I though Miraheze stood for, is ultimately about using the Miraheze brand for some third party to financially benefit [12:37:02] we would benefit [12:37:26] Miraheze not so much, I could definitely see wikiforge appreciating being able to use the MH brand [12:37:58] It gets their foor in the door and gets them an initial audience [12:38:20] There wouldn't be financial benefit [12:38:31] All surplus revenue after server costs would go back to Miraheze proper [12:39:14] After server costs and after paying employees right? Or would it be volunteers too? [12:40:08] Well initially, it'd be volunteers. If paid devs want to be considered later on, it could be something done [12:40:13] That's a good question that should be covered in the page [12:40:44] I mean, if there's enough revenue that's being generated for paid devs, I'd expect them to also contribute to things like CreateWiki and ManageWiki to improve those extensions [12:41:08] so WF wouldn't be selfish and would contribute back to Miraheze proper [12:42:03] Ooh I see, so it would be exactly like miraheze, just a different team and paid. In that case, how do we know that a volunteer team will have enough capacity for that project? I understand that part of the problems miraheze has is server costs, but it's also the fact that with volunteer staff, availability is limited, right? [12:42:47] I'm ok with the idea in general, I'm just worried about the feasibility 🤔 [12:45:12] Especially since as soon as it's a premium service, it will be in competition with for-profit companies, so why should someone choose WikiForge over a company that does have paid staff and, therefore, has quicker reaction time when things go wrong and can provide better and faster customer support? [12:47:59] Adding to the questions by Ondo, the amount of people that are going to work on Wikiforge is potentially picked from the same pool of people that could volunteer in Miraheze? @Agent [12:50:49] oh [12:50:57] just learning about WikiForge now [12:51:20] <2x2Master#7039> Is literally anyone here gonna fix the image problem on the wiki [12:51:27] <2x2Master#7039> The pcb wiki uses a fuckton of images [12:51:27] @2x2Master Watch your language. [12:51:35] ignore the bot [12:51:48] which problem? [12:52:06] They are working on it, see #announcements and #Images Not Showing Up (Unauthorized Access?) [12:52:06] The problem with Cloud11 I assume [12:52:11] <2x2Master#7039> Whatever this is [12:52:49] [1/2] it's probably the thing with cloud11 and swift [12:52:49] [2/2] I'm not part of the staff itself so I'm not sure about the progress [12:53:02] [1/3] Give them time [12:53:02] [2/3] It takes more than 30 seconds to solve issues like this [12:53:02] [3/3] If I had a dollar for every person who demanded it be fixed now I'd be rich [12:53:21] Last I heard things weren't exactly going well [12:54:04] Void posted an update at phab https://phabricator.miraheze.org/T10717#216236 [13:28:27] the worst thing about the outage is that [[mh:backrooms:Level Fun]] is broken 😦 [13:28:27] https://mh.wikipedia.org/wiki/backrooms:Level_Fun [13:28:27] [13:30:35] also [13:30:40] WHAT THE HELL IS THIS CSS [13:31:37] CSS is a really good game (https://en.wikipedia.org/wiki/Counter-Strike%3A_Source), what do you mean /s [13:31:49] God that hurts my eyes [13:32:26] dark mode is broken on most skins :p [13:32:47] and oH [13:33:09] i'm blue dababa dee daba die [13:33:50] i mean monaco as well [13:37:53] welcome to reception wiki design [13:37:59] it's notoriously terrible [13:38:11] i don't remember them looking this ugly [13:38:38] that was a popular design for a majority of reception wikis, the rest were either unstyled or just plain strange [13:38:49] the character wikis are the only ones I would say have got it right [13:39:00] backrooms wikidot was just yellow for almost a year [13:39:14] ah reception wikis [13:39:16] and some people actually liked it 🤷 [13:39:23] I tried to make an alternate that was a little more thought through, but even that wasn't very good [13:39:28] the wikis that make tables [13:39:33] a main page [13:39:37] my attempt is the ones with more lines and styled header buttons [13:40:07] the main page system was always horrible and I never did figure out an arrangement that I liked for them [13:40:38] that is another thing I think the character wikis have got right [13:40:44] i mean it's pretty ok for 5 12 year olds [13:40:57] it was an effort [13:41:04] it probably worked on the designer's screens [13:41:15] Rip mobile users [13:41:23] yeah, mobile was always screwed [13:41:30] they might've been using school chromebooks which have like a 480p display [13:41:52] though in practice it wasn't that bad outside the main page because they just defaulted to minerva [13:42:09] I don't like minerva but I like it better than typical rw design [13:42:39] i use pivot for [[mh:backrooms:Main Page]] and for some reason search is broken 🤷 [13:42:39] https://mh.wikipedia.org/wiki/backrooms:Main_Page [13:42:40] [13:42:55] there are various little things broken for the off-brand skins sadly [13:43:25] search works for me though [13:43:29] ratepage doesn't display and neither does the sitenotice [13:44:17] ratepage may be a compatibility thing requiring a patch or hack of some sort, but I know ratepage does not play well with multiple skins [13:44:30] sitenotice should work universally but I haven't tested all configurations [13:44:35] it worked about a year ago but it stopped working :p [13:44:47] might require a local hack and testing to see if the skin really did brick it [13:45:06] I was never too fond of pivot, so I haven't tested it much specifically [13:45:28] vector doesn't work either [13:45:58] nvm the sitenotice is there [13:46:03] on monaco [13:46:12] I'd have to look into it then [13:46:29] to be honest I have sort of a long list of things to look at though :p since the rfs is going well I have to start thinking about steward backlog [13:46:36] so far there's 14 things and counting to look into [13:46:42] damn [13:47:14] I'm still taking suggestions as well, if it isn't on the SN, RFRW or CN [13:47:25] I know there's a guy who had an account problem I need to follow up on [13:53:24] also something funny [13:53:56] https://tenor.com/view/lenny-eyebrow-flirt-smile-gif-5516050 [13:54:36] that was a weird closure [13:54:42] <2x2Master#7039> Reception wikis seem like a cesspool of pure autism [13:54:48] <2x2Master#7039> Usually I just keep to myself [13:55:06] <2x2Master#7039> Everything on miraheze except for pcb seems like cancer [13:55:13] you are so late man [13:55:22] they're gone from Miraheze [13:55:25] I was tracking until you excluded pcb from cancer [13:55:53] pcb is famous for being the one flavor of wikis that had to be smacked down harder than the reception wikis when they were still a problem [13:56:04] <2x2Master#7039> PCB can definitely have it's cringe at times [13:56:06] it has since shaped up somewhat but only because its cancer is not allowed to flare on the wiki [13:56:08] * reception wikis are gone from Miraheze [13:56:44] a website populated by 13-year-olds is bound to end up in spergatory if the admins don't really put their foot down [13:56:52] pcb/anarchy had to make radical changes to exclude the entire community element from actually appearing on the wiki or it would have been shut down [13:56:57] <2x2Master#7039> Idk but pcb seems better than "drawn fanon feet wiki" [13:57:02] so a pcb resident talking about cancer seems rather ironic [13:57:02] what [13:57:21] dfw is a weird cringy bit on the fringes of the platform that at least keeps to itself [13:57:32] and the more problematic ones in the feet vein are dead and buried [13:58:05] between feet, reception and political polandball wikis you have a rather tiny fraction of what actually exists on miraheze at this point [13:58:06] one time i complained on [[wikia:backrooms]] about there being too many underaged users and all the comments were pretty much "i'm (insert age)" [13:58:06] https://www.wikia.com/wiki/c:backrooms [13:58:07] [13:58:29] there are over 6k wikis man [13:58:37] just sayin [13:58:55] if there's any benefit i've noticed that wikia has a lot of high-quality wikis which miraheze lacks [13:59:10] miraheze kinda has a reputation for low-quality wikis [13:59:13] I suggest to end this convo as it seems rather unproductive [13:59:19] Good thing comments are not enabled by default on miraheze [13:59:23] https://tenor.com/view/youknow-you-gif-19056787 [14:01:03] wikia is a rather huge platform that is orders of magnitude larger tha nus [14:01:39] I assure you the amount of abandoned/junky wikis on fandom alone are many times the volume of miraheze combined: and that's the thing about platforms at scale [14:02:09] most free services have many strange corners or huge swathes of desert and abandonment; it is just the way of things [14:02:26] true [14:03:54] Where does Cosmos store the page content in the html?# [15:38:25] [1/2] In my opinion, both farms have very high quality wikis, their content itself does not depend on the platform but on their editors, if a wiki has a large community on X topic, the quality of said wiki is presumed (it is not a rule but it is the common denominator) [15:38:25] [2/2] What essentially differentiates both platforms beyond who has better quality wikis, is the service offered to these communities in terms of tools and customization of their wikis, where, in my opinion, Miraheze is better , and in ads, the joke tells itself [15:48:55] wikia has a monopoly so they can pretty much do anything and nobody would care beyond silent protests [16:44:16] What happens if swiftac cannot be repaired? [16:50:30] We don’t know [16:56:48] End of Miraheze: mass suicide, global catastrophe and rising depression rates all over the world. [16:58:37] dude [16:59:23] Well, we have to laugh about it. [17:11:09] SRE team is best positioned to talk about what is/isn't possible on such hypotheticals, but I doubt it will go to such extremes as the 'end of miraheze'. 🙂 [17:24:21] images seem to be OK, this isn't as bad as november [17:24:25] just rights are broken [17:34:04] Does anybody know any working wikitext parsers [18:40:28] images still do not load... [18:41:07] I have a post I wanted solved [18:42:21] light_angel: yeah, they won't until https://phabricator.miraheze.org/T10717 is solved [18:43:54] i still trust the HDDs more than the SSDs when it comes to reliability and recovery options. [18:49:35] Still troubles with pictures. 😦 [18:49:40] yes [18:51:45] Sadness. [18:52:04] Let's just hope before end of April everything will be okay! 🙂 [18:52:33] But I say ya something funny. [18:52:47] This place seems less active now [18:53:15] Favicon works at some arts at my websites. <:ThinkingHardMH:769233180799795221> [18:54:05] Eyrith: #miraheze-feed looks pretty lively considering all that's going on, wdym? [18:57:56] i only use Discord [18:58:24] What about non bot posts though? [18:58:40] bots don't show up on #miraheze-feed [18:59:03] it's a feed of all public wikis, contains only non-bot edits, don't know if that channel exists in Discord though [18:59:57] #global-wiki-feed [19:01:52] Either way, I hope I get help for my pytion problem soon# [19:02:05] pytion? [19:02:07] ]It is a MediaWiki related python problem [19:02:47] and what's the problem? [19:03:23] [1/4] I have this code https://pastebin.com/yDUkJbum [19:03:23] [2/4] But it does not remove all metadata, category info, and headings from a text parsed from an MediaWiki xml dump. It the regrex is there, but appears not to be stripping eveything [19:03:23] [3/4] Please ping me on replies so I see the reply [19:03:23] [4/4] MediaWiki knowledge is needed. Please DM me if you can help. (edited) [19:03:55] Trying to strip metadata/category data/headings from a txt file that was an xml dump [19:04:52] wouldn't it be easier to use an XML parser instead of a regex? [19:06:52] What one? [19:08:39] https://docs.python.org/3/library/xml.html#module-xml [19:10:14] The text I have is plaintext [19:10:43] is that plaintext wikitext? [19:10:54] So xml dump > plaintext file > stripped plain text file is what I want (and no, not wiki text_ [19:12:42] At the mo, I am at the "plain text file, but it has a wiki text less verson of the page that I am trying to remove the headers, metadata and category stuff from) [19:13:01] [1/2] It also has reputation for having more than six default themes, customisation beyond the icon and the bar at the top of the screen, and a pool of extensions that are ready for use, and a way to add new extensions, and that's not the end of a list. It's not just the reputation, but reality. The way big fandoms don't need all this, an [19:13:01] [2/2] d niche projects prefer to take on Miraheze functionality, says a lot about our society<:ThinkingHardMH:769233180799795221> [19:23:18] When will the files be back up [19:24:13] 2nd up in #announcements [19:25:26] Do I have to copy my content to the new host [19:27:26] I believe you're referring to the latest message, instead of the one before that. There is no new host, anything to that effect is purely hypothetical. [19:28:38] We're currently working on the file server, with no ETA. Currently trying to boot a recovery ISO on the affected server, but it may take upwards of an hour to get it booted, not even counting the work that would need to be done afterwards to actually perform recovery. [19:29:14] Oh okay [19:29:18] So, I wanted to regrax out the headers, category stuff and metadata from the .txt file (lacking MediaWiki markup) [19:29:22] I was just wondering [19:41:43] Bruh, Wikia is a company, I mean, Wikia is owned of everything on Wikia [20:01:49] oh neat, actually really looking forward to wikiforge, having had previously proposed a higher-availability paid option after the november crash [20:02:42] Yeah, lots of potential there, I'm excited about it. [20:04:27] [1/2] Though, this is bound to be one of the most controversial RfCs, which we already knew when publishing the draft. We know there are things to work out still, but if the initial concept passes, the board will then vote on it, and if approved, more community RfCs to ratify other plans from the community will also be done. This is no small thing for sure, nothing that can be don [20:04:27] [2/2] e overnight. [20:06:25] most votes now are {{oppose}}, i myself voted for {{oppose}} [20:06:25] https://meta.miraheze.org/wiki/Template:oppose [20:06:25] [20:06:50] Yes, but there are also a few people who vocally support [20:07:05] It's not currently live for voting, it's still a draft. Hence why there aren't votes at the moment. [20:07:22] there are a few drafts in atm [20:08:22] i guess we can get people to go to #announcements and react with either <:StrongestSupportMH:945088423469916160><:SupportMH:775411010583396352><:WeakSupportMH:945088926350200862><:WeakOpposeMH:945089209822232606><:OpposeMH:775411033330155520><:StrongestOpposeMH:945088333204320348> [20:08:31] so uh [20:08:34] do that i guess [20:08:38] i have no rights [20:09:07] <:OpposeMH:775411033330155520> [20:09:12] I think we're talking past each other a bit here. The point of it not being a live RfC but being in 'draft' status is to get community feedback before a vote is held. [20:09:26] I think it might be all about how it's framed, honestly. And, addressing the largest concerns very clearly at the outset. [20:09:45] i'm not entirely against it but i don't really see it going anywhere [20:10:08] WikiForge will exist whether with Miraheze or not. [20:10:24] Actually I see how this can fix the MH problem especially giant wikis [20:10:32] I see huge potential for it. I watch a certain grouping of wikis leave MH and other platforms to go independent because they don't have a better option. That's missed opportunity. [20:11:12] This is a big thing [20:11:46] mh doesn't really offer a platform to grow but neither does other wiki farms [20:11:51] The MH policy of 'always the latest version of MW' (or however it is worded) is problematic for wikis that value stability and continuity over being on the latest version (that's potentially a LOT of wikis imo) [20:12:06] This would be an opportunity to grow. [20:12:19] And is precicely the reason why our prod site isn't on MH. [20:12:19] most wikis are still on 1.35 [20:12:22] If we reject, WikiForge becomes a direct competitor then and a risk to us [20:12:33] That's ShoutWiki [20:12:37] That’s one thing to note [20:12:42] some others too [20:12:50] Not to mention loss of potentially shared benefits [20:13:02] I think the actual idea is 50/50 for me [20:13:17] The proposal needs a lot of work though [20:13:34] We've been waiting for a few security fix versions to upgrade to 1.39.x LTS before making the hop. We always want to be on an LTS version for stability/continuity. [20:14:06] We could have done our independent before now but I've been dragging my feet 😆 [20:14:20] We can't do that on MH [20:15:06] If SRE wants to remain on LTS releases, now is the perfect opportunity to make the change [20:15:12] i don't really notice but that's probably because i work on my wiki for like 2 hours a day at most [20:15:14] Isn't shoutwiki relies on ads? [20:15:21] yep [20:15:26] Is WikiForge a different Wiki hosting service [20:15:27] also mh is down very frequently [20:15:35] I thought "the latest version of mw" was a differentiating factor for MH though, from the competition? [20:15:37] Yes [20:15:40] i think that's a bigger issue than mediawiki [20:16:17] Not having enough money to operate + giant influx of users [20:16:43] tru(dy) [20:17:11] Performance, uptime, and stability would still be a factor for us, as well as advanced features/extensions, and better control of when extensions are removed. [20:17:35] Or at least, more warning for extension removal, so there's more time to adapt. [20:17:42] [1/2] WikiForge has the resources to support multiple versions of MediaWiki for individual wikis that we attempt to do also. LTS and latest are likely to be the possibilities for now at least though. That is one of the biggest things I will hopefully add support for within the next week or two, if it goes according to plan. But I agree, with how long and hard it can be for SRE to [20:17:42] [2/2] upgrade MH using LTS might be better, but then it becomes 5x harder and longer to upgrade between LTS versions when you 300 extensions you have to work out. [20:18:31] that's a lot of extensions to test [20:18:34] SRE spend 1/3 - 1/2 the year doing upgrade work [20:18:36] lts might be hard to support due to security vunerabilities in extensions [20:18:51] @!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! LTS get security updates [20:18:59] extensions though [20:19:12] At least the testing of extensions between LTS versions is longer, and less often. [20:19:14] That applies to the vast majority of extensions too [20:19:35] *testing period [20:20:04] You can edit your comments [20:20:23] I know, I just know some users can't see edits (I thought, if on IRC). [20:20:32] Correct [20:20:44] like s/testing of extensions/testing period [20:21:03] Disabling extensions is not something we can give any warning to [20:21:13] The more time you leave them up the more time an attacker has [20:21:20] When will WikiForge be released [20:21:29] It's already out [20:21:29] [1/2] I have security experience to help patch extensions when absolutely necessary or backport them usually can be done also. I have done it before with things. Security wouldn't be a blocker often times for that. WikiForge uses an entirely different setup for extensions then Miraheze does due to Miraheze setup. It takes 30 secon [20:21:29] [2/2] ds to install or upgrade extensions, and 2.5 minutes to upgrade MediaWiki core is my record there (and that is without multiversion, and not including DB patches) [20:21:39] It depends on what the problem is, I was referring to those that go unmaintained. [20:22:28] In our case, skin went unmaintained, no ticket to maintainer, no opportunity to fix. Took time until WMF offered to take it on and get its repo moved. [20:22:44] When was WikiForge released [20:22:52] March 28th [20:22:53] DPL3 went maintained, took time for CA to adopt and fix (much appreciated btw, by a large amount of users). [20:22:59] *unmaintained [20:23:16] March 21 was when i started working on it, released March 28 [20:23:28] Can you give me a link to the brand new Wiki hosting service [20:23:39] meta.wikiforge.net [20:23:46] Thanks [20:24:23] What's the difference between wikiforge and miraheze? [20:24:54] WikiForge is intended to offer premium features in addition to free features [20:25:45] Haven’t taken the time to give my full thoughts but atm I’m curious what the benefit to miraheze is right now. Seems like the proposal is for mh to help wf get off the ground, then once wf gets big enough it’ll provide some financial support to mh (and contribute to software that mh can use)? [20:26:18] That’s fairly accurate from my reading too [20:26:58] [1/2] If the RfC passes, free features will not happen on WikiForge, that will be Miraheze, and only things Miraheze is not technically capable of offering will WikiForge offer with premium. [20:26:58] [2/2] MH funds never go into WF, some of WF's do after operating costs. If anything it is more beneficial for MH than WF. [20:29:11] i hope this image issue doesn't turn into db141 2.0 [20:29:41] Nah, it just the cache or sort of failed. Original files are fine [20:29:56] Did I read somewhere that overages from premium offerings might go to MH? [20:30:09] Did I read somewhere that overages from premium offerings might go to MH? [20:30:27] It says something like that at the RfC [20:31:06] From the outside looking in, rn it feels like there is a volunteer shortage already and having to divert some time to another project may stretch them thin? Long term I can see the benefit to MH but what’s the timing on that [20:31:29] Why was I blocked by Abuse Flitter creating a account I was wrongly blocked for some reason [20:31:40] you're absolutely right on the volunteer shortage [20:31:40] There will be no Miraheze volunteer diverting to WikiForge. [20:32:00] Unblocked and fixed AbuseFilter. [20:32:11] Thanks [20:32:12] everytime I log in to phab and see 50 open normal tasks it just fills me with dread and makes me want to log out [20:32:32] morale is also not exactly high [20:33:14] If anything WikiForge will bring more help to Miraheze technically. [20:33:46] The morale problem can hopefully be addressed soon. [20:33:52] I started my wiki 3 weeks ago and boy do I feel lucky to come across one outage after anoter [20:34:01] Or at least the stuff stemming from community/volunteer morale. [20:34:13] no hate, just unlucky, I guess [20:34:24] Not being data outage is safe [20:34:28] I’m not sure WikiForge is going to save Miraheze if anyone is thinking morale and money issues will go away [20:34:32] Orange_Star: ^ [20:37:04] Maybe not overnight, but I also don't think it would a hindrance either. [20:37:18] @CosmicAlpha ye that’s my point [20:37:49] Companies take time to make a profit [20:38:06] And morale is a harder issue to solve [20:38:16] Dang that sucks :/ [20:39:38] There's just a lot of work pending there [20:40:32] for a while I tried to organize the Miraheze SRE workboard so that I could concentrate on the issues that are more bug reports instead of feature requests but that was a lost battle already [20:43:28] I must’ve misunderstood the sentence about the future sysadmins and SRE. So the partnership would be one where MH offers WF name recognition and a potential pool of MH wikis that are willing to go to a premium service? Am I missing anything else that MH provides? [20:44:04] There's a discussion in the #meetings channel that gives more context [20:45:02] Miraheze isn’t giving a lot [20:45:23] People actively look for services as WF describes that MH and Wikia don't meet, so if launched I'm not sure it'd need name recognition at all, frankly. [20:45:46] There's a bracket of wikis whose needs aren't being met, that are forced to go independent to get them met. [20:46:38] My interpretation is, this helps bring those folks under the MH umbrella for some possible mutual benefit, but folks can correct me if that interpretation is wrong. [20:47:14] I mean, it would need name recognition, because paid wiki hostings already exist on the market 😄 [20:47:59] I've been witness to multiple game wikis trying, then leaving MH because it can't meet their needs at current. [20:48:43] They end up independent [20:48:52] As ours continues to be (same situation) [20:49:04] https://www.mediawiki.org/wiki/Hosting_services is a very bad list but it lists some options [20:49:30] I think if we worked collaboratively, we stop a potential competitor competing [20:51:19] Exactly [20:51:24] It's a good opportunity [20:51:34] Well free feels better than paid so would the audience have that much overlap [20:51:35] We do need to consider the law though [20:51:47] It’s anti-competitive behaviour [20:52:15] To fill a void that exists by expanding? I didn't think of this... [20:52:52] For those that value different priorities, paid feels better than free too, so it really is two unique user groups that can be served cooperatively. [20:53:09] @FrozenPlum well entering into an agreement between 2 companies to restrict who each can have as customers is illegal [20:53:25] And can result in a custodial sentence [20:53:52] Ahh okay. Interesting. If there's a way around this, that would be good... [20:54:25] Seek legal advice to stay within the law [20:54:29] looks like a problem for Owen [20:55:59] https://cheatingorcompeting.campaign.gov.uk/ [20:56:12] Maybe setting a global strategic direction statement and corresponding policies that clearly state the unique niche to be served, and complimentary intent? I have no idea. [20:56:48] [1/9] Honestly Miraheze turns down volunteers or forces them out due to some mistake(s) far to often. Happened multiple times in SRE since I joined Miraheze initially. Including some of my own mistakes contributed to and were by contrast a casualty from this. [20:56:48] [2/9] I know something needs to eventually be done in the internal structure of Miraheze, and it isn't horrible, won't say that at all, but it isn't perfect either. And no, I am not talking about WikiForge at all with this comment (so far, will below). Just a general observation. [20:56:49] [3/9] So I do understand how people do not like the idea of something they feel will contribute against this, but I don't think this will negatively impact anything. Miraheze itself continues to operate normally, WikiForge provides profit to Miraheze, and Miraheze has one less potential future competitor. And allow Miraheze to become a bigger active competitor in the MediaWiki rea [20:56:49] [4/9] lm. Additionally it allows for additional technical work to be done on MH itself based off features WF is developing. I really don't see where the disadvantage to MH comes in? Although I do understand the concerns raised, which hopefully we could address. [20:56:49] [5/9] I have tried to help things as best I could, and made some mistakes along the way, I admit, but regardless I have tried, and there is only so much I can do, giving Miraheze WikiForge as a potential project within was my last attempt to help Miraheze, and not necessarily benefit WF as much, though I admit it isn't completely unbenefited by this, but MH is definitely on the be [20:56:50] [6/9] tter end of the merger, at least in my mind. I didn't immediately jump to pursue the potential merger, it took a lot of thinking still. [20:56:50] [7/9] Again, I reiterate, I understand the concerns, and apologize if it seems we didn't properly outline the plan. [20:56:50] [8/9] And finally @RhinosF1, WikiForge is not a registered company, even though I intended to make it one before this proposed merger idea. So as it isn't, it would likely not be against said law regarding competitors either. If the RfC falls through, I will probably register it, but am still open to some kind of collaboration with Miraheze in the future, regardless of how that co [20:56:50] [9/9] llaboration may present itself. I am not looking to make a full competitor between Miraheze and WikiForge either. [20:56:53] I thought the idea was a merger, rather than 2 separate companies? [20:57:15] Definitely I need to re-read [20:57:54] There’s a lot to explore [20:57:58] Informal merger. WikiForge isn't a company, just a project started by CosmicAlpha [20:58:03] Nothing is going to happen overnight [20:58:12] so no legal mergers and agreements are going to have to be filed [20:58:29] That makes better sense, thank you! [20:58:34] it's basically just a community endorsement for CosmicAlpha to do his project but under Miraheze supervision [20:59:14] I had thought it shouldn't be that complex, but I'm still getting up to speed. [21:00:22] Yeah, talking about anti-trust law etc. is premature if there isn't even a company in play. [21:00:32] I mean, of course it would be complex, just, I didn't think there'd be legal ramifications if consulting legal guidance. [21:00:36] This is probably what helps it the most [21:01:22] The only real legal problem is whether an NGO can provide services for payment to people. [21:01:30] I’m expecting if the proposal is approved, WikiForge be a child company [21:01:41] If, of course, Miraheze is even registered as that. [21:01:43] That’s not an issue, happens all the time [21:01:52] Were not for profit [21:02:25] I don't know what the British law is on this matter, so I didn't want to assume. [21:02:42] I am trying to organise legal guidance to be independently published and made public to the community on any final agreement [21:08:37] https://tenor.com/view/blank-stare-really-i-dont-believe-you-side-eye-looking-gif-6151149 [21:18:09] Is my wiki only one having these issues ? [21:18:27] Or maybe it's the issue on my side [21:18:33] Been like that all day [21:19:25] https://discord.com/channels/407504499280707585/407504500136607745/1095367595777085561 [21:19:42] Oh okay thanks [21:19:46] https://tenor.com/view/hurry-up-youre-late-time-check-gif-13143819 [21:27:02] https://tenor.com/view/tmnt-leonardo-a-ninja-is-always-patient-ninja-patient-gif-26012978 [21:27:10] 😆 [21:27:21] Bruh [21:27:26] Thank god this didn't send [21:27:39] (wrong gif) [21:28:10] I hate that when that happens [21:28:25] The right one can't be sent either [21:29:09] Did you `/auth` ? [21:29:20] Not sure if that might be part of it or not. [21:50:48] fix your servers [21:53:54] [1/2] Please don't be rude. Fixes are in progress. Once again, please have patience. MH is run by volunteers (who have jobs and other commitments) but volunteer hours nonetheless, so that users can have free wiki hosting. They do stuff in the best time that they are able. [21:53:55] [2/2] Some technical stuff isn't a quick or easy fix, or it requires advanced knowledge, and/or significant time to do. [21:56:28] I'm sure the volunteers understand that this can be frustrating, and they too are likely frustrated also. [21:56:44] They're doing their best. [21:57:30] ... [21:58:09] It will get fixed 🙂 it just takes some time. [21:59:36] Right now, they are a bit short in volunteers, and the issue is a bit complex. [22:09:40] Miraheze getting entangled in anti-trust? 🤣 [22:09:51] Fandom would like to make a case for that. [22:10:19] "Miraheze does anti-competitive behaviour... like letting their users LEAVE!!!! Also, they won't accept our payment platform, Fandom Cash!" [22:10:33] Is that actually a thing [22:10:40] Nah [22:10:49] But I can imagine Fandom trying something as ridiculous as that [22:11:51] haha, they really are a mini-apple, it feels like sometimes [22:11:59] best I can promise is that my rfs will hopefully result in more time for steward-sres to be more sre [22:42:43] Fandom did launch their own 2FA mobile app, not too far out of imagination [23:02:13] why did i expect someone with that pfp to act immature [23:04:37] Since text is working fine, this seems a great day to muck around with MH extensions [23:04:53] isnt every day [23:05:14] Most days I'm mucking around with stuff that involves images [23:05:43] If we're sans images a while, then text-based is going to be the thing. [23:39:57] plenty that can be done without image tbh [23:41:10] may depend on what needs to be done [23:41:29] normal article editing aside