Talk:Spam blacklist/Archives/2017-12
Proposed additions
logindevelopers.org
logindevelopers.org
- (LinkSearch: meta | en | es | de | fr | ru | zh | simple | c | d | Wikipedias: top 25 · 50 · major wikis · sc · gs)(Search: Google | en (G) | fr (G) | de (G) | meta (G) | backlinks | → links ←)logindevelopers.org
- (Reports: Report ← track | XWiki | Local | en | find entry)(DomainTools: whois | AboutUs | Malware?)
loginidol.org
- (LinkSearch: meta | en | es | de | fr | ru | zh | simple | c | d | Wikipedias: top 25 · 50 · major wikis · sc · gs)(Search: Google | en (G) | fr (G) | de (G) | meta (G) | backlinks | → links ←)loginidol.org
- (Reports: Report ← track | XWiki | Local | en | find entry)(DomainTools: whois | AboutUs | Malware?)
Spamming on Beta Cluster. Potential propagation to production. Adding in a sec. —MarcoAurelio (talk) 20:21, 7 December 2017 (UTC)
files.wordpress.com
files.wordpress.com
- (LinkSearch: meta | en | es | de | fr | ru | zh | simple | c | d | Wikipedias: top 25 · 50 · major wikis · sc · gs)(Search: Google | en (G) | fr (G) | de (G) | meta (G) | backlinks | → links ←)files.wordpress.com
- (Reports: Report ← track | XWiki | Local | en | find entry)(DomainTools: whois | AboutUs | Malware?)
We are having spambots runninng riot with the domain at the moment, so at least as a temporary measure I am adding the extended domain as an emergency measure. We can talk about its removal or fine-tuning the regex. — billinghurst sDrewth 04:40, 23 December 2017 (UTC)
Proposed removals
Troubleshooting and problems
Discussion
How can I prove that I am not a paid editor?
I just imported 25 images from the website of the University of California at Santa Barbara and I'm sure that COIBot might note me as the exclusive user of this link and I've used it numerous of times on Wikipedian like at w:nl:Riukiuaanse mon and one Commons category is Commons:Category:Kokin kousei, Shinsen zeni kagami, I know the external linking policy and I have no COI, but how can I declare this before this link gets globally blacklisted and every mention of the University of California at Santa Barbara gets removed? --Donald Trung (Talk 🤳🏻) (My global lock 🔒) (My global unlock 🔓) 13:45, 15 December 2017 (UTC)
- Don't fuss COIBot's reports. It watches and runs reports, it makes no accusations. Users read reports and make assessments. You jump to conclusions. — billinghurst sDrewth 14:59, 15 December 2017 (UTC)
- I just don’t want a repeat of this and this (this reference was placed here years ago, and not by me), and I am currently planning on importing over 300 images from Art-Hanoi to Wikimedia Commons and importing a full book from that same website to Wikisource, I also used that website as a source on multiple wiki’s so I fear that if I do that it could get blacklisted, when I notified the removing party the last time he stated that I have "an obvious COI" but I can’t tell how or why other than using it as a source. Since I write about obscure subjects I will usually be the person to mostly use a link. Can I at least request that when Art-Hanoi or the University of California at Santa Barbara get reviewed by "spam fighters" that they will look objectively at what those links support instead of just blindly removing references? I don’t want the situation to repeat. --Donald Trung (Talk 🤳🏻) (My global lock 🔒) (My global unlock 🔓) 15:34, 15 December 2017 (UTC)
- @Donald Trung: Do you understand why that link was (considered to be) blacklisted? Do you understand why global locks, local blocks, abusefilters, etc. etc. are being applied? Do you understand why Arbitration Committees ban, block or desysop people? Since you keep failing to drop the stick (see this discussion and your signature), obviously you don't. Core policies apply to anyone, I do not understand why you think it is fine to sock (and even still show understanding for others who do). As I suggested elsewhere: Drop it. Edit. Communicate. Now! --Dirk Beetstra T C (en: U, T) 07:35, 19 December 2017 (UTC)
- This section was archived on a request by: — billinghurst sDrewth 23:07, 13 February 2018 (UTC)
Change to BLHandler
I have implemented here in our SBHandler gadget a change adding 2 possibilities for blacklisting:
- {{BLRequestRegex}}: template takes a parameter that is a regex. Is passed to the Blacklist unaltered.
- {{BLRequestLink}}: template takes a full link (not only a domain, e.g.), changes it to a regex, and passes that to the blacklist
- {{LinkSummary}}: as usual, just a domain.
The three are handled in order - if there are BLRequestRegex-es in the section, it will ONLY pass those (ignoring BLRequestLink and LinkSummary); if there is no BLRequestRegex but BLRequestLink-s, it will ONLY pass the parameters of BLRequestLink (ignoring the LinkSummaries), or it will only pass the domains in the LinkSummaries. (@Billinghurst:, see the Twitter request above). --Dirk Beetstra T C (en: U, T) 07:42, 19 December 2017 (UTC)
- Thanks Beetstra. Apart from using here, it will be useful in COIBOt's XWiki entries to capture the specific components. I have been doing a few more of these recently as the spambots have been using these extra links as good flags of problematic intent. — billinghurst sDrewth 11:12, 19 December 2017 (UTC)
- Oh, this only works on the requests on this page, on the /XWiki/domain pages the to-be-blacklisted information is parsed out of the title of the report. --Dirk Beetstra T C (en: U, T) 11:34, 19 December 2017 (UTC)