This is an archive of past discussions with User:Parsecboy. 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.
Hi there, I'm pleased to inform you that I've begun reviewing the article HMS Formidable (1898) you nominated for GA-status according to the criteria. This process may take up to 7 days. Feel free to contact me with any questions or comments you might have during this period. Message delivered by Legobot, on behalf of Sturmvogel 66 -- Sturmvogel 66 (talk) 16:02, 5 November 2018 (UTC)
Hi there, I'm pleased to inform you that I've begun reviewing the article HMS Implacable (1899) you nominated for GA-status according to the criteria. This process may take up to 7 days. Feel free to contact me with any questions or comments you might have during this period. Message delivered by Legobot, on behalf of Peacemaker67 -- Peacemaker67 (talk) 02:20, 14 November 2018 (UTC)
Hi there, I'm pleased to inform you that I've begun reviewing the article HMS Queen (1902) you nominated for GA-status according to the criteria. This process may take up to 7 days. Feel free to contact me with any questions or comments you might have during this period. Message delivered by Legobot, on behalf of L293D -- L293D (talk) 13:21, 14 November 2018 (UTC)
Hi there, I'm pleased to inform you that I've begun reviewing the article HMS London (1899) you nominated for GA-status according to the criteria. This process may take up to 7 days. Feel free to contact me with any questions or comments you might have during this period. Message delivered by Legobot, on behalf of Peacemaker67 -- Peacemaker67 (talk) 03:21, 17 November 2018 (UTC)
Hello, Parsecboy. Voting in the 2018 Arbitration Committee elections is now open until 23.59 on Sunday, 3 December. All users who registered an account before Sunday, 28 October 2018, made at least 150 mainspace edits before Thursday, 1 November 2018 and are not currently blocked are eligible 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.
Hello, Parsecboy. Voting in the 2018 Arbitration Committee elections is now open until 23.59 on Sunday, 3 December. All users who registered an account before Sunday, 28 October 2018, made at least 150 mainspace edits before Thursday, 1 November 2018 and are not currently blocked are eligible 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.
Hi there, I'm pleased to inform you that I've begun reviewing the article London-class battleship you nominated for GA-status according to the criteria. This process may take up to 7 days. Feel free to contact me with any questions or comments you might have during this period. Message delivered by Legobot, on behalf of L293D -- L293D (talk) 03:01, 29 November 2018 (UTC)
Hi there, I'm pleased to inform you that I've begun reviewing the article Formidable-class battleship you nominated for GA-status according to the criteria. This process may take up to 7 days. Feel free to contact me with any questions or comments you might have during this period. Message delivered by Legobot, on behalf of Djmaschek -- Djmaschek (talk) 02:20, 1 December 2018 (UTC)
Hello, Parsecboy. Please check your email; you've got mail! It may take a few minutes from the time the email is sent for it to show up in your inbox. You can remove this notice at any time by removing the {{You've got mail}} or {{ygm}} template.
I'd like to invite editors who participated in the deletion discussion to give their input at article talk. There was considerable interest in cleaning up this article in one way or another, but there have been few responses to my proposal to trim the passenger lists. Alternative proposals are certainly welcome as well; I'm hoping that we can build some sort of consensus for the scope and direction of the article moving forward. Thanks –dlthewave☎21:52, 7 December 2018 (UTC)
Hi there, I'm pleased to inform you that I've begun reviewing the article HMS Albemarle (1901) you nominated for GA-status according to the criteria. This process may take up to 7 days. Feel free to contact me with any questions or comments you might have during this period. Message delivered by Legobot, on behalf of Sturmvogel 66 -- Sturmvogel 66 (talk) 23:40, 11 December 2018 (UTC)
Voting now open for "Military historian of the year" and "Military history newcomer of the year" awards
Hi there, I'm pleased to inform you that I've begun reviewing the article HMS Cornwallis (1901) you nominated for GA-status according to the criteria. This process may take up to 7 days. Feel free to contact me with any questions or comments you might have during this period. Message delivered by Legobot, on behalf of Kges1901 -- Kges1901 (talk) 23:20, 22 December 2018 (UTC)
Hi there, I'm pleased to inform you that I've begun reviewing the article HMS Montagu (1901) you nominated for GA-status according to the criteria. This process may take up to 7 days. Feel free to contact me with any questions or comments you might have during this period. Message delivered by Legobot, on behalf of Kges1901 -- Kges1901 (talk) 02:01, 23 December 2018 (UTC)
Hi there, I'm pleased to inform you that I've begun reviewing the article HMS Duncan (1901) you nominated for GA-status according to the criteria. This process may take up to 7 days. Feel free to contact me with any questions or comments you might have during this period. Message delivered by Legobot, on behalf of Kges1901 -- Kges1901 (talk) 02:41, 23 December 2018 (UTC)
Hi there, I'm pleased to inform you that I've begun reviewing the article HMS Russell (1901) you nominated for GA-status according to the criteria. This process may take up to 7 days. Feel free to contact me with any questions or comments you might have during this period. Message delivered by Legobot, on behalf of Sturmvogel 66 -- Sturmvogel 66 (talk) 10:01, 26 December 2018 (UTC)
Hi there, I'm pleased to inform you that I've begun reviewing the article HMS Exmouth (1901) you nominated for GA-status according to the criteria. This process may take up to 7 days. Feel free to contact me with any questions or comments you might have during this period. Message delivered by Legobot, on behalf of Sturmvogel 66 -- Sturmvogel 66 (talk) 10:01, 26 December 2018 (UTC)
Please check out "Happy" once more, for a smile, and sharing (a Nobel Peace Prize), and resolutions. I wanted that for 1 January, but then wasn't sad about having our music pictured instead. Not too late for resolutions, New Year or not. DYK that he probably kept me on Wikipedia, back in 2012? By the line (which brought him to my attention, and earned the first precious in br'erly style) that I added to my editnotice, in fond memory? --Gerda Arendt (talk) 14:40, 12 January 2019 (UTC)
Today, thank you for SMS Kronprinz, the ship that "fought at the Battle of Jutland in the front of the German line, but emerged completely unscathed, while her three sisterships directly ahead were the most damaged German battleships in the engagement. Kronprinz engaged and forced the retreat of the Russian battleship Tsarevitch during the Battle of Moon Sound in 1917. She was ultimately interned in Scapa Flow at the end of the war and scuttled by her crew." --Gerda Arendt (talk) 07:41, 21 February 2019 (UTC)
Today, thank you for SMS Schlesien, with "a relatively eventful career, despite having been made obsolescent by HMS Dreadnought before even entering service. Schlesien was present at the Battle of Jutland during WWI, and was one of the few ships to survive into the postwar navy. Still in active service during WWII, she took part in the invasions Poland in 1939 and Denmark and Norway in 1940, and ended up shelling advancing Soviet forces in 1945, before being scuttled in Swinemunde."! - I took some travel pics, - click on "March" --Gerda Arendt (talk) 08:22, 27 March 2019 (UTC)
R4 (new): Redirects in the file namespace (and no file links) that have the same name as a file or redirect at Commons are now covered under the new R4 criterion (discussion). This is {{db-redircom}}; the text is unchanged.
G13 (expanded): Userspace drafts containing only the default Article Wizard text are now covered under G13 along with other drafts (discussion). Such blank drafts are now eligible after six months rather than one year, and taggers continue to use {{db-blankdraft}}.
Members of the Bot Approvals Group (BAG) are now subject to an activity requirement. After two years without any bot-related activity (e.g. operating a bot, posting on a bot-related talk page), BAG members will be retired from BAG following a one-week notice.
Technical news
Starting on December 13, the Wikimedia Foundation security team implemented new password policy and requirements. Privileged accounts (administrators, bureaucrats, checkusers, oversighters, interface administrators, bots, edit filter managers/helpers, template editors, et al.) must have a password at least 10 characters in length. All accounts must have a password:
User accounts not meeting these requirements will be prompted to update their password accordingly. More information is available on MediaWiki.org.
Blocked administrators may now block the administrator that blocked them. This was done to mitigate the possibility that a compromised administrator account would block all other active administrators, complementing the removal of the ability to unblock oneself outside of self-imposed blocks. A request for comment is currently in progress to determine whether the blocking policy should be updated regarding this change.
{{Copyvio-revdel}} now has a link to open the history with the RevDel checkboxes already filled in.
Accounts continue to be compromised on a regular basis. Evidence shows this is entirely due to the accounts having the same password that was used on another website that suffered a data breach. If you have ever used your current password on any other website, you should change it immediately.
Around 22% of admins have enabled two-factor authentication, up from 20% in June 2018. If you haven't already enabled it, please consider doing so. Regardless of whether you use 2FA, please practice appropriate account security by ensuring your password is secure and unique to Wikimedia.
In recognition of the decision by the Wikipedia Signpost to feature SMS Zähringen as the lead image for its "Feature Content" section in the 05 February 2018 edition you are hereby presented with the Special Barnstar. Admittedly, this was a "luck of the draw" matter, but its still worthy on noting :) TomStar81 (Talk) 18:59, 4 January 2019 (UTC) TomStar81 (Talk) 18:59, 4 January 2019 (UTC)
On behalf of the Military History Project, I am proud to present the The Content Review Medal of Merit (Military history) for October to December 2018 reviews. MilHistBot (talk) 01:06, 8 January 2019 (UTC)
Keep track of upcoming reviews. Just copy and paste {{WPMILHIST Review alerts}} to your user space
Hi there, I'm pleased to inform you that I've begun reviewing the article HMS King Edward VII you nominated for GA-status according to the criteria. This process may take up to 7 days. Feel free to contact me with any questions or comments you might have during this period. Message delivered by Legobot, on behalf of Zawed -- Zawed (talk) 07:20, 9 January 2019 (UTC)
Hi there, I'm pleased to inform you that I've begun reviewing the article HMS Commonwealth you nominated for GA-status according to the criteria. This process may take up to 7 days. Feel free to contact me with any questions or comments you might have during this period. Message delivered by Legobot, on behalf of Ed! -- Ed! (talk) 17:20, 12 January 2019 (UTC)
Hi there, I'm pleased to inform you that I've begun reviewing the article HMS Dominion you nominated for GA-status according to the criteria. This process may take up to 7 days. Feel free to contact me with any questions or comments you might have during this period. Message delivered by Legobot, on behalf of Ed! -- Ed! (talk) 18:01, 13 January 2019 (UTC)
The article HMS Dominion you nominated as a good article has been placed on hold . The article is close to meeting the good article criteria, but there are some minor changes or clarifications needing to be addressed. If these are fixed within 7 days, the article will pass; otherwise it may fail. See Talk:HMS Dominion for things which need to be addressed. Message delivered by Legobot, on behalf of Ed! -- Ed! (talk) 18:20, 13 January 2019 (UTC)
Hi there, I'm pleased to inform you that I've begun reviewing the article HMS Britannia (1904) you nominated for GA-status according to the criteria. This process may take up to 7 days. Feel free to contact me with any questions or comments you might have during this period. Message delivered by Legobot, on behalf of Sturmvogel 66 -- Sturmvogel 66 (talk) 23:01, 13 January 2019 (UTC)
Hi there, I'm pleased to inform you that I've begun reviewing the article HMS Africa (1905) you nominated for GA-status according to the criteria. This process may take up to 7 days. Feel free to contact me with any questions or comments you might have during this period. Message delivered by Legobot, on behalf of Sturmvogel 66 -- Sturmvogel 66 (talk) 23:01, 13 January 2019 (UTC)
Hi there, I'm pleased to inform you that I've begun reviewing the article HMS Zealandia you nominated for GA-status according to the criteria. This process may take up to 7 days. Feel free to contact me with any questions or comments you might have during this period. Message delivered by Legobot, on behalf of Sturmvogel 66 -- Sturmvogel 66 (talk) 23:01, 13 January 2019 (UTC)
Hi there, I'm pleased to inform you that I've begun reviewing the article HMS Hibernia (1905) you nominated for GA-status according to the criteria. This process may take up to 7 days. Feel free to contact me with any questions or comments you might have during this period. Message delivered by Legobot, on behalf of Zawed -- Zawed (talk) 08:20, 15 January 2019 (UTC)
Hi there, I'm pleased to inform you that I've begun reviewing the article King Edward VII-class battleship you nominated for GA-status according to the criteria. This process may take up to 7 days. Feel free to contact me with any questions or comments you might have during this period. Message delivered by Legobot, on behalf of Ed! -- Ed! (talk) 00:20, 19 January 2019 (UTC)
Hello PB firstly congrats. I'm happy to see this article reaching FA-class. Secondly, sadly that not all of my comments were replied and addressed in this nomination. The weird part is that Sarastro1 clossed the nomination before I could give you my support and before you even saw which comments I meant. Can you please have a look into the clossed nomination and answer my comments? Cheers. CPA-5 (talk) 21:04, 21 January 2019 (UTC)
Thanks - that is odd that Sarastro closed it before I could respond to your comments, perhaps they saw that I had responded to you but didn't notice that you added another comment. I took out the short tons from the one conversion template, but I think the "autumn" thing is fine as is. Readers should be able to context clue their way to the correct time frame from the fact that the article discusses events in June and July before the maneuvers and November afterward. Hildebrand et. al. usually gives specific dates for the maneuvers, but they didn't in this instance - they were typically in late August and into September, FWIW. Parsecboy (talk) 13:03, 22 January 2019 (UTC)
Yes indeed it's a little bit odd. That's fair enough, anyway if I could I would surely give you my support. Cheers. ;) CPA-5 (talk) 21:51, 22 January 2019 (UTC)
Also good luck with the other thousand ships. I'd say you and Sturm have work for an other decade. Cheers. :p CPA-5 (talk) 21:57, 22 January 2019 (UTC)
Thanks - with any luck, the battleships will be done by 2020, at least as far as everything being GA or above - there's another 60 or so articles left to write, so we'll see how we do. Parsecboy (talk) 12:37, 24 January 2019 (UTC)
Ha 60 articles for GA in 2020 and in 2030 everything has to be A-class or above. :) Nah you and Sturm can easily archive GA in those 60 or so articles in 2020. In the last months, I was watching closely to your, Sturm's and the battleships progresses. It impressed me (alot), that you both could make it that far and fastly in the last years. Especially for you, you're already working almost a whole decade on those articles. That's why I started reviewing your and Sturm's articles, to give you both a little pat on the back if I could say that of course. :p Any support is welcome even from "someone who's English so great like me" but hey it's an intresting topic. Also I re-reviewed your Ersatz Yorck-class battlecruiser A-Class nomination Cheers. CPA-5 (talk) 20:45, 30 January 2019 (UTC)
The trouble is, we've left most of the difficult work for last ;) It's easy to chop through a few dozen British pre-dreadnoughts that were already in fairly decent shape, it's another thing to tackle monsters like French battleship Richelieu, USS Tennessee (BB-43), or Queen Elizabeth-class battleship, which all basically need to be rewritten from scratch. The other problem is, Sturm and I easily get distracted ;) He's been off writing scores of articles on German torpedo-boats and Soviet destroyers, and these are calling my name.
I do appreciate your reviews - one of the biggest hurdles to moving things beyond GA-level is getting enough people to review articles so they can be promoted - the Schlesien FAC lasted just about 2 months. I'll get to your additions to the Ersatz Yorck review in the morning. Thanks again. Parsecboy (talk) 21:42, 30 January 2019 (UTC)
Ha! I definitely can believe that! It shouldn't suprise me that you and Sturm can get distracted that easily. But that's not a problem, we and Wikipedia have time. Also you still have co-operators like L293D and Kges1901, which make also some (little more) progresses in the ships. They can still help you and Sturm. But what I can't and won't belive is that you wouldn't reach your GA goal in the ships in 2020. ;) Cheers. CPA-5 (talk) 18:35, 1 February 2019 (UTC)
I guess we'll just have to see how far we get ;) One problem right now is that White Shadows, who had been rewriting the Austro-Hungarian ship articles last year (after a rather long wikibreak) hasn't edited since December - hopefully he'll be back soon. Parsecboy (talk) 21:39, 1 February 2019 (UTC)
Oh dear God I totaly forgot him, it's already two months ago. I hope nothing bad happend to him. Sadly that's life here on Wikipedia some people work hard like you and Sturm to establish a real, meaningful and importand goal and then you have people like me who don't work that hard but try to do their best to make Wikipedia a meaningful place. But everywhere and anytime can someone drop Wikipedia because something happend in the real world bad or good they're gone for a really long time or even gone forever. Yes indeed I hope he will be safe and back soon too. Cheers. CPA-5 (talk) 22:20, 1 February 2019 (UTC)
Yeah, he had been gone for several years before - let's hope this is a shorter departure. There have been editors who just dropped off the face of the earth though - one of the original OMT editors (user:MBK004) just stopped editing one day back in 2010. I never heard what happened to him. That's the nature of a place like this, I suppose. Parsecboy (talk) 23:07, 1 February 2019 (UTC)
Hi there, I'm pleased to inform you that I've begun reviewing the article HMS Resolution (09) you nominated for GA-status according to the criteria. This process may take up to 7 days. Feel free to contact me with any questions or comments you might have during this period. Message delivered by Legobot, on behalf of Peacemaker67 -- Peacemaker67 (talk) 02:40, 25 January 2019 (UTC)
What was wrong with the cite style I changed it to? I am trying to change all the cites on that page to that style as it is cleaner and what most other pages use. WelpThatWorked (talk) 16:32, 30 January 2019 (UTC)
You should not change the citation style used in an article without securing consensus to do so on the article talk page. You also degraded the accuracy of the citation - you removed the specific page number when you converted the short cite to the long cite. You can read WP:CITEVAR for further info on this. Parsecboy (talk) 16:46, 30 January 2019 (UTC)
Parsecboy, I moved a copy to my sandbox and worked on it there. I tried to make sure that all the citations have the correct page numbers, so please tell me if I missed anything. If there are any other issues, please tell me. If not, as you are the main contribute to the article, do you think that would be consensus enough? I really enjoyed reading the article, and I wish it luck on gaining featured status. Thanks! WelpThatWorked (talk) 18:25, 30 January 2019 (UTC)
Thanks, but no, I don't like long citations - they're too cluttered and generally require too many compromises to make them work accurately. Parsecboy (talk) 18:28, 30 January 2019 (UTC)
South Dakota (1939) edit revert
The hypens come and go on ship/class pages. For example, it's hyphenated in the 1st sentence of the lead at the Iowa-class page (which form I followed in making my edit). If you know the grammar distinctions that well, perhaps you could spare some time from page monitoring to make some corrections on them. A hidden explanatory note at the top would go a long way toward casual editors and non-grammarians' understanding of the rules, as there's a hyphen in the page name, none in the intro of the lead, none in the Infobox for preceding and succeeding classes, then they dance around throughout any given ship/class page's text.Wikiuser100 (talk) 17:38, 30 January 2019 (UTC)
Yes, the hyphen is present in the first sentence at Iowa-class battleship because it is identical to the title (which is to say, "Iowa-class" is a compound adjective modifying "battleship", the noun. When "Iowa" is the adjective modifying "class", the noun, there is no hyphen. I fix hyphen issues as I find them, but I don't generally have the time to go scouring for them. Parsecboy (talk) 17:56, 30 January 2019 (UTC)
I'm kinda getting it now. Grammar biz. Saw where you fixed an instance of errant hyphenry in the body of the article, but left the intro line of the lead as is. Clearly the use of "battleship" in bold is redundant of referring to the class as "fast battleships" immediately after (as in the South Dakota article). So I deleted that redundant word, which also required eliminating the hyphen in the initial use of "Iowa class". That should take care of it for that article, at the least. Thanks for the education. Yours, Wikiuser100 (talk) 18:51, 30 January 2019 (UTC)
No problem - the lead looks good to me. Grammar stuff is a complicated thing, and I'm by no means an expert on it all, this is just one little thing I've mastered over the years ;) Parsecboy (talk) 18:57, 30 January 2019 (UTC)
Administrators who are blocked have the technical ability to block the administrator who blocked their own account. A recent request for comment has amended the blocking policy to clarify that this ability should only be used in exceptional circumstances, such as account compromises, where there is a clear and immediate need.
A request for comment closed with a consensus in favor of deprecating The Sun as a permissible reference, and creating an edit filter to warn users who attempt to cite it.
Technical news
A discussion regarding an overhaul of the format and appearance of Wikipedia:Requests for page protection is in progress (permalink). The proposed changes will make it easier to create requests for those who are not using Twinkle. The workflow for administrators at this venue will largely be unchanged. Additionally, there are plans to archive requests similar to how it is done at WP:PERM, where historical records are kept so that prior requests can more easily be searched for.
A new IRC bot is available that allows you to subscribe to notifications when specific filters are tripped. This requires that your IRC handle be identified.
Hello, I have spent most my time on Wikipedia fighting vandalism but am starting to get into editing articles. As of right now I have taken on the task of getting Anti-torpedo bulge up to GA status but am not really sure where to start. Do you have any suggestions as to what I should do first? A 10 fireplaneImform me18:31, 4 February 2019 (UTC)
The first thing I'd suggest is to look up sources on the first ships to carry the bulges - the Edgars are mentioned as the testbeds for the bulges. D. K. Brown's book is listed in the references for the Anti-torpedo bulge article, and that would likely be a good place to start, as would Friedman's British Cruisers of the Victorian Era (that I haven't read, so I can't say whether it includes details on later modifications, but based on Friedman's other books, I'd wager it does.
The other thing you'd want to do is to sketch out an outline of how you see the article developing - you'd probably want a background section that discusses the threat of torpedoes and the various methods used to defend against them (mostly you're going to be looking at anti-torpedo nets), a section on the development of the idea (covering Tennyson-D'Eyncourt's experimentation with the Edgars, tests with HMS Ramillies (07) that led to the bulges being added to the other four Revenge-class battleships, etc.), a section on the effectiveness of the bulges (you could discuss their impact on ship handling in addition to examples of vessels being torpedoed in the world wars), and maybe a section on later anti-torpedo defense systems (torpedo bulkheads and the Pugliese system come to mind). Parsecboy (talk) 19:24, 4 February 2019 (UTC)
I take it that all the measurements in the infobox came from the book source. This info should also appear in a "Description" section and be referenced. This addition should raise the article to Start class. Mjroots (talk) 21:50, 7 February 2019 (UTC)
Hi, this is to let you know that the above article will appear as Today's Featured Article on March 27, 2019. The blurb to be used can be found here. You are free to edit the blurb, and may want to watchlist that page, as well as WP:ERRORS in case there are queries about it on the day it runs, as well as the previous day. If you have questions or concerns, feel free to post on my talk. Thanks for building quality content!--Wehwalt (talk) 18:58, 17 February 2019 (UTC)
Hi there, I'm pleased to inform you that I've begun reviewing the article USS California (BB-44) you nominated for GA-status according to the criteria. This process may take up to 7 days. Feel free to contact me with any questions or comments you might have during this period. Message delivered by Legobot, on behalf of Sturmvogel 66 -- Sturmvogel 66 (talk) 17:41, 2 March 2019 (UTC)
Following discussions at the Bureaucrats' noticeboard and Wikipedia talk:Administrators, an earlier change to the restoration of adminship policy was reverted. If requested, bureaucrats will not restore administrator permissions removed due to inactivity if there have been five years without a logged administrator action; this "five year rule" does not apply to permissions removed voluntarily.
Technical news
A new tool is available to help determine if a given IP is an open proxy/VPN/webhost/compromised host.
Arbitration
The Arbitration Committee announced two new OTRS queues. Both are meant solely for cases involving private information; other cases will continue to be handled at the appropriate venues (e.g., WP:COIN or WP:SPI).
paid-en-wpwikipedia.org has been set up to receive private evidence related to abusive paid editing.
checkuser-en-wpwikipedia.org has been set up to receive private requests for CheckUser. For instance, requests for IP block exemption for anonymous proxy editing should now be sent to this address instead of the functionaries-en list.
Hi there, I'm pleased to inform you that I've begun reviewing the article HMS Ramillies (07) you nominated for GA-status according to the criteria. This process may take up to 7 days. Feel free to contact me with any questions or comments you might have during this period. Message delivered by Legobot, on behalf of Peacemaker67 -- Peacemaker67 (talk) 05:40, 16 March 2019 (UTC)
Hey PB may I ask you a question?
I'm just curious but I saw that you and Sturm uses Brtish English if the ships are British or French and American English in German and American ships but why are the Japanese ships written in British instead of American English? Because by Tetsuya Fukuda Dokkyo University most students want to learn American English - see link. [1]
And East Asians in general uses American English – see link.[2] Cheers. CPA-5 (talk) 17:54, 17 March 2019 (UTC)
@Sturmvogel 66: Oh hey Sturm didn't expect you here. Yes I understand your point on one side. So you mean if it is written by a Canadian hen it means you are writing -ize instead of -ise on that article. But one thing is really odd to me. You want to use American English in the Normandie-class battleship article but the article originally uses British English because it was made by a Briton. So why changing the originally style of English? Cheers. CPA-5 (talk) 21:13, 17 March 2019 (UTC)
Talk page stalker! We're not supposed to change the original style, although we've done it inadvertently more than once. Personally I don't take the time to go back and see what it was originally, I go with whatever it's got when I start work on it. If it's mixed without strong national ties, I'll default to my native AmEng.--Sturmvogel 66 (talk) 21:20, 17 March 2019 (UTC)
@Sturmvogel 66: Well, that's why I thought you and PB uses strong national ties. Countries like Japan or China as examples uses American English even it's not their offcial language but anyway as long it will reached (and stay) FA-class in whatever kinda style of English it is. PS how nice to call me a talk page stalker. ;) Cheers. CPA-5 (talk) 21:40, 17 March 2019 (UTC)
What Sturm said - basically it's up to whoever created the page unless they left it as a stub, in which case whoever wants to write the article can choose. Personally, I think the rule is a bit outdated and too strict - I feel that if I'm going to take a start-class article and develop it to FA level, I ought to be able to pick what version of English I want to write it in, but that opinion so far hasn't caught on ;) Parsecboy (talk) 11:35, 18 March 2019 (UTC)
I translated German FK cruiser designs to pl.wiki and somebody asked me question: in article there is The designs carried up to 1,000 t (980 long tons; 1,100 short tons) and 1,150 t (1,130 long tons; 1,270 short tons) of fuel oil, respectively, which permitted a cruising radius of 2,800 nautical miles (5,200 km; 3,200 mi) at a speed of 17 kn (31 km/h; 20 mph. That means that in total this cruisers can go 5600 nautical miles (so "cruising radius"x2) or that was range of this ships? PMG (talk) 13:04, 25 March 2019 (UTC)
I wanted to let you know that we've renominated Albatros and perhaps you'll have a chance to see if your previous comments have been adequately addressed before it's archived.--Sturmvogel 66 (talk) 20:35, 26 March 2019 (UTC)
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. Please see meta:Community health initiative/User reporting system consultation 2019 to provide your input on this idea.
Two more administrator accounts were compromised. Evidence has shown that these attacks, like previous incidents, were due to reusing a password that was used on another website that suffered a data breach. If you have ever used your current password on any other website, you should change it immediately. All admins are strongly encouraged to enable two-factor authentication, please consider doing so. Please always practice appropriate account security by ensuring your password is secure and unique to Wikimedia.
As a reminder, according to WP:NOQUORUM, administrators looking to close or relist an AfD should evaluate a nomination that has received few or no comments as if it were a proposed deletion (PROD) prior to determining whether it should be relisted.
Hi there, I'm pleased to inform you that I've begun reviewing the article USS Pennsylvania (BB-38) you nominated for GA-status according to the criteria. This process may take up to 7 days. Feel free to contact me with any questions or comments you might have during this period. Message delivered by Legobot, on behalf of Peacemaker67 -- Peacemaker67 (talk) 09:00, 14 April 2019 (UTC)
No, plain Krupp armor was long since outdated by the 1930s - Groener doesn't say, but it likely would've been a combination of Wotan Hart and Wotan Weich, which were improvements on Krupp cemented steel. Parsecboy (talk) 11:36, 16 April 2019 (UTC)
Haha, and as a veteran, to boot, I've had my fill of drills ;) I'll take a look at the article in the next couple of days and make sure there isn't anything significant that needs to be updated. Parsecboy (talk) 20:49, 17 April 2019 (UTC)
Hi there, I'm pleased to inform you that I've begun reviewing the article USS Tennessee (BB-43) you nominated for GA-status according to the criteria. This process may take up to 7 days. Feel free to contact me with any questions or comments you might have during this period. Message delivered by Legobot, on behalf of Peacemaker67 -- Peacemaker67 (talk) 12:00, 18 April 2019 (UTC)
OK, I'll get my verification from the Naval History and Heritage Command. I've contacted Public Affairs about the discrepancy. I've been in contact with a member of the http://www.ussutah1941.org/ memorial organization which provided me with the picture of the Honor Roll from the Memorial at Pearl Harbor off of Ford Island. So, I'll get confirmation from the Navy as to the official Death & Survivor counts. I expect they'll be surprised if the Honor Roll is in fact, in error, and would need to be corrected.
I've found the people who run DANFS to be receptive to correcting errors, so let me know if and when they update the site. I had the contact info for the Rear Admiral who was in charge, but that was several years ago and I'm sure he's long gone. Speaking of that, I need to get around to hassling them about this mess. Parsecboy (talk) 15:41, 18 April 2019 (UTC)
Hello, I've finally gotten a reply from the Naval History and Heritage Command concerning this question. It seems an error was introduced somewhere along the way with the death toll count for the USS Utah. They've verified my number which was supplied by the USS Utah BB-31 Memorial Organization. The picture of the plaque is indeed a factual list of the dead. They are in the process of correcting the on-line information and I've asked them to notify me when that correction has been made.
This is an extract from the e-mail I received:
MC2 Capizzi and Dr. Bereiter,
I’d forgotten I had a book in my office about the Utah (published 2009), which contains a copy of the original DANFS history (which I wrote) available when the author wrote the book -- not the original DANFS hard-copy published in 1981 that gave incorrect numbers) that gives the corrected numbers as:
6 officers and 52 enlisted, for a total of 58 dead.
Four enlisted men’s remains (no officers) were recovered and buried ashore.
I’m at a loss to say why the numbers were changed somewhere along the line (2017?).
Rest assured the correct numbers will be up ASAP when I get into the CQ5.
My apologies for any inconvenience caused, that’s my fault – I should have gotten to this RFI sooner.
Further update:
Thank you for contacting Naval History and Heritage Command! We are
committed to assisting you in your request. Please see information below to
best accommodate your request.
Once the entry has been updated on our website, you will be forwarded the link so you can provide WIKI with the correct reference.
Hi there, I'm pleased to inform you that I've begun reviewing the article USS Indiana (BB-58) you nominated for GA-status according to the criteria. This process may take up to 7 days. Feel free to contact me with any questions or comments you might have during this period. Message delivered by Legobot, on behalf of Sturmvogel 66 -- Sturmvogel 66 (talk) 15:40, 19 April 2019 (UTC)
An editor has asked for a deletion review of USS Augustus Holly. Because you closed the deletion discussion for this page, speedily deleted it, or otherwise were interested in the page, you might want to participate in the deletion review. Izno (talk) 13:07, 30 April 2019 (UTC)
Hi. With regard to SMS Pillau, omitting articles before ship names may be style in naval or military writing, but I don't think it is in general expository writing, including historical writing. Normally, one speaks of "the Titanic," "the Bismarck," etc. I would expect encyclopedic writing to follow the same practice. Comment? –
There have been several lengthy discussions on this at WP:SHIPS - it used to be covered in the project guidelines but was removed at some point. In any event, in my view, ship names are much the same as a person's name; one wouldn't say "the Fred went to the store". Parsecboy (talk) 16:37, 2 May 2019 (UTC)
No, but surprising as this may seem to the nautically minded, ships are not people, they are things. That they usually have names is merely tradition – a type of anthropomorphism. – Sca (talk) 13:37, 3 May 2019 (UTC)
By the way, the MoS for images discourages using forced image sizing. The biggest concern is that not all displays are the same size (particularly with a lot of readers on smart phones these days) and so forced size can cause problems there. Also, it overrides the preferences of logged in users, since they can set a preference to display photos at larger or smaller sizes. Parsecboy (talk) 16:44, 2 May 2019 (UTC)
There is a case to be made that most readers aren't logged in and thus don't have preferences to override. And I don't know how common it is to have display problems on mobile devices - both versions of the photo looked fine on my iphone. Parsecboy (talk) 11:45, 3 May 2019 (UTC)
As a rule we should not force size of images. By forcing size of image you are telling "I am sure that in 15 years this image should have this size only and no changes in technology, browsers, MediaWiki, common.css/js, user settings should change it". It's really strong statement. Wikipedia existed 15 years ago, and probably will exist in 15 years. People will may be using VR and other new technologies, and this size will be still forced. PMG (talk) 14:46, 6 May 2019 (UTC)
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.