User talk:Dylnuge

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

BKFIP[edit]

Hi Dylnuge, I have created this SPI thread about some IP ranges that I suspect are / were being used by BKFIP to disrupt a wide variety of articles, I just thought I'd let you know about this SPI since you were directly involved with them in the past, creating this AN/I thread which has went stale unfortunately. But there still seem to be disruptive edits coming from that /37 IPv6 range to this very day... — AP 499D25 (talk) 05:49, 11 July 2023 (UTC)[reply]

Thanks for letting me know! They stopped editing on the /64 in question right after it was reported to ANI, which suggests to me they are indeed changing their lease assignment. I left a note on the SPI about the /37—unfortunately I doubt that blocking that entire range will be productive—but hopefully there's something that can be done here. Dylnuge (TalkEdits) 14:47, 11 July 2023 (UTC)[reply]

Re: July 2023[edit]

Hello, Dylunge. My apologies on the edit on Lapsus$. After I have added the hacker's name on the Untitled Grand Theft Auto game page, that is where I learned from a user about WP:BLPNAME.

As for the citation, I was going to add it later when I get onto a desktop. Editing on Wikipedia on mobile is cumbersome.

In any case, I would like to thank you for further educating me about these rules with the names. Unless he was some sort of world class, international hacker, I now know it is best to keep his name out of the spotlight, regardless if he is an adult or not. 2A02:A020:86:180B:91A5:C50D:7F8F:9640 (talk) 11:44, 17 July 2023 (UTC)[reply]

Thanks and no worries! Happy editing! Dylnuge (TalkEdits) 16:14, 17 July 2023 (UTC)[reply]

Colleen Ballinger[edit]

Re: the Colleen Ballinger talk page, also please note the extensive discussions on that page concerning the referencing of the material about these accusations that was eventually added to the article by consensus. Thanks! -- Ssilvers (talk) 03:31, 24 July 2023 (UTC)[reply]

Thanks! I did peruse the previous edit requests and discussion and wasn't planning on making any change without carefully reviewing the existing consensus, but figured it was worth noting to that editor that they weren't requesting a proper change. I also missed that which sources to use was a specific point of earlier contention; thanks for letting me know! Dylnuge (TalkEdits) 03:38, 24 July 2023 (UTC)[reply]

Charles III requested move discussion[edit]

There is a new requested move discussion in progress for the Charles III article. Since you participated in the previous discussion, I thought you might like to know about this one. Cheers. Rreagan007 (talk) 06:31, 24 July 2023 (UTC)[reply]

Thanks for the notice; I think I'll avoid the mess this time ;) Dylnuge (TalkEdits) 16:20, 24 July 2023 (UTC)[reply]

Re: Talk:Oneida Baptist Institute[edit]

Semi-protected edit request on 26 July 2023

Thanks for helping me out in the sources problem today. I just started using Wikipedia and I am attempting to edit the Wikipedia page for the school I work at. Is there any way to get past the “semi-protected” status of this page? A recent graduate of the school is the one who made the incorrect edits, and I am attempting to fix their attempt at a practical joke for the sake of the schools’ reputation.

Thanks! Joseph Thomas Cochrane (talk) 01:59, 27 July 2023 (UTC)[reply]

Hey @Joseph Thomas Cochrane, welcome to Wikipedia! I'm happy to help with the changes you want to make! Note that working for the subject of the article presents a potential conflict of interest in editing the page; while you can directly edit pages you have a conflict of interest on, it is recommended that instead you use edit requests similar to the one you already filed (you can use the Edit COI template for these on pages with no protection). I also recommend putting a note on your user page indicating this conflict of interest; see WP:DISCLOSE for instructions on this.
Regarding the semi-protection, this is a way to prevent vandalism on pages; in this case, it was put in place to prevent the vandalism you're trying to fix. You'll be able to edit semi-protected pages directly when your account is autoconfirmed, which means it at least four days old and has made at least ten edits. Currently you already meet the second condition (with 18 edits); your account will be autoconfirmed on July 30 at 21:40 UTC. It's rare for users to be given an exemption for this, since the threshold is intentionally very low. Also, even once you are autoconfirmed, I strongly encourage you to use the edit COI template for editing Oneida Baptist Institute. These edit requests are usually responded to decently quickly by editors who volunteer to help ensure that edits meet Wikipedia's guidelines on neutrality and verifiability. Dylnuge (TalkEdits) 02:25, 27 July 2023 (UTC)[reply]

Other British monarch requested move discussions currently taking place[edit]

Since you recently participated in the Charles III requested move discussion, I thought you might like to know that there are two other discussions currently going on about other British monarch article titles here and here. Cheers. Rreagan007 (talk) 22:28, 30 July 2023 (UTC)[reply]

Glen Waverley line[edit]

Hi @Dylnuge. I was willing to fix the issues that you pointed out in the article, but I've been busy for the last few hours and was going to get it tonight. Is there anyway to undo the fail to allow me to fix the mistakes and then continue the review? HoHo3143 (talk) 00:02, 18 August 2023 (UTC)[reply]

