User talk:RojaLand
Add topicMay 2025
[edit]
Hello, I'm Cooldudeseven7. I noticed that you added or changed content in an article, Women in the United States Army, but you didn't provide a reliable source. It's been removed and archived in the page history for now, but if you'd like to include a citation and re-add it, please do so. You can have a look at referencing for beginners. If you think I made a mistake, you can leave me a message on my talk page. Thank you. Cooldudeseven7 join in on the tea talk 12:06, 6 May 2025 (UTC)
ArbCom 2025 Elections voter message
[edit]
Hello! Voting in the 2025 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 1 December 2025. 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 2025 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:51, 18 November 2025 (UTC)
November 2025
[edit]
wikimedia.org for assistance. Otherwise, if you are able to confirm that you are the user who created this account, please read the guide to appealing blocks (specifically this section), then add this below the block notice on your talk page: {{unblock|reason=Your reason here ~~~~}}. ~Lofty abyss 02:10, 29 November 2025 (UTC)- Lofty abyss - I saw your block on this account and agreed that the sudden behavior might suggest a compromised account. I ran a CheckUser and looked through all of the IP address, user agent, and client hint data that this account has used, and in order to gather some forensic information and determine if this was due to a compromised account. The technical data that I pulled, compiled, and examined provided me with a clear conclusion.
- This account has edited from only a few IP address ranges, and using only two different user agents that suggest that they edited between only two different devices over time. The IP address that the account was editing through when they were blocked was from one of the typical IP ranges that this account has edited through for the past few months, and the user agent used to make the disruptive changes was also the same device that they've used to edit for many months. The disruption also included edits that said that this user was a sock puppet, meaning that the disruption came from someone who's familiar with the term "sockpuppet" as well as other terms on this project.
- This information allows me to conclude that the disruption was not due to someone logging into this account from a new device, IP address, or location outside this account's typical patterns. The specific behavior and terms used also allows me to conclude that the disruption was not made by someone who gained unauthorized access to this user's device and used it to log into the account. The user is obviously familiar with the project. Therefore, I can conclude that the disruption is not the result of the account being compromised. ~Oshwah~(talk) (contribs) 03:05, 29 November 2025 (UTC)