User talk:Headbomb/unreliable
 | If you're curious about why a source is highlighted, first check b} |
|
|
|
This page has archives. Sections older than 30 days may be automatically archived by Lowercase sigmabot III when more than 4 sections are present. |
Baidu Baike sister site
Yet another sister site for
- baike.baidu.hk: Linksearch en (insource) - meta - de - fr - simple - wikt:en - wikt:fr • MER-C X-wiki • gs • Reports: Links on en - COIBot - COIBot-Local • Discussions: tracked - advanced - RSN • COIBot-Link, Local, & XWiki Reports - Wikipedia: en - fr - de • Google: search • meta • Domain: domaintools • AboutUs.com
Amigao (talk) 04:11, 4 February 2024 (UTC)
- Hi WP:BAIDUBAIKE sites are by your script. Thanks for the superb work as always! - Amigao (talk) 00:34, 11 March 2024 (UTC)]
- Added b} 01:57, 11 March 2024 (UTC)]
- Added
Opast
another predatory publisher, via Phoebe: https://www.opastpublishers.com/ – SJ + 11:35, 13 March 2024 (UTC)
- Already flagged. b} 03:17, 14 March 2024 (UTC)]
Dark mode is coming
Some of the CSS in dark mode "scans" for inline CSS and then makes certain assumptions about colors. Those assumptions were not friendly to this script. (I made a bad report on Phab as a result, see phab:T361785.)
I think it should be pretty easy to adjust this script so that instead of adding the CSS for each element directly, each element gets a class for each CSS and that CSS gets pulled into a "full" CSS declaration earlier in the script that always loads the entirety. I think that's modifying 143 and 157 to use $.addClass(), changing the related "css" in the JSON to "class" with class names, and then using addCSS() to get the actual CSS onto the page.
Is that reasonable? Izno (talk) 03:14, 9 April 2024 (UTC)
- Possibly. But that's beyond my paygrade. @b} 22:15, 9 April 2024 (UTC)]
- Ok, this works like I thought it would. I'm not sure of the best way to support custom rules. I think it would make more sense to do it like this in that case also. Assign some CSS to a known variable in unreliable-rules (
var unreliablerulecss = ...), load that by name in the core script, and then make similar changes to load cssclass instead of the CSS for each of the additional rules. We have about 15 pages of legacy to move over unless you want to support that for whatever reason.... some of those might even be simplified because they could choose to use the standard class names without resorting to custom color definition. Izno (talk) 23:54, 9 April 2024 (UTC)
- Ok, this works like I thought it would. I'm not sure of the best way to support custom rules. I think it would make more sense to do it like this in that case also. Assign some CSS to a known variable in unreliable-rules (
Cconfigure a script for me to treat sources differently than the defaults
Can I configure a script for me to treat sources differently than the defaults? For example, I would like to have MDPI journals displayed as normal sources, rather then "borderline" if an article in a journal by MDPI group has PMID and PMC. Another example is that I want Semantic Scholar ID attribute to also be displayed as normal rahter than "borderline".
As an example of configurable script, see User:Maxim_Masiutin/common.js where there is a custom hook 'refrenamer.rename' to assign default names for me differently than by default, naming references to articles with PMID citation attribute as "pmid1234567" (where 1234567 is an example PMID).
Can I do the same for the "unreliable" script? I viewed the code and it seems that I cannot do that other than making a fork (copy the whole script to my user area and change appropriate lines of code). Maxim Masiutin (talk) 11:09, 18 April 2024 (UTC)