[00:15:29] Pipe Escape extension helps with that [00:21:22] https://klipy.com/gifs/metal-pipe [00:49:39] Hello again [02:22:42] Good evening! a:fallon_confetti: [02:57:16] It's a great character from bakugan [03:00:33] [1/2] Hello all, sticking my nose in here. I'm a fan of the little plastic army men game 'Warhammer 40k', and it's recently had some wiki drama. There is a long established fan wiki that is cc-by-nc, and folks are upset with it's moderation, so they tried to fork it to wiki.gg, but after an initial go-ahead from wiki.gg's moderation team, it was reversed when the original wiki (lexicanu [03:00:33] [2/2] m) complained. I had warned the forking team that cc-by-nc probably wasn't cool on wiki.gg, but I was wondering if it might be cool here? Is forking established wikis (with potentially litigious publishers) a thing that Miraheze does? [03:05:51] i'd do that TBH. [03:29:48] wdym by "cc-by-nc" wasn't cool [03:31:10] Wiki gg has ads and this is commercial, I think that was the point of contention [03:31:30] Miraheze is non commercial so it should be fine to fork here as long as you keep the license the same [03:32:54] I've been following that situation a bit. You'll need to maintain a compatible license and excise any content from after their godawful license change [03:33:25] They went all rights reserved for anything after the changeover, if I recall that mess correctly [03:34:43] We will not act on your behalf in the case of lawsuit, due warning [03:35:16] So if they get litigious, that'd be on the forking party to litigate that right to fork [03:35:26] I did not know the license change oh my goddd [03:35:48] Ooof, yeah, i was unfamiliar with the license change [03:37:08] I could be wrong on that [03:38:10] Id be fine with them suing me, but I would figure they'd contact the publisher/host [03:38:27] They do, but we act as passthrough [03:38:46] Something akin to the dmca? [03:38:53] Correct [03:39:42] Fair enough. I'll look into the weird license stuff. How easy would it be to backdate a fork? [03:56:57] The licensing information is on their terms of use page if you need a quick reference [03:58:18] Text only goes under CC BY NC SA after _five years_ after the final edit of a page is published, which is absurd. [04:00:25] I think that's a fairly recent change, which can't possibly be retroactive [04:01:10] [1/2] Yeah the history page says it was updated 27 October this year [04:01:11] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1568475374759845958/IMG_8122.png?ex=6aeff406&is=6aeea286&hm=a9baeaa358ad4ec9647a68f0cd46fdd8425a809951d56d7263d6ec3f48bc1ec3& [04:07:59] Yeah that only applies to any written content after that date, all of the writing before then def still falls under Cc by nc [04:08:28] They've got a weird ass licence currently and clearly aren't acting in the community's best interests anymore [04:08:52] I’m just appalled by the gall of it all but don’t want to clog up general [04:24:09] The most recent change in the history changes the 'all rights reserved -> cc-by-nc' from 1 year to 5 years. But I suspect that the '1 year' is also a new addition. They somehow lost the edit logs of their ToS at the start of october. [04:26:11] Might be worth running it through Wayback Machine or something. [04:27:10] [1/2] https://web.archive.org/web/20250505041813/https://wh40k.lexicanum.com/wiki/Warhammer_40k_-_Lexicanum:General_disclaimer [04:27:10] [2/2] Yeah, may of last year, all content was published CC-BY-NC by default [04:28:56] Actually, that's there disclaimer, which is still up 😐 [04:30:58] [1/2] Okay, this is probably clogging up general at this point. But tl;dr: Yeah, the nerve of these guys kinda fries my grits. [04:30:58] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1568482873323823205/image.png?ex=6aeffb02&is=6aeea982&hm=056ac8ecb38ff007c3a606310507ac94aa606b835768c1b7c0deb714c40fec57& [06:18:11] it seems the change in licensing happened after the fork (or, rather, even because of the fork), so it sounds like if the data dump from the wiki.gg fork is still available, it shouldn't conflict with whatever license change they did [08:35:01] Do we need another warhammer 40k wiki? [08:42:19] the team at wiki.gg need a new home because lexi was threatening legal action against wiki.gg for the wiki [08:42:27] so wiki.gg dropped wh40k [08:43:03] more on why they closed the wiki [08:43:06] does anyone know any templates i can use for a peace treaty looking infobox? [08:43:51] [1/2] @eytirth [08:43:51] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1568546512953286746/image.png?ex=6af03646&is=6aeee4c6&hm=e7721fc3e004413344e7bcfada6a84a8dbf2b33c7e6c2004de9be5038bfa2ba4& [08:44:30] Oh [08:44:46] fandom wiki is out of the question though, it's obviously trash lol [08:44:50] Shame as it was the best of all the wikis [08:44:55] yeah I agree [08:45:06] and lexicanum is being terribly managed now [08:45:16] which prompted the split in the first placre [08:45:49] I suggest for them DMCA free hosting, pay in cypro [08:45:53] I get that it is one thing to be the owner of lex and to be disappointed that your editors do not want to work with you anymore [08:46:19] it's a whole other thing to go as far as to harass an official wh40k author for supporting the new wiki and threatening legal action [08:47:07] even fandom never went as far as lex did, they always just deal with their copy of the forked wiki [08:47:50] Lex are k!drp'tsh nothlits! [08:48:16] it's quite unfortunate that they're currently the 'best' wiki around at this moment [08:48:28] until wh40k wgg finds a new host and recovers though [08:48:59] Wait... they did legal action over content that CC-BY-NC-SA allows free copying under the terms? [08:49:21] that's the thing, we don't know on what grounds they were threatening legal action [08:50:07] if anything, the team at the wh40k wiki.gg abided by the license, which is cc by-nc [08:50:16] lex listed their content license as cc by-nc and so did gg [08:50:28] If they wanted no one use it, they need to use All Rights Reserved [08:50:48] even if lex later on applied a weird way to license the content [08:51:00] which is copyrighted for 5 years then cc by-nc [08:51:12] Huh, show link to TOS [08:52:09] I thought to change a license you would need to get people to agree to it formally, as in not just click a botton [08:52:49] . [08:53:13] that's supposed to be the case [08:53:23] Skxawngs! [08:53:24] dunno wth they're doing [08:53:39] So confusing, and unethcial [08:54:50] [1/7] "4. Your Use of Our Content is Restricted: (a) Unless expressly permitted, you may not copy, reproduce, distribute, publish, enter into a database, display, perform, modify, create derivative works from, transmit or in any way exploit any part of our site or any content thereon, except as permitted under the last sentence of this Section 3(a) and except tha [08:54:50] [2/7] t you may make one print copy that is limited to occasional articles of personal interest only. Without limiting the generality of the foregoing (but subject to the last sentence of this Section 3(a)), you may not distribute any part of this site or any content thereon over any network, including, without limitation, a local area network, or sell or offer i [08:54:50] [3/7] t for sale. In addition, these files may not be used to construct any kind of database. Just as we from time to time excerpt materials from other sources in order to support the various commentaries and writings contained herein, we respect the right of others to make “fair use” of the materials contained on our site; accordingly, you may from time to time [08:54:51] [4/7] excerpt and use materials set forth on this site consistent with the principles of “fair use”. [08:54:51] [5/7] (b) We are concerned about the integrity of our site when it is viewed in a setting created by a third party that includes advertising or other materials that we have not authorized to be displayed with the content of our site. Neither you nor any third party shall make use of the contents of our site in any manner that constitutes an infringement of our ri [08:54:51] [6/7] ghts, including copyright or that has not been authorized by us." [08:54:52] [7/7] @justleafy2003 AFIAK CC lisances would not allow this [09:17:08] lets play a game of compare the tos https://web.archive.org/web/20261201000000*/https://wh40k.lexicanum.com/mediawiki/index.php?title=Warhammer_40k_-_Lexicanum:Terms_of_Service&action=history [09:18:09] or just the one they still have up https://wh40k.lexicanum.com/mediawiki/index.php?title=Warhammer_40k_-_Lexicanum:Terms_of_Service [09:19:50] one thing I'm not seeing is the license having been specified either currently or formerly [09:19:58] "No additional restrictions — You may not apply legal terms or technological measures that legally restrict others from doing anything the license permits." - https://creativecommons.org/licenses/by-nc-sa/4.0/deed.en [09:20:00] maybe it showed when logged in [09:20:17] AFIAK they are violating the terms of the CC-BY-NC-SA [09:21:14] but is that what they're using [09:21:17] or have ever used [09:21:25] Even the older ones I belive have that [09:21:36] it would be nice for that to be absolutely affirmed [09:22:10] AFIAK it was under CC-By-NA-SA but now it has changed [09:22:14] my experience is with other indie sites that simply did not specify and took a slightly modified all rights reserved approach which was mostly just vague, and is part of what makes the specific wiki I had in mind toxic waste to reproduce even if it would be valuable to do so [09:22:48] if you can find an archive entry to validate that then you have a case, if people who were editors can absolutely affirm it then they may have a case, otherwise if there is any room for 'I think so' that is not fully credible then it cannot be a case [09:22:52] Here we go [09:22:56] odd sites like that can very well just go forever not specifying [09:23:33] Seems like it was CC-BY-NC-SA then soem stupid terms from the TOS [09:23:34] ok so yep, they screwed that up bigtime and have a case to be litigated [09:23:45] the tricky thing is who is going to litigate that [09:24:10] IDK [09:24:51] IDK, someone with good laywers [09:41:12] sent a message elsewhere, best I can do about it I think [09:42:04] it is a domain I'd love to be able to fight them on principle and explicitly welcome them with open arms onto Miraheze because their case is solid, but I cannot rationally speak for or commit miraheze to such a situation [09:42:52] if we had a war chest or could run a farm explicitly with a war chest for controversy that would be another story, alas [09:59:41] <.labster> Does anyone here know about InternetArchiveBot? It keeps vandalizing our wiki, like removing links to live sites, or replacing links with links to archive or a different URL. [10:01:50] [[metawikimedia:InternetArchiveBot]] [10:02:02] [10:02:03] iirc it can be run on non-wmf wikis on request [10:03:44] oh. we also have a page [[InternetArchiveBot]] [10:03:44] [10:04:35] <.labster> Huh, I don't remember signing our wiki up for that, and neither does another admin. [10:05:00] so your wiki is not listed there? [10:06:07] is it listed on https://iabot.wmcloud.org/?page=runpages then? [10:07:46] <.labster> Oh, it's listed there, just no way to disable it. [10:08:26] maybe you can contact the person who enabled it for your wiki [10:08:36] <.labster> Maybe, don't know the person. [10:08:50] Harej is one of the operators of IA Bot so you can reach out to him [10:09:18] https://meta.miraheze.org/wiki/User:InternetArchiveBot says you can leave message on https://meta.miraheze.org/wiki/User_talk:Cyberpower678 [10:10:54] @wikitideharej or Cyberpower [10:11:16] <.labster> Sure, I will [10:11:28] (maybe the user page should be copied to loginwiki? [10:11:37] so it can be a global user page [10:12:31] that would be appropriate [10:13:35] <.labster> I have to sign an EULA to get my bot shut off? Wow. No way. [10:14:10] [1/3] We do have the option of an emergency fundraiser, but taking in a wiki knowing that we have a high likelihood of needing a fundraiser later to defend it legally is another story. Not something we should do unless we know wikis on the platform are okay with resources being devoted to one wiki's legal case. [10:14:10] [2/3] I wouldn't mind a private wiki for them to temporarily stash their work until they find a feasible solution out of the mess (e.g. self-hosting), though. On tech's side it isn't much of a burden besides needing someone to do the import and later delete the database/images to free up resources. But it's not my decision to make, for both the wiki editors and [10:14:10] [3/3] stewards reviewing the case. [10:16:32] Just block it then and message your fellow director [10:19:55] <.labster> He's asleep probs [10:32:45] I'd probably even say this should route somewhat to board 2c even above stewards given the circumstance [10:33:41] [1/2] do banners suddenly have weird spacing for anyone else [10:33:41] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1568574153634615306/Captura_de_pantalla_2026-11-07_102349.png?ex=6af05004&is=6aeefe84&hm=1b18a9e9ce1c5b8ec41e97e58497e813ddfc07b2eb9b1b7cb4f8e5bf102e4538& [10:38:44] nvm it was the dum,b noinclude thing that automatically adds spacing [10:38:52] ❤️‍🩹 [10:54:01] [1/2] whats going on with commentstreams? you cant enter text [10:54:01] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1568579271897653359/image.png?ex=6af054c9&is=6aef0349&hm=3c2fd5f1db462c8c0dee1da21cf831478de592dbc7e0913454bf9d01f175355e& [10:56:02] for some reason its disabled across the wiki [10:56:51] Someone enabled VEForAll probably [10:58:14] isn't veforall designed to integrate with cs? why it breaks? [10:58:15] how do I fix that [10:58:38] Try disable VEForAll and clear cache? [10:58:46] Probably something that happened after the MW upgrade [10:59:14] bad news [10:59:15] hope we can get yappin soon [11:01:03] MW new, broken? [11:01:29] [1/2] it seems like everything still works but for some reason the box for entering text is disabled [11:01:29] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1568581149666713681/image.png?ex=6af05688&is=6aef0508&hm=9c9fa96904c2d8e7d11f8742f539ba4c9410571dd33a67df1b403303ea5abdc7& [11:02:41] Did you append `?debug=2`? [11:03:07] yeah [11:03:08] still disabled [11:03:23] Well you re-enabled the extension 2 minutes after disabling it so... [11:03:51] Like from your screenshot the VEForAll toolbar was still there... [11:04:06] comments worked after VEForAll was disabled [11:04:13] im just sharing whats causing it to not work with its on [11:04:22] Ah I see. Thanks for clarifying. [11:04:57] [1/2] Probably this [11:04:57] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1568582021968826429/image.png?ex=6af05758&is=6aef05d8&hm=02fd737ee975161da42c00dbe86e58fb173a1ae5e8f2735ace68140fd4f3a268& [11:05:13] We plan to get rid of CommentStreams and PageForms anyway. So after that VEForAll wouldn't be useful. [11:06:15] how come? [11:06:51] [1/2] I remember there being a option to allow editing comments with visual editor but its not there anymore [11:06:52] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1568582502027632660/image.png?ex=6af057cb&is=6aef064b&hm=c3421d9b5053ab4e71d97504347bf5ee78520abdcb66788e1978b68aa3ca06a0& [11:09:14] [1/2] VEForAll adds VE support to those 2 extensions. Once they're gone there would be no use for it. [11:09:14] [2/2] Yappin supports VE out of the box. [11:09:45] vefor2 [11:10:12] [1/2] It supports a few more but on our platform only 2. [11:10:12] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1568583342629199963/image.png?ex=6af05893&is=6aef0713&hm=65e6ca4b868f323143541cb0b02f146ea0a69c0d0750f3793b959c3eb8c36ff0& [11:12:07] Pagforms, get rid of, why? [11:12:45] just wanted to play the pun [11:26:00] [1/2] See draft page: https://meta.miraheze.org/wiki/Tech:Noticeboard/Disabling_PageForms_on_wikis_with_no_usage [11:26:00] [2/2] Note that this is just a draft and does not reflect the technology team's consensus. [11:26:25] As far as performance goes it used to bring down the entire farm. Plus security issues. [11:32:35] I mean, it is useful for mass-making blank pages [11:38:47] MediaWiki core provides that feature, and so does Extension:InputBox. [11:41:19] [1/2] And TBH it's hard to imaging needing 15k lines of PHP to achieve that feature, and if you count JavaScript and tests it's close to 100k lines of code. [11:41:20] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1568591175345250364/image.png?ex=6af05fdf&is=6aef0e5f&hm=cb46ba850b35309c34f4daebc5edcf1c027773131061ef4232d900b304a6e468& [11:54:46] How do you do it with mediawiki core? [12:06:33] See https://www.mediawiki.org/wiki/Manual:Creating_pages_with_preloaded_text [13:06:07] [1/2] finnaly after a monts! [13:06:07] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1568612514323894342/image.png?ex=6af073be&is=6aef223e&hm=73fe5e1b5fb251ff1b856a505a99a0ed4744176c9d261488b2b2357599c7286b& [13:09:56] The subreddit was abandoned for a while, and moderators on there had other, more important roles [13:10:37] 😭 the thing i wanna join to miraheze reddit cuz i know it improve seo on wat i watch on shorts [13:10:56] glade they are back [13:30:54] Wait, miraheze has a subreddit? [13:37:43] r/MirahezeWikis [13:40:23] LOL, I should menion the stuff I v put on dev there [13:52:58] [1/2] @posix_memalign got another minor bug with mustache, it's way more minor than the other one but attempting to use a template that includes a style on the page title (with displaytitle) will cause the