Jump to content

User talk:GrapesRock

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Welcome!

[edit]

Hi GrapesRock! I noticed your contributions and wanted to welcome you to the Wikipedia community. I hope you like it here and decide to stay.

As you get started, you may find this short tutorial helpful:

Learn more about editing

Alternatively, the contributing to Wikipedia page covers the same topics.

If you have any questions, we have a friendly space where experienced editors can help you here:

Get help at the Teahouse

If you are not sure where to help out, you can find a task here:

Volunteer at the Task Center

Happy editing! Schazjmd (talk) 22:06, 1 June 2024 (UTC)[reply]

Barnstars!

[edit]
The Cleanup Barnstar
Awarded in appreciation of the work you're doing to make Wikipedia a better place. Thank you!
Jlahorn (talk) 13:18, 15 June 2024 (UTC)[reply]

Demographics section changes

[edit]

Per Your Contributions, why are you changing demographics information to estimated non-Decennial years, such as 2022, instead of 2020? 2020 was the last official census, every year since then is an unofficial estimate. If you going to start making this type of change in community articles, then you should probably discuss at Wikipedia:USCITY. • SbmeirowTalk17:41, 22 June 2024 (UTC)[reply]

Thanks for linking the guideline! I tried asking over at WP:WikiProject United States and went ahead with editing since I didn't hear anything. I'll work on updating my code over the next couple of days to be more in line with the guideline and then ask for feedback over on the US City talk page. Is it chill if I ping you in that message? Of course I won't go using my script until it's modified :-).
I chose to use solely ACS data mainly since I didn't want to bother mixing data sources. It seems to be an official estimate (I think extrapolating from ~1% of the population for 1 Year and 5% for 5 Year) from the Census Bureau and I saw other pages using it a lot (or saying that they're using Decennial Census Data, when only the ACS had that data).
Looks like I replaced 2010 Census Data (as in deleted 2010 Decennial data and added in 2022 ACS data) 3 times, should I add that back in? How about the 5 times I replaced 2000 Census Data? More generally, should I revert all of the changes that I made with the script, or keep them in since they do indeed add information? GrapesRock (talk) 18:25, 22 June 2024 (UTC)[reply]
I remember that one or more groups have already upgraded city articles in one or more states to official 2020 census text, which is why you need to look at what they did. As for myself, I would prefer "2020 census" section, then maybe "2025 estimate" section, then "2030 census" section. Adding sections for one or more of the following 2021 / 2022 / 2023 / 2024 / 2026 / 2027 / 2028 / 2029 is probably overkill. If estimate data is added, the section name should be simplified, such as "20XX estimate". We'll find out more how other people feel after you post on USCITY. • SbmeirowTalk11:07, 24 June 2024 (UTC)[reply]
[edit]

Hi GrapesRock! Nice work with the disambiguation links that you have been fixing. I noticed that you've been updating the list when you finish an entry, but it would be helpful if you also updated the 2 counters at the top at the same time, so that the progress bars are accurate (or at least mostly so - they'll always be a bit off based on partially-fixed entries, etc). Notice in this diff where, since I was moving two entries, each with two links, to the bottom, I updated the number of entries that have been fixed from 1309 to 1313 in two locations - one for the text, one for the progress bar.

I'm still relatively new to doing these myself, so there may be more procedures I'm unaware of, but I figured I'd mention it. Cleancutkid (talk) 20:30, 22 June 2024 (UTC)[reply]

Oh, huh, thanks! I'll make sure to do that going forward. I've gotten somewhat spoiled with tons of automatically updating progress bars that I figured this one was too :-) GrapesRock (talk) 20:35, 22 June 2024 (UTC)[reply]
It's not a problem at all - I know from experience that it can sometimes be a bit confusing figuring out how processes operate on here. There are some counters and lists that are automatically updated on the toolforge pages for the project, too, if you find that helpful. Cleancutkid (talk) 04:14, 24 June 2024 (UTC)[reply]

JUDI

[edit]

Hi, you are hitting it out of the park. Not sure how you do it. Don't say if it helps the spammers.

I need help with spam titles. The bot will convert |title=Situs Daftar to |title=Article Title (placeholder). But it needs to confirm the title is spam, and it does that be a regex match on keywords. This is the current regex string, very outdated:

((Hongkong|HK|Result|Toto) (HK|Pools|Prize)|Togle Live|Live (Casino|Draw|Slot)|(Casino|Slot|Bola|Judi|Game|Gacor) Online|Roulette Blog|[ ](Terpercaya|Judi|Situs|Daftar|Keluaran|Keluaran|Pengeluaran|Mostbet([.]com)?|Chia s?|Giris|Siteleri|Canli|Bahis|Bonusu|Dotdash)($|[ ]))

If you know other key terms to add, it would help the bot cleanup spam titles. -- GreenC 00:38, 3 September 2024 (UTC)[reply]

Thanks! (and thanks for developing the tools to deal with 'em!) It's been a wiki-obsession lately for whatever reason to hunt these down. It's kinda satisfying whenever I find a new one, and the feeling of making Wikipedia slightly better is groovy! Seems like the search is slowing down though, and I'll just passively stay on top of newly usurped domains.
Anyways, here are the search terms I've been using and cared to note down at some point that aren't covered already by your list:
  • insource:/togel/i
  • insource:"bermain"
  • insource:"Taruhan"
  • insource:"link alternatif"
  • insource:"pragmatic play"
  • insource:"maxwin"
Thai for slots:
  • insource:"สล็อต"
Thai for "web":
  • insource:"เว็บ"
Thai for deposit:
  • insource:"ฝาก"
Russian for casino:
  • insource:/казино/i
I'm sure that there's other signs of usurped titles... I do have "LOTRE4D : Bandar Lotre 4D, Game paling populer dengan hadiah terbesar 2024 !" noted down as one that doesn't have any of the search terms I was aware of (from lotre4d-borneo.com (I have no idea where I got this domain, probably one of the other domains redirects to it)) and I don't think is captured by any bit of that regex. From my experience, 4D is somewhat common in titles. In a similar vein, there's 88.
One thing that I've noticed is that some of the sites were added by either ReFill or Citation Bot, when there are redirects, such as in Ryan Wagler in this edit, which introduced mpltoto.com, which lost the original trenchtownmusic.com. Is there some good algorithmic way to deal with that? In the future, I'll make sure to note down whenever I see that happen,,,
I don't think I made any headway for figuring out search terms for crypto sites (such as southasianmedia.net which redirects to ccyport.com) or porn sites (such as radionigeriaenugu.com, whose page changes pretty frequently and loads inconsistently. Fwiw, when it loaded last there was nothing nsfw on specifically the home page, but the Archive does show that there definitely has been), both because I have so few examples and the fact that the examples are both from the Chinese family of scripts GrapesRock (talk) 02:02, 3 September 2024 (UTC)[reply]
This is great. AFAIK the only way we can detect these sites is the method you describe. And the only way these title strings get added are by those tools like Citation bot. If those tools ever prevented adding the titles, we would be in the dark finding usurped domains. -- GreenC 20:00, 4 September 2024 (UTC)[reply]
@GreenC Don't forget to add "rungkad". Also, you might want to modify "deposit" into "deposit pulsa". Veracious ^(•‿•)^ 10:08, 17 September 2024 (UTC)[reply]
Got all, thank you. -- GreenC 18:25, 17 September 2024 (UTC)[reply]

ArbCom 2024 Elections voter message

[edit]

Hello! Voting in the 2024 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 2 December 2024. All eligible users are allowed to vote. Users with alternate accounts may only vote once.

The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.

If you wish to participate in the 2024 election, please review the candidates and submit your choices on the voting page. If you no longer wish to receive these messages, you may add {{NoACEMM}} to your user talk page. MediaWiki message delivery (talk) 00:54, 19 November 2024 (UTC)[reply]

December 2024

[edit]

WP:JUDI

[edit]

Great work you're doing on this. Far beyond what I managed. Came across this one today which is a new gambling site to me while I was working on Domains for sale (which I feel is a similar problem to JUDI as the existing url is removed and new url, title etc inserted onto wiki) and wondered if your filters could add it in some way http://www.letsgotoponce.com/ Lyndaship (talk) 14:50, 20 December 2024 (UTC)[reply]

Ooh, yeah. I've encountered a couple of sites usurped for Chinese gambling, but I haven't really found a good way to actually find them yet. Just based on Google Translate, seems like that specific one has a fairly innocuous title which makes it more difficult to discover.
One website that I've found super helpful for finding domains is example3.com which has lists of domains sorted by keywords which should also be great for finding domains for sale (e.g. this list). I will probably be posting the script I've used for the gambling stuff later today which should be fairly easy to modify to look for domains for sale...
Update: The script is now here. If you wanted to use it for looking for for-sale domains you'd change the USURPED_PATTERN variable in the Python file to be a RegEx that captures those domains instead (if those words don't mean much, I'd be happy to help). GrapesRock (talk) 20:29, 20 December 2024 (UTC)[reply]
Thanks but all too technical for me. My limit is using insource for likely strings! Lyndaship (talk) 15:54, 21 December 2024 (UTC)[reply]