Redirects to sketchy site. EvergreenFir(talk)22:28, 3 October 2022 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"20221003222800","author":"EvergreenFir","type":"comment","level":1,"id":"c-EvergreenFir-20221003222800-consumersolution.org","replies":[]}}-->
Adding class action lawsuits into company pages, so far I have found 4 "different" users involved in this abuse. VVikingTalkEdits19:33, 3 October 2022 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"20221003193300","author":"Viewmont Viking","type":"comment","level":1,"id":"c-Viewmont_Viking-20221003193300-lawow.org","replies":["c-Ohnoitsjamie-20221004222400-Viewmont_Viking-20221003193300"],"displayName":"VViking"}}-->
After initially adding some links as Garesasa11 (including vandalizing an ELN discussion) and getting a final warning, has switched to IP hopping. - MrOllie (talk) 13:50, 14 October 2022 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"20221014135000","author":"MrOllie","type":"comment","level":1,"id":"c-MrOllie-20221014135000-softwareshopk.com","replies":["c-Kuru-20221014173500-MrOllie-20221014135000"]}}-->
DoneSam Kuru(talk)17:35, 14 October 2022 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"20221014173500","author":"Kuru","type":"comment","level":2,"id":"c-Kuru-20221014173500-MrOllie-20221014135000","replies":[],"displayName":"Sam Kuru"}}-->
Both accounts already blocked for spamming, and I believe I've cleaned up all lingering instances. --JBL (talk) 19:09, 25 October 2022 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"20221025190900","author":"JayBeeEll","type":"comment","level":1,"id":"c-JayBeeEll-20221025190900-manualsnet.com","replies":["c-Ohnoitsjamie-20221026134900-JayBeeEll-20221025190900"],"displayName":"JBL"}}-->
Blog spam by IPs and socks. Apparition11Complaints/Mistakes18:26, 23 October 2022 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"20221023182600","author":"Apparition11","type":"comment","level":1,"id":"c-Apparition11-20221023182600-themoviesz.com","replies":[]}}-->
Add a couple more socks. Apparition11Complaints/Mistakes11:05, 25 October 2022 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"20221025110500","author":"Apparition11","type":"comment","level":1,"id":"c-Apparition11-20221025110500-themoviesz.com","replies":["c-Ohnoitsjamie-20221026231700-Apparition11-20221025110500"]}}-->
This is spam website with no, absolutely no connection or relevance to arlington cemetery, arlington national cemetery, or any other such cemetery. Links in WP to this website have been removed, Still, I request a block IOT avoid future spamming via WP. – S. Rich (talk) 02:49, 26 October 2022 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"20221026024900","author":"Srich32977","type":"comment","level":1,"id":"c-Srich32977-20221026024900-arlingtoncemetery.org","replies":["c-Anastrophe-20221026212300-Srich32977-20221026024900"],"displayName":"S. Rich"}}-->
The current owner of the domain has no connection to Arlington cemetery - and they disclose that on their 'About us' page. But indeed, their content is for the most part unrelated to Arlington, primarily dealing with drug abuse and PTSD among veterans (though even that is only minimally covered in a direct fashion).
The problem however is that the former holder of the domain did cover significant information related to Arlington cemetary and those interred there. Nearly all of the links that have been removed so far have included the direct archive pointers to archive.org, where the original articles are, providing that fully relevant information.
I took the liberty of reverting most (possibly all) of the removals that were performed, because they removed important sourcing for information in the articles.
I would strongly argue against putting in place a block on use of the domain, because of the archived content that is relevant.
That said, I do wish there was a better way of displaying the reference information, so that people would simply not have the opportunity to click on the wrong one of the two links provided. As well, the default wording is confusing, showing a hyperlink entitled "The original" for what is not the original, but in fact the current site. This needs correction as well. I'm not sure if it's incorrect application of the template by previous editors or some other issue - but I will investigate.
Let me be clear, I believe @S. Rich's removals of these were in good faith. cheers. anastrophe, an editor he is.21:23, 26 October 2022 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"20221026212300","author":"Anastrophe","type":"comment","level":2,"id":"c-Anastrophe-20221026212300-Srich32977-20221026024900","replies":[]}}-->
For future reference, I learned from another editor that in cases like this, one can use
|url-status=unfit or usurped
which will prevent the current url from even being linked to. Handy!
I"m going to modify the aforementioned cites to use them.02:07, 27 October 2022 (UTC)
__DTSUBSCRIBEBUTTONDESKTOP__{"headingLevel":2,"name":"h-ProcrastinatingReader-2021-12-08T11:53:00.000Z","type":"heading","level":0,"id":"h-top100_blog_charts-2021-12-08T11:53:00.000Z","replies":["c-ProcrastinatingReader-2021-12-08T11:53:00.000Z-top100_blog_charts","c-ProcrastinatingReader-20221023113600-top100_blog_charts"],"text":"top100 blog charts","linkableTitle":"top100 blog charts"}-->
__DTSUBSCRIBEBUTTONMOBILE__{"headingLevel":2,"name":"h-ProcrastinatingReader-2021-12-08T11:53:00.000Z","type":"heading","level":0,"id":"h-top100_blog_charts-2021-12-08T11:53:00.000Z","replies":["c-ProcrastinatingReader-2021-12-08T11:53:00.000Z-top100_blog_charts","c-ProcrastinatingReader-20221023113600-top100_blog_charts"],"text":"top100 blog charts","linkableTitle":"top100 blog charts"}-->
Regex requested to be blacklisted: top100\w*\.blog
Regex requested to be blacklisted: charly1300
Regex requested to be blacklisted: mickeycharts
Regex requested to be blacklisted: atrl.net\/forums
Regex requested to be blacklisted: hot100brasil\.com
Regex requested to be blacklisted: twitter.*?\/mickeycharts\b
Filter 554 is used to block spammy refs, matching the above regex. Pretty much the only disallow filter for sources, and not subject to community discussion, so probably shouldn't be a filter. Should be moved to the spam blacklist. ProcrastinatingReader (talk) 11:53, 8 December 2021 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2021-12-08T11:53:00.000Z","author":"ProcrastinatingReader","type":"comment","level":1,"id":"c-ProcrastinatingReader-2021-12-08T11:53:00.000Z-top100_blog_charts","replies":["c-Beetstra-2021-12-08T12:19:00.000Z-ProcrastinatingReader-2021-12-08T11:53:00.000Z"]}}-->
@ProcrastinatingReader: I split the regex into 5 domain regexes and tried to find some actual links as examples. Can you point me to examples for charly1300 and mickeycharts? (I just want to see whether we should immediately up this to XWiki. --Dirk BeetstraTC12:19, 8 December 2021 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2021-12-08T12:19:00.000Z","author":"Beetstra","type":"comment","level":2,"id":"c-Beetstra-2021-12-08T12:19:00.000Z-ProcrastinatingReader-2021-12-08T11:53:00.000Z","replies":["c-ProcrastinatingReader-2021-12-08T12:36:00.000Z-Beetstra-2021-12-08T12:19:00.000Z"],"displayName":"Dirk Beetstra"}}-->
@Beetstra: I think mickeycharts was mickeycharts.com (eg, [https:// twitter.com/MickeyCharts Twitter]), but seems to be an unregistered domain now. For charly1300: Wikipedia:WikiProject_Spam/LinkReports/charly1300.comProcrastinatingReader (talk) 12:36, 8 December 2021 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"2021-12-08T12:36:00.000Z","author":"ProcrastinatingReader","type":"comment","level":3,"id":"c-ProcrastinatingReader-2021-12-08T12:36:00.000Z-Beetstra-2021-12-08T12:19:00.000Z","replies":[]}}-->
---
I posted the above here before but it seemingly ended without action. I'm going to disable 554 (hist·log) momentarily - re-making this request so an admin can add these URLs to the spam blacklist as necessary. ProcrastinatingReader (talk) 11:36, 23 October 2022 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"20221023113600","author":"ProcrastinatingReader","type":"comment","level":1,"id":"c-ProcrastinatingReader-20221023113600-top100_blog_charts","replies":["c-Ohnoitsjamie-20221026135000-ProcrastinatingReader-20221023113600"]}}-->
@ProcrastinatingReader: Added to MediaWiki:Spam-blacklist. --OhNoitsJamieTalk13:50, 26 October 2022 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"20221026135000","author":"Ohnoitsjamie","type":"comment","level":2,"id":"c-Ohnoitsjamie-20221026135000-ProcrastinatingReader-20221023113600","replies":["c-Ohnoitsjamie-20221026135900-Ohnoitsjamie-20221026135000"]}}-->
Dirk Beetstra - The handler didn't add \b word boundary prefix/suffixes to these, but that didn't seem right; I manually added them, but wanted to make sure that omission wasn't by design. OhNoitsJamieTalk13:59, 26 October 2022 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"20221026135900","author":"Ohnoitsjamie","type":"comment","level":3,"id":"c-Ohnoitsjamie-20221026135900-Ohnoitsjamie-20221026135000","replies":["c-Beetstra-20221027102000-Ohnoitsjamie-20221026135900"]}}-->
If you have the {{BLRequestRegex}} then the handler takes those regexes literally. It only adds \b around the domains/links, and escapes the needed characters, in {{LinkSummary}}/{{BLRequestLinks}}. If you want to blacklist '\bmickeycharts\b', you have to request that regex, not 'mickeycharts'. It depends sometimes whether you really want to use or even need the \b's. Dirk BeetstraTC10:20, 27 October 2022 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"20221027102000","author":"Beetstra","type":"comment","level":4,"id":"c-Beetstra-20221027102000-Ohnoitsjamie-20221026135900","replies":[],"displayName":"Dirk Beetstra"}}-->
