This is an archive of past discussions with User:Eagles247. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page.
Recently, several Wikipedia admin accounts were compromised. The admin accounts were desysopped on an emergency basis. In the past, the Committee often resysopped admin accounts as a matter of course once the admin was back in control of their account. The committee has updated its guidelines. Admins may now be required to undergo a fresh Request for Adminship (RfA) after losing control of their account.
What do I need to do?
Only to follow the instructions in this message.
Check that your password is unique (not reused across sites).
Check that your password is strong (not simple or guessable).
Enable Two-factor authentication (2FA), if you can, to create a second hurdle for attackers.
How can I find out more about two-factor authentication (2FA)?
Administrator account security (Correction to Arbcom 2019 special circular)
ArbCom would like to apologise and correct our previous mass message in light of the response from the community.
Since November 2018, six administrator accounts have been compromised and temporarily desysopped. In an effort to help improve account security, our intention was to remind administrators of existing policies on account security — that they are required to "have strong passwords and follow appropriate personal security practices." We have updated our procedures to ensure that we enforce these policies more strictly in the future. The policies themselves have not changed. In particular, two-factor authentication remains an optional means of adding extra security to your account. The choice not to enable 2FA will not be considered when deciding to restore sysop privileges to administrator accounts that were compromised.
We are sorry for the wording of our previous message, which did not accurately convey this, and deeply regret the tone in which it was delivered.
XTools Admin Stats, a tool to list admins by administrative actions, has been revamped to support more types of log entries such as AbuseFilter changes. Two additional tools have been integrated into it as well: Steward Stats and Patroller Stats.
Arbitration
In response to the continuing compromise of administrator accounts, the Arbitration Committee passed a motion amending the procedures for return of permissions (diff). In such cases, the committee will review all available information to determine whether the administrator followed "appropriate personal security practices" before restoring permissions; administrators found failing to have adequately done so will not be resysopped automatically. All current administrators have been notified of this change.
Following a formal ratification process, the arbitration policy has been amended (diff). Specifically, the two-thirds majority required to remove or suspend an arbitrator now excludes (1) the arbitrator facing suspension or removal, and (2) any inactive arbitrator who does not respond within 30 days to attempts to solicit their feedback on the resolution through all known methods of communication.
You deleted the starting quarterbacks for both the San Antonio Commanders and Orlando Apollos
Hello, why did you deleted from the roster list the starting quarterbacks of both of these teams?. Do you know that the AAF no longer exists and will not be in operation next year because of the lawsuits they have ?. You need to leave for future reference the roster that played during its lone season. Hopefully you can give an explanation of your reasoning.Tecmo (talk) 13:46, 5 May 2019 (UTC)
My understanding is that a player is a rookie in the NFL only if he is in his first year of professional football AND the contract he signs with an NFL team is his first professional contract. Any player who plays in another league (e.g., the CFL) and then signs with an NFL team is not a rookie, but a first-year player.
Johnson, according to the press release,[1] played in the AAF last season, so he is not a rookie, but a first-year player. The same applied to Blake Jackson last season for the Browns; he had signed with a CFL team before signing with the Browns, so he was a first-year player, not a rookie. — Preceding unsigned comment added by Lugubrious DBB (talk • contribs) 16:10, 17 May 2019 (UTC)
Regarding the AAF block; it was specifically and NFL exclusive out clause, which is why the NFL was the one organization named. As stated on their website still: "We are grateful to our players, who delivered quality football and may now exercise their NFL-out clauses in our contract."[1]
There was a story back when all this was going on, I think in the Canadian press, that made roughly the same points, but all I can currently find is this piece regarding the restriction to the out clause, ignoring it, and the possibility of being sued. "Third, the CFL could simply ignore the AAF’s alleged directive and sign the players. There is a good chance the AAF would take no action, save for sending a sternly-written letter penned by a lawyer. The AAF likely would not want to incur additional attorneys’ fees by suing the CFL. This is particularly the case given that the AAF will probably need to spend considerable monies defending against lawsuits. Of course, the CFL might be risk averse and not interested in taking a chance that signing AAF players would bring about a lawsuit."[2] — Preceding unsigned comment added by CestusHaberdasher (talk • contribs) 20:46, 19 May 2019 (UTC)
As you commented on my talk page about unhelpful edits, I decided that I'll focuse more on references and other things and not updating scripts. Sorry for the unhelpful edits, keep up the work Scribbley (talk) 23:42, 3 June 2019 (UTC)
russell okung citation
What is wrong with my citations? I have sourced this information from the actual person, and will continue to do so. Have you looked at the actual references? Theses are his exact words and you should respect these citations. If I may ask, what more would be required to have you stop undoing my work. He has clearly said these things and retweeted another person that mentions that he is evangelizing bitcoin to others on his team and around the world through his followers. — Preceding unsigned comment added by Lightningchargers (talk • contribs) 17:12, 5 June 2019 (UTC)
The CSD feature of Twinkle now allows admins to notify page creators of deletion if the page had not been tagged. The default behavior matches that of tagging notifications, and replaces the ability to open the user talk page upon deletion. You can customize which criteria receive notifications in your Twinkle preferences: look for Notify page creator when deleting under these criteria.
Twinkle's d-batch (batch delete) feature now supports deleting subpages (and related redirects and talk pages) of each page. The pages will be listed first but use with caution! The und-batch (batch undelete) option can now also restore talk pages.
Miscellaneous
The previously discussed unblocking of IP addresses indefinitely-blocked before 2009 was approved and has taken place.
By the way eagles nice to meet you ~sorry for my mistake ~ I was in a rush and didn't do my research like I normally do before I ever revert ~ you know what they say, the one time you don't cross your t's and dot your i's is the time that you will get bit in the butt ~ nice to meet you again ~ mitch ~ Mitchellhobbs (talk) 02:13, 14 June 2019 (UTC)
I would request if you could make the protection level on Anthony Davis extended confirmed because of wrongful editing nothing is confirmed till free agency starts. Scribbley (talk) 23:18, 15 June 2019 (UTC)
@Scribbley: It's already at that protection level unfortunately. You just have to undo changes by editors who don't fully understand how official announcements work, and explain to them why you are doing so in hopes that they learn for the future. It's very frustrating, especially since there's a template at the top with an explanation that they ignore. Eagles24/7(C)23:28, 15 June 2019 (UTC)
@Scribbley: My bad, extended confirmed is a newer protection I wasn't familiar with and have changed the protection on Davis' page to that one. Thanks! Eagles24/7(C)23:47, 15 June 2019 (UTC)
Hello Eagles247, you mentioned on my talk page that an edit I made to Larry Dierker's Page was reverted (by Yankees10). I wrote on Yankee10's page to ask what specifically could be done better to avoid getting the edit reverted, but I they have not responded to my comment. I don't want my edit to come across as an ad, but I do want to communicate that Larry Dierker has pursued other things in his later career. Do you have any recommendations on what content should be removed that would make it seem like it isn't an ad? I've reviewed the Wikipedia guidelines and I'm still not sure. Here's my original edit:
In 2017, Dierker teamed up with Benjamin Scardello of Houston, Texas to promote over 500 original and unique Baseball Stories Dierker had researched, written and recorded between 1982 and 1995. The stories contain information starting from the early days of baseball around 1900.
The two agreed to a digital entrepreneur endeavor to build a Podcast Website, www.49sfastball.com, converting the Baseball Stories into easily accessible Podcasts. The stories include a wide range of subjects and little known “back story” narratives about Players, Stadiums, Records, Promos and Unusual Events, Pitching, Openers and Debuts, Hitting, and All-Star Games.
The Podcasts can be heard on iTunes, Google Play, Spotify, AnyPod, Stitcher, Tune In, and Soundcloud.
In addition to the Podcasts, other relevant baseball information is available on the website including, Current Blog Articles, a Vast MLB Resources Section linking visitors to all of the top baseball websites, including colligate baseball. There’s even a “Contests and Prizes” section where participants can win MLB Baseball memorabilia.
Podcast Website Address: www.49sFastball.com Content: Iconic Baseball Podcast Stories Library & More Current Podcast Inventory: ~500 Historical Perspective: from the 1900s to 1995 Copyright: 49sFastball
As a co-founder with Scardello of 49sFastball.com, Dierker continues to provide new content for the website and is an active speaker, spokesperson, and proactive with philanthropic causes. Both Dierker and Scardello look to advance and promote the interest in our National Past Time by providing a look at baseball from a different time and a unique perspective. — Preceding unsigned comment added by Convergent1 (talk • contribs) 13:54, 17 June 2019 (UTC)
@Convergent1: Unfortunately, almost all of the content is promotional in nature and cannot be accepted on Wikipedia. I suggest adding a sentence like "In 2017, Dierker and Benjamin Scardello created a podcast called 49's Fastball in which Dierker shares baseball stories he researched going back to the early years of baseball." with a third-party reference attributed at the end. If you need more help with what is not acceptable to include on Wikipedia, please see WP:PROMO (specifically #5). Eagles24/7(C)00:27, 19 June 2019 (UTC)
The edit of mine you undid was from a vandal who was making small edits that were adding incorrect info, so it's not a big deal for me. But after reviewing your reasoning for reverting me, I was curious as to how we usually handle "ceremonial contracts". I ask because neither NFL.com or Pro Football Reference include these seasons in the player's lists of seasons played. A more recent example I can think of is Jordy Nelson. Was there discussion that determined consensus to include these seasons in the player's infobox? Just curious. Thanks, « Gonzo fan2007(talk) @ 19:35, 20 June 2019 (UTC)
@Gonzo fan2007: I’m not sure I understand, the vandal removed the ceremonial contract season that was added by a different user and you reverted his edit. We don’t show ceremonial contracts in the infobox. Eagles24/7(C)14:13, 22 June 2019 (UTC)
I did not even think about that. Just a coincidence. You seem to be one of the few really active ones this time of year on the NFL articles. Great work overall! Red Director (talk) 15:58, 28 June 2019 (UTC)
In a related matter, the account throttle has been restored to six creations per day as the mitigation activity completed.
The scope of CSD criterion G8 has been tightened such that the only redirects that it now applies to are those which target non-existent pages.
The scope of CSD criterion G14 has been expanded slightly to include orphan "Foo (disambiguation)" redirects that target pages that are not disambiguation pages or pages that perform a disambiguation-like function (such as set index articles or lists).
The Wikimedia Foundation's Community health initiative plans to design and build a new user reporting system to make it easier for people experiencing harassment and other forms of abuse to provide accurate information to the appropriate channel for action to be taken. Community feedback is invited.
Miscellaneous
In February 2019, the Wikimedia Foundation (WMF) changed its office actions policy to include temporary and project-specific bans. The WMF exercised this new ability for the first time on the English Wikipedia on 10 June 2019 to temporarily ban and desysop Fram. This action has resulted in significant community discussion, a request for arbitration (permalink), and, either directly or indirectly, the resignations of numerous administrators and functionaries. The WMF Board of Trustees is aware of the situation, and discussions continue on a statement and a way forward. The Arbitration Committee has sent an open letter to the WMF Board.
Your reversion of stub sorting and stub tag removal
Per my earlier response to your inquiry on my talk page, @User:Eagles247, I'm reposting our discussion here on your talk page just to be sure that you see my response to your inquiry. 47thPennVols (talk) 19:27, 3 July 2019 (UTC)
Actually it would appear that the Cowboys site no longer has that, and the article I linked, while the title says injury settlement, the actual article only said waived/injured. I'll look into it but feel free to put him on IR for now. RevanFan (talk) 02:16, 3 August 2019 (UTC)
I'll just give this a few days, maybe a week, for the website to reflect him being on IR. But if he is still not on there by then, then will he ever be? Does being waived/injured guarantee that they revert to IR if they go unclaimed by other teams? I just figured it was an option because I've seen players get W/I and never end up on IR. ~ Dissident93(talk)12:29, 3 August 2019 (UTC)
@Dissident93: Sometimes players are given injury settlements at the same time they are waived/injured, in that case they wouldn’t revert to IR. But in most cases injury settlements come after the player is already on IR. In this case specifically, he has definitely reverted to IR per the official league transactions wire (used by NFLTradeRumors, RosterMon, and CBS Sports). From past experiences, team websites are sometimes not privy to the official league transaction wire and might not know a player has reverted to IR after clearing waivers, so they won’t add the player to the list on their website. It’s frustrating, because you’d assume the official team website would be 100% accurate, but the people who update the rosters work in the marketing department instead of the football operations staff. Eagles24/7(C)13:27, 3 August 2019 (UTC)
I'll just wait like a week to see if he gets added, but at some point if he's still not listed on the roster, then we shouldn't list him here either. ~ Dissident93(talk)14:50, 4 August 2019 (UTC)
But then how will we know when he's eventually released from it if he never got added to the roster and thus gets removed from it, unless somebody catches a transaction that mentions it or something? Is there a third source independent of NFL.com transactions and team rosters that we can use to check this sort of stuff? ~ Dissident93(talk)14:56, 4 August 2019 (UTC)
NFL.com also shows a transaction for Dunn as "Reserve/Injured from Waived/Injured; Not Against 90" (can't link here because there's no permalink but if you go to [3] and search "Dunn" it will appear). Every transaction gets reported, always, on the official transaction wire (NFLTradeRumors posts the report daily, and RosterMon and CBSSports have it as well), so we'll see it through one of those sites if/when it happens. Tyrone Robertson was on the reserve/suspended list for 14 years and when he was finally waived from it by the Bills in 2016, it was reported. So ya gotta have some faith in the NFL news outlets. Eagles24/7(C)15:07, 4 August 2019 (UTC)
He is still not listed on the roster as of today, and the team's official transactions simply says he was simply waived outright. If he is still not listed on the roster by the time of the final 53, then you shouldn't oppose me removing him again, right? ~ Dissident93(talk)13:45, 18 August 2019 (UTC)
Nope, there are still multiple independent reliable sources that contradict the primary source. When he is officially removed from the list by the Redskins, we will reflect the same here. Eagles24/7(C)01:09, 19 August 2019 (UTC)
Yes, I am aware that it is not a guarantee that waived/injured always leads to the placement on IR. In Dunn's case specifically, it has been reported by NFL.com and CBSSports.com that he was placed on IR after clearing waivers. It appears that Sickels was not placed on IR as you said. I haven't seen "Waived, Injury Waiver" before, but it appears to be a different designation than waived/injured or waived with an injury settlement. Eagles24/7(C)16:37, 19 August 2019 (UTC)
Following a research project on masking IP addresses, the Foundation is starting a new project to improve the privacy of IP editors. The result of this project may significantly change administrative and counter-vandalism workflows. The project is in the very early stages of discussions and there is no concrete plan yet. Admins and the broader community are encouraged to leave feedback on the talk page.
Since the introduction of temporary user rights, it is becoming more usual to accord the New Page Reviewer right on a probationary period of 3 to 6 months in the first instance. This avoids rights removal for inactivity at a later stage and enables a review of their work before according the right on a permanent basis.
@Callmestarbucks: I see what you mean, but the name of the team is the Jacksonville Dolphins much like the Texas Longhorns is the University of Texas' sports team name. I've made a change that hopefully clears a little bit of it up, but I'm not sure how much more we can do there without calling the team by an incorrect name. Eagles24/7(C)00:59, 5 August 2019 (UTC)
Your idea to merge the articles is a good one, I concede that fact. However I feel that with separate articles, the pages feel less... Cluttered... They can be easier to read for some people. James-the-Charizard (talk) 04:06, 5 August 2019 (UTC)
@James-the-Charizard: Thanks for the input. In general, I was looking at how Wikipedia handled XFL team articles since that league also only lasted one season (i.e. Birmingham Thunderbolts). The AAF team would not be notable in itself if the one season did not get played, and that's part of my rationale. Eagles24/7(C)00:50, 6 August 2019 (UTC)
@PhoenixRancor: See User talk:Eagles247#Casey Dunn. Team websites are typically inaccurate about transaction minutiae for whatever reason, but according to websites that pull from the official NFL transactions wire, Valentine was waived/injured and then placed on IR after clearing waivers. If you go to this link from NFL.com and search "Valentine" you will see he was placed on IR on August 8. Eagles24/7(C)17:27, 12 August 2019 (UTC)
@Eagles247: I got tweeted back from one of the cardinals reporters (Kyle Odegard) that Valentine was released not placed on IR. I'm kinda confused on what to do next and wanted to get a second opinion. PhoenixRancor (talk) 5:24, 14 August 2019 (UTC)
@PhoenixRancor: I'd still go with the official NFL transactions wire that's been reported in numerous places over a reporter for the team website. The websites just aren't as accurate as they should be. Eagles24/7(C)12:27, 14 August 2019 (UTC)
@Eagles247: Hey update for you, apparently the nfl transactions changed to he was fully released instead of injured reserve. So I dont know what to do now. PhoenixRancor (talk) 3:31, 20 August 2019 (UTC)
Hello. We haven't spoken in about 7 and a half years, but you may remember an editor who caused a lot of trouble between late 2011 and early 2012 by the name of 1ravensnflfan who was eventually blocked indefinitely for using a sockpuppet. That was me. I was unblocked on request in December 2015, and have since then mostly stayed away from editing football-related articles but have done a lot of editing on history articles. I just wanted to let you know that when I was editing before, I was 12 years old and only in the seventh grade. I was way too young and immature to be on Wikipedia. I just wanted to offer a very belated apology for being such a pain the ass. Display name 99 (talk) 13:22, 13 August 2019 (UTC)
I didn't know, since I am not over at the Commons... And it had been here for a bit, which makes me feel dumb for reverting a correct ousting of the image earlier (by an IP)... (I'm not really on any other Wikimedia sites.) James-the-Charizard (talk) 22:04, 25 August 2019 (UTC)
@James-the-Charizard: Actually, upon closer review it doesn't look like a copyright violation. The image was pulled from a YouTube video by the Falcons and they licensed it as eligible to be used in other works. In my opinion, however, the Ohio State image of Thomas is better than the screenshot from a video as a Saints player. Eagles24/7(C)22:20, 25 August 2019 (UTC)
This is an archive of past discussions with User:Eagles247. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page.