Hey @HoHo3143. Unfortunately, I think the sourcing issues are too pervasive to be fixable as part of the GAN review. I spot checked seven different statements from different parts of the article and every single one of these had significant issues. This is the kind of problem I'd consider tagging with a {{cite check}} at the top of the article. I think it would be useful to find sources that cover Melbourne rail lines and Glen Waverley in depth and use those to rebuild much of the article. I did check on Discord with @Premeditated Chaos who was kind enough to review my sourcing examination and weigh in with a second opinion; she confirmed that the sourcing issues were a valid and significant concern.
I'd be happy to keep chatting about how to improve the article but I don't think it's ready for GAN at this time. I'm really sorry it turned out this way and I hope my review comments are helpful in preparing the article for a future nomination. Dylnuge (TalkEdits) 00:25, 18 August 2023 (UTC)[reply]
Ok thank you for the additional feedback @Dylnuge. I've added fixing the article to my to do list and will get to it soon. Not your fault that the review has failed but I have taken this feedback on for future articles. Just a bit disheartening that this is the third time its happened...
It'll be fine though as I'll renominate them soon. HoHo3143 (talk) 00:43, 18 August 2023 (UTC)[reply]
HoHo3143, if this is the third time your articles are being failed on sourcing issues, I would take a step back and review your writing process. A few instances of source-text issues is human error - everyone is liable to do it. People overextend what the source says, accidentally cite the wrong thing, misunderstand the source, the article gets edited out of sync with the source, whatever. But three GA fails on this basis says that not only is it an ongoing issue, it's an ongoing issue you aren't conscious of, which is problematic.
When I glanced at the review at Dylnuge's request, I saw what seemed to be a lot of sourcing used kind of as a guess, like, "I'm talking about electrification, here's a source about electrification" even when the source doesn't cover the actual facts it's being cited to support. The disability one he pointed out is the same - it's a source that talks about disability, but does not say that all stations are built in compliance with the 1992 DDA. Maps can't be used to confirm dates unless they say, textually, that such and such happened on such and such day. Otherwise all the map tells us is that X thing was on a map by Y date, which is different than knowing that X opened on Y date.
Can you see why these concerns are a serious issue? ♠PMC(talk) 00:49, 18 August 2023 (UTC)[reply]
Thank you @Premeditated Chaos. I do understand the issue. The problem has been that I completed and nominated these articles awhile ago and continued working on more, with very little of them being reviewed. Now that they are being reviewed, I'm learning of the issues. Some articles have been successful with minimal issues and others not so much (usually the ones from earlier on). These issues are important and I'm making sure not to commit them in the articles that I am currently working on for GA status. So I have been learning about the issues throughout the process and am making sure to prevent them from occurring in future articles. Thank you for your help. HoHo3143 (talk) 00:57, 18 August 2023 (UTC)[reply]
Frankly, with the issues being this pervasive, I would recommend removing all your remaining nominations and going through them one by one to confirm the sourcing is appropriate, and only renominate when you are confident that all the sourcing issues have been addressed. Leaving articles up (or saying that you will "renominate them soon") that you know have serious problems with the sourcing is really unfair to reviewers, who are operating under the expectation that articles have been written in a properly policy-compliant way. Don't force people to continue to fail your work. ♠PMC(talk) 01:02, 18 August 2023 (UTC)[reply]
@Premeditated Chaos ok I've decided what I'll do. Tonight (when I have some extra time) I will go through and fix all the currently nominated articles. For the ones I don't finish by tonight, I'll take them down and renominate them once the issues have been fixed. The recent ones are much better than the first, so they will take less time to fix. HoHo3143 (talk) 02:14, 18 August 2023 (UTC)[reply]
@HoHo3143 I'm sorry for the stress this must be causing and appreciate your work on these articles. Please do let me know if there's any questions I can answer; I'd be happy to help you with sourcing, prose, or anything else. Dylnuge (TalkEdits) 02:35, 18 August 2023 (UTC)[reply]
Don't worry @Dylnuge its not your fault (and @Premeditated Chaos). I appreciate the feedback you have provided especially as you have both been polite about giving it. If I need any help I'll make sure to reach out. HoHo3143 (talk) 02:38, 18 August 2023 (UTC)[reply]

Thank you for participating in the August 2023 GAN backlog drive[edit]

The Premium Reviewer Barnstar
We really appreciate that you reviewed several GANs during the drive. Due in part to your efforts, the backlog of unreviewed nominations was reduced by 440 articles, an astonishing 69 percent.

MediaWiki message delivery (talk) 07:10, 6 September 2023 (UTC)[reply]

DYK for Autonomous (novel)[edit]

On 1 October 2023, Did you know was updated with a fact from the article Autonomous (novel), which you recently created, substantially expanded, or brought to good article status. The fact was ... that Annalee Newitz chose to set their debut novel Autonomous in the Canadian prairies because it was "the kind of place that often gets forgotten"? The nomination discussion and review may be seen at Template:Did you know nominations/Autonomous (novel). You are welcome to check how many pageviews the nominated article or articles got while on the front page (here's how, Autonomous (novel)), and the hook may be added to the statistics page after its run on the Main Page has completed. Finally, if you know of an interesting fact from another recently created article, then please feel free to suggest it on the Did you know talk page.

RoySmith (talk) 00:02, 1 October 2023 (UTC)[reply]

ArbCom 2023 Elections voter message[edit]

Hello! Voting in the 2023 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 11 December 2023. 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 2023 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:24, 28 November 2023 (UTC)[reply]