User talk:Steelpillow
From Wikipedia, the free encyclopedia
Talk archives (Please do not edit archive pages! All posts should go on my current talk page.)
·
2006-10 ·
2011-12 ·
2013-14 ·
2015 ·
2016-17 ·
2018-19 ·
2020-22 ·
If you want to contact me, you can still PM me. You can also drop me a line on my talk page, though I may not pick it up for weeks on end.
— Cheers, Steelpillow (Talk) 11:42, 18 November 2025 (UTC)
Retrocasuality
My parameter deletions from an arXiv citation template were undone because the URL was perfectly good. Achmad Rachmani (talk) 12:59, 19 June 2023 (UTC)
- It's fine now, so I probably owe you an apology. When I checked it out before I got an error message (and I checked again to be sure); it seems that must have been a system hiccup or glitch, and not a mistake by you, these things do happen. Anyway, thank you for coming here to ask. — Cheers, Steelpillow (Talk) 13:08, 19 June 2023 (UTC)
help copyedit
Hi Steelpillow,
I added a section to the mediawiki2latex documentation
Could please check if the language is in order an correct it in case it isn't
Thanks in advance
Dirk Hünniger (talk) 11:56, 22 July 2023 (UTC)
Thanks a lot Dirk Hünniger (talk) 12:50, 22 July 2023 (UTC)
- Hi Dirk, I have just had a go at some more of the page, hope it still looks OK to you? — Cheers, Steelpillow (Talk) 12:57, 22 July 2023 (UTC)
- Yeah everthing looks fine. Thanks again Dirk Hünniger (talk) 13:33, 22 July 2023 (UTC)
Advising RfC
Thanks for taking on a difficult discussion. Sorry to do this to you, but I'd like to challenge it.
The main takeaway from your closing statement is There is consensus that the policy on WP:COI should be widened to include off-wiki paid advising for promotional purposes, but litle else.
. I think there are some problems here.
1) Scope of the RfC. There is no dispute that exchanging money creates a COI in the basic sense of a conflict of interest. The COI policy however, is only concerned with edits to Wikipedia. Your finding would radically change what what that policy means -- a much, much bigger finding than the RfC asks, and something that most people did not even directly speak to. This proposal was to modify WP:Paid-contribution disclosure, not WP:COI. COI is all about what happens on-wiki, and what someone should do to mitigate it. The finding of this RfC, however, is no consensus to require a COI disclosure, so what would even go into the policy based on this discussion?
2) How do you (or more importantly, how did participants) distinguish "promotional purposes"? Every company paying someone for advice is looking to promote themselves, so isn't it all promotional? Further, how would anyone distinguish between them? How can you tell when someone provided good advice but the company didn't follow it from someone providing bad advice? It is uncontroversial to say "Wikipedians shouldn't tell companies how to subvert our policies and guidelines". Is that all "promotional" means in this case? The controversial things are how to tell someone is doing that, how to distinguish company promotion that disregards good advice from company promotion based on bad advice, whether to assume that everyone advising is acting in bad faith, whether someone already acting in bad faith would simply ignore the disclosure requirement, whether conversations and relationships we have off-wiki must always be disclosed even if they don't result in on-wiki edits, etc.
In short, your closure seems to find no consensus for the RfC while at the same time finding consensus for something much, much bigger -- a change to a policy that wasn't even part of the proposal, and which most people didn't address directly. I have trouble seeing consensus for any change to the COI policy coming out of this discussion. If someone is found to be providing advice on subverting our policies, they should be blocked per our basic policies like WP:NOT. Transforming the COI policy from a policy regarding on-wiki activities into something dealing with off-wiki dealings is not a reasonable outcome here. It's possible there's some modification to e.g. WP:PAID to say "don't tell them how to break the rules", but even that would be pointless: consensus is against required disclosure on a "just in case" basis, someone violating those rules would likewise just ignore the disclosure anyway, and there's no way for the community to know what conversations are being had off-wiki. — Rhododendrites talk \\ 16:50, 17 November 2023 (UTC)
- Hi there, no problem - if I messed up it needs to be outed. The RfC is just a part of a much wider discussion; most of my summary concerns that wider discussion. This is why most of my findings are outside the scope of the RFC proposal. Hence my closure, as you put it, "seems to find no consensus for the RfC while at the same time finding consensus for something much, much bigger". I suggested that the details, of how that wider change might crystallise, might be thrashed out in a subsequent RfC, including any changes to WP:COI or what the "promotional" meme expressed by participants might mean. If you wish to argue that there really is no consensus for tightening up the wording on the need to declare a COI, I am sure you know better than I how to pursue that. But you might like to bear in mind that another uninvolved editor has endorsed my closure, and one or two others involved have sent their thanks. — Cheers, Steelpillow (Talk) 17:50, 17 November 2023 (UTC)
- We use RfCs to ensure big decisions get a lot of outside input and to structure discussion. If your closure indeed was based "most" on discussions that were outside the RfC (preceding said outside input and preceding said structuring), it was not an appropriate way to close the RfC. This wasn't a case of finding some small nuance in external discussions to contextualize the RfC, but of rejecting the proposal of the RfC and imposing an outcome that was never proposed, that most people didn't address, that concerns a different policy, and which radically changes that policy. That's a hugely problematic thing for an RfC closing statement to do and a poor way to construct policy. — Rhododendrites talk \\ 18:02, 17 November 2023 (UTC)
- The brief closure discussion at the end is structured as a subtopic of the main discussion and not of the RfC. I therefore closed the main discussion. I "closed the RfC" in only one of my findings, viz. that there was no consensus (i.e. over the proposed wording); I do not regard that as an outright "rejection", but what do I know? If you feel this was an improper way to close the RfC that is as may be, but it does not imply it was an improper closure of the wider discussion, which was the main remit. — Cheers, Steelpillow (Talk) 18:28, 17 November 2023 (UTC)
- I agree with Rhododendrites, I'm afraid; I think you put more in the close than is present in the discussion. Mike Christie (talk - contribs - library) 18:42, 17 November 2023 (UTC)
- That is possible, or at least I can see how it might appear that way. I could certainly water down my "recommendation" to a "suggestion" and move it outside the findings, more as an afterthought. The only positive finding is that "There is a consensus [for paid advisers] to declare a COI." I stand by that. — Cheers, Steelpillow (Talk) 18:56, 17 November 2023 (UTC)
- I'm also in agreement that the issue of COI wasn't presented to the community in the RfC and should not have been mentioned as having received consensus in the close. If that had been presented, I would have addressed it. But I did not know it needed to be addressed. Wehwalt (talk) 20:01, 17 November 2023 (UTC)
- That is possible, or at least I can see how it might appear that way. I could certainly water down my "recommendation" to a "suggestion" and move it outside the findings, more as an afterthought. The only positive finding is that "There is a consensus [for paid advisers] to declare a COI." I stand by that. — Cheers, Steelpillow (Talk) 18:56, 17 November 2023 (UTC)
- I agree with Rhododendrites, I'm afraid; I think you put more in the close than is present in the discussion. Mike Christie (talk - contribs - library) 18:42, 17 November 2023 (UTC)
- The brief closure discussion at the end is structured as a subtopic of the main discussion and not of the RfC. I therefore closed the main discussion. I "closed the RfC" in only one of my findings, viz. that there was no consensus (i.e. over the proposed wording); I do not regard that as an outright "rejection", but what do I know? If you feel this was an improper way to close the RfC that is as may be, but it does not imply it was an improper closure of the wider discussion, which was the main remit. — Cheers, Steelpillow (Talk) 18:28, 17 November 2023 (UTC)
- We use RfCs to ensure big decisions get a lot of outside input and to structure discussion. If your closure indeed was based "most" on discussions that were outside the RfC (preceding said outside input and preceding said structuring), it was not an appropriate way to close the RfC. This wasn't a case of finding some small nuance in external discussions to contextualize the RfC, but of rejecting the proposal of the RfC and imposing an outcome that was never proposed, that most people didn't address, that concerns a different policy, and which radically changes that policy. That's a hugely problematic thing for an RfC closing statement to do and a poor way to construct policy. — Rhododendrites talk \\ 18:02, 17 November 2023 (UTC)
- Heads up: I think this might be my first formal closure challenge. Sorry to do this to you, but I think this is a really problematic outcome: Wikipedia:Administrators'_noticeboard#Close_challenge:_Required_disclosure_for_admin_paid_advising. — Rhododendrites talk \\ 19:26, 17 November 2023 (UTC)
- Just dropped in to say thanks for taking it on, even though there was objection to your closure. Valereee (talk) 09:53, 19 November 2023 (UTC)
- Thanks to all for your advice, support and civility. To be honest, I was quite pleased that only one part of it was questioned. My purpose was as much to move things forward and clarify people's thoughts, as it was stagnating. But even now, with a blanket "no consensus" advocated and the significance of the issue highlighted, nobody else has yet stepped up, which disappoints me. I don't think it would be wise for me to engage further, though. — Cheers, Steelpillow (Talk) 11:09, 19 November 2023 (UTC)
mediawiki2latex now faster
Hi Steelpillow, mediawiki2latex now works many times faster due to http2 multiplexing and compression when downloading images an related information. You may try it online https://mediawiki2latex.wmflabs.org/ or install the Docker image see b:de:Benutzer:Dirk_Hünniger/wb2pdf/install#Using_Docker which works on any operating system. Yours Dirk Hünniger (talk) 10:07, 5 January 2024 (UTC)
Translation errors
You keep translating Swedish definitive viggen (the thunderbolt, the tufted duck) into indefinite forms. These are specifically translation errors. Blockhaj (talk) 21:45, 29 February 2024 (UTC)
- No. These are differences in the way the two languages are constructed. Translation may be "literal", exactly following the constructs of the source language, or it may instead seek to follow its own rules of grammar and syntax. Literal translation is seldom used, because it becomes unreadable. This is the real mistake here, to insist on bad English. Wikipedia is written in readable English. You also misunderstand when, where and how we do or do not use the term "bolt" as an abbreviation of "thunderbolt", and so on. You really need to step back and let native English speakers edit the text, and not try to second-guess our language for us. I should warn you now, that if you persist in your edit warring, sanctions may be taken against your user account here. — Cheers, Steelpillow (Talk) 09:30, 1 March 2024 (UTC)
- Your argument doesn't work. In what way does literal translation become unreadable? In what world is inflection seen as bad English? This is not Simple English Wikipedia. Bolt here is also the preferred translation of Viggen when referring to thunderbolt (sv: åskvigg), as it is missing the first element "åsk". The English word is likewise made up of two elements: thunder-bolt, and can be found in abbreviated form as "bolt", see for example Bolt (2008 film). I acknowledge that bolt is not a common abbreviation in the English language (beside use in phrases like "bolt of lightning"), but neither is vigg in Swedish. Blockhaj (talk) 22:34, 7 March 2024 (UTC)
- I have replied at Talk:Saab 210#Meaning of "Draken". If you don't like it, take me to WP:ANI, but you may wish you hadn't. — Cheers, Steelpillow (Talk) 11:16, 8 March 2024 (UTC)
- Your argument doesn't work. In what way does literal translation become unreadable? In what world is inflection seen as bad English? This is not Simple English Wikipedia. Bolt here is also the preferred translation of Viggen when referring to thunderbolt (sv: åskvigg), as it is missing the first element "åsk". The English word is likewise made up of two elements: thunder-bolt, and can be found in abbreviated form as "bolt", see for example Bolt (2008 film). I acknowledge that bolt is not a common abbreviation in the English language (beside use in phrases like "bolt of lightning"), but neither is vigg in Swedish. Blockhaj (talk) 22:34, 7 March 2024 (UTC)
Breguet or Bréguet
Bréguet or Breguet? There is certainly a case for Breguet however a lot of French language publications write it as Bréguet particularly when dealing with WW1 and the 1920s some examples:
https://heritage.medialibrary.safran-group.com/Heritage/media/21839
https://heritage.medialibrary.safran-group.com/Heritage/media/72186
Stivushka (talk) 06:18, 10 March 2024 (UTC)
- "A lot"? Really? The French sometimes make spelling mistakes too, you know. See for example https://www.breguet.com/en/classic-tour/paris which explains "Rue Bréguet, that carries by mistake an acute accent that does not feature in the family name." Evidently a common mistake, but a mistake nonetheless (and quite likely popularised by that very street name). Just google say "breguet alize" and you will soon see which generally gets an accent and which does not. — Cheers, Steelpillow (Talk) 11:16, 10 March 2024 (UTC)
- Yes, a lot … including Jane’s Fighting Aircraft of WW1.
- That said, there are also plenty books that spell it Breguet.
- Either way is fine by me but I can see a lot of back and forward edits Stivushka (talk) 13:17, 10 March 2024 (UTC)
- Updated the Renault 12F and 12Fe pages.
- For me the best argument in favour of spelling it Breguet is that this is the way it’s spelled in the Breguet 14 manual.
- https://commons.m.wikimedia.org/wiki/File:Breguet_14_Aircraft_Manual.pdf
- The manual does use accents. Not using them in the manufacturers name is clearly a deliberate choice. Stivushka (talk) 15:52, 27 March 2024 (UTC)