[01:13:32] you will be uncontrollable! [01:22:16] https://tenor.com/view/absolutely-unstoppable-chris-hurt-fuzzywuzy-smite-unstoppable-gif-18563626 [03:50:53] [1/2] ??* [03:50:54] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1219855660796215307/image.png?ex=660cd21d&is=65fa5d1d&hm=74a403e51a0d5b1fc015c1d40b00ca640a5844b6e43a28a058c85bd6d025df08& [07:46:08] <.labster, replying to koreirose> you have held broken English [07:58:40] ? [07:59:18] <.labster> "you have held broken packages" seems wrong, I don't know what that means in English as a native speaker. [07:59:39] Probably apt [07:59:49] You can add or install packages in apt [07:59:57] I don't know what it means to hold an apt package though [08:00:03] Like holding back an update? Idk [08:00:13] <.labster> I guess it means that at one time in your life, you had a physical package in your hand that was broken, and for that reason apt hates you. [08:00:27] Lol [08:00:33] I would assume so [08:00:38] Have you blacklisted any package before [08:00:44] Are you using unstable? [08:01:05] Did you tell it to ignore dependencies ? [08:01:10] Not that I know of [08:01:35] Maybe try a manual install of them packages [08:01:42] You need to see why they are failing [08:02:01] Because for some reason apt thinks it's been asked to do the impossible [08:03:18] I will later bc it's late into the day, I only came online because I had wanted to solve the issues with RemoveRedlinks [08:03:29] https://github.com/marohh/mediawikiRemoveRedlinks/pull/13 - hopefully this PR will get merged, it works on my machine [08:05:25] That's the correct way to do it [08:05:36] I haven't code reviewed the slightest though [08:05:44] Just that you are using a partition [08:06:22] Fandom didn't use a parser option and theirs works fine but it just seemed hacky [08:06:41] + some people browse the Internet without JS for strange reasons so I want the extension to work for them [08:07:55] Works and the correct way to do it are not the same thing [08:08:15] Yea I know lol [11:58:28] [1/3] may I add something regarding removeredlinks? [11:58:28] [2/3] why they appear as normal clickable links? [11:58:28] [3/3] iirc fandom converts red link into plain text, it's even more confusing because the links are fake [12:18:37] Why remove red links at all? I mean, they give you a reason to create the page [12:25:22] if it wasn't clarified, held in deb-speak is suppressing updates I believe [12:25:28] it makes sense in its own context [12:31:37] it's only for logged out users, because, apparently, red links hinder SEO [12:32:58] [1/2] logged in users will see red links properly [12:32:58] [2/2] but because extension is wonky, they sometimes appear as normal links [12:36:21] Ah [12:36:26] thanks [12:44:53] Also have them appear as normal links does make me wonder if it is even gonna help SEO, depends on how it is done I geuss, but I fear it just sets the color in the CSS to the same color as normal links, which ofc isn't gonna fool google crawlers and the line [12:45:12] it doesn't do that [12:45:37] it keeps the `a` element, but removes the `href` attribute, so it doesn't link anywhere [12:45:59] iirc [12:48:57] Fair, haven't actually seen it used, so was pure geuss (still I wonder how that affects SEO compared to not having the a element at all) [12:56:21] yeah, clicking such links does nothing [12:56:31] but it's just weird [12:56:46] visually [12:57:28] I'm taking a guess here but the bot clicks every link it's able to access [12:57:43] clicking on red link will take it to action URL [12:58:02] and action URL are noindex/nofollow [12:58:55] google doesn't like when a lot of pages are noindex/nofollow (but looking at PTW's console, it still can disrespect the rule and index pages anyway???) [12:59:28] the search engine crawlers are outside of the comprehension of mere mortals [12:59:38] it's soooo damn confusing [12:59:40] it will do whatever it wants and just treat these things as hints [13:01:10] so, yeah, I suggest to look into showing disabled red links as plain text instead of fake normal links [15:16:01] [1/2] It means the package is being "held back" from being installed, but it wasn't removed from apt. [15:16:02] [2/2] So apt still knows that you want it (are "holding" it) but refuses to install it. [15:45:34] They don't appear as normal clickable links unless you have !important styles set on the a elmener [15:48:31] This is what it does on my machine [15:48:40] [1/4] When users who aren't logged in don't have editing permissions or usually don't see the need to edit, links to non-existent pages is more confusing than helpful. [15:48:40] [2/4] Links to non-existent pages that aren't nofollow is bad for SEO [15:48:41] [3/4] This extension disables red links to non-existing pages to users which are not logged in. [15:48:41] [4/4] The red links are still shown to logged in users in order to facilitate editing. [15:49:20] Don't make red links in the first place? 😉 [15:50:28] I don't always have enough time to create all the pages linked to [15:50:38] Redlinks are useful to editors but not readers [15:52:34] Yeah you should make links to anything that potentially should have a page, even if it doesn't as it then also shows up on Special:WantedPages for other editors to see that well a page for those things are well... wanted [15:56:06] Yeah [15:57:23] easier to say than done when you are the sole editor + the stub tendency on bigger wikis [15:57:51] hmm 🤔 [15:59:53] [1/8] ```php [15:59:53] [2/8] if( $wgRemoveRedLinksAlsoLoggedInUsers || !$parserOptions->getOption( 'loggedin' ) ) { [15:59:54] [3/8] unset( $attribs['href'] ); [15:59:54] [4/8] unset( $attribs['title'] ); [15:59:54] [5/8] unset( $attribs['class'] ); [15:59:55] [6/8] $attribs['style'] = 'color: unset; cursor: text; text-decoration: none'; [15:59:55] [7/8] } [15:59:55] [8/8] ``` [16:00:44] I don't remember if I set !important tbh but all my wikis have custom link styling [16:15:16] JS? [16:16:18] [1/2] also yeah, I used important, removing it in inspector is messing up w/ "Page" (can be fixed, I guess) and "Discussion" (it stays red) tabs [16:16:19] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1220043251415912528/2024-03-20_19_14_26.png?ex=660d80d2&is=65fb0bd2&hm=92fe66fc41045d20ba07a9425b89edaa546c160fd87218e668c666924e10dead& [16:16:47] I guess it's just always like that [16:16:58] not affected by extension [16:22:30] + sidebar etc links in Vector will require additional styling [16:24:55] It's PHP [16:33:21] aight, this ain't working as I thought [16:33:40] there's a:hover which can be changed only w/ !important [16:34:16] and redlinks-turned-into-plain-text receive hover effect [16:41:01] and I can't do anything about it, it seems [16:41:37] extension removes `new` class from red links [16:55:47] Btw why is JS not the correct way? [16:56:25] Better for performance [16:57:00] Ah I see [16:57:03] Interesting [16:57:48] It's slightly more complex than that [16:57:53] But that's the simple answer [17:19:40] aight, new question [17:21:26] why it seems like it works only on main page? [17:21:53] [1/2] can see all red links, all clickable as anon here [17:21:53] [2/2] [18:12:27] <.labster> cache? [18:14:58] I'll wait [18:22:02] it's getting mixed up anyway [18:22:21] I'm getting hidden links while logged in [18:22:41] unclickable too [18:24:20] Yeah that happens for me too outside of Miraheze. [18:24:23] <.labster> On that page, I'm seeing no redlinks except for the talk page. [18:24:40] logged in or out? [18:24:44] The extension seems to fuck the parser cache up. [18:24:49] <.labster> logged out, private window [18:25:06] <.labster> yeah, that's pretty much what I thought, parser cache [18:25:36] [1/3] I logged in and see no links here, when I know they are here [18:25:36] [2/3] [18:25:36] [3/3] https://cdn.discordapp.com/attachments/1006789349498699827/1220075787609444403/2024-03-20_21_25_29.png?ex=660d9f1f&is=65fb2a1f&hm=f93efd2abd38e68e79bc20e7073a7c17f51d98a10a2d6eade9768b102acea8dc& [18:25:46] <.labster> yep, now logged-in the redlink disappeared [18:26:15] <.labster> what's the name of this extension again? [18:26:30] RemoveRedlinks or something like that [18:27:03] Yeah [18:30:07] That's what the linked PR is supposed to fix [18:30:22] https://github.com/marohh/mediawikiRemoveRedlinks/pull/13 [18:30:26] It took me too long (apologies!) but this is done. Do you want access, @rhinosf1 and/or @originalauthority? [18:30:40] I do [18:30:59] I have WMF security access [18:31:08] I would like to know which ticket though [18:31:59] Ah, that explains why I see you in so many places. [18:32:17] https://phabricator.wikimedia.org/T360557 [18:35:06] <.labster> I guess lets wait a week, if it doesn't get merged, deploy Collei's branch [20:41:24] Hai guis is me Jonny an I laik apols [20:42:04] <.labster> Jony Ive, is that you? [21:26:42] The extension has been broken for a long time and I don't think the maintainer is very active so we might have to wait a bit for my PR to be merged [21:27:07] If it's not merged in like a month I'm going to just make a fork of the extension and maintain it until the maintainer becomes active again [21:27:40] <.labster> I mean, you kind of already did make a fork of the extension. [21:28:07] Ngl I thought you made the extension itself for a bit [21:29:18] has anyone tried pmwiki [21:29:42] <.labster> yes [21:29:58] <.labster> I also know the author of pmwiki [21:30:58] I made every working version of it and the maintainer made every broken version of it [21:31:04] it's really interesting... [21:31:09] but also years behind MediaWiki [21:31:19] only 1 dev from what I can see, though. [21:32:01] What’s the differences to MW [21:32:19] same concept but more granular control and also a bit dated [21:33:58] also it stores page content in txt files 😮 [21:34:39] :moonch: