DZ
DefZone.Net

Kien thuc cong nghe & giai tri

Wiki Article

User talk:Redrose64

Nguồn dữ liệu từ Wikipedia, hiển thị bởi DefZone.Net

Xem trên WikipediaBài ngẫu nhiên khác
Hello, Redrose64! Welcome to Wikipedia! Thank you for your contributions. You may benefit from following some of the links below, which will help you get the most out of Wikipedia. If you have any questions you can ask me on my talk page, or place {{helpme}} on your talk page and ask your question there. Please remember to sign your name on talk pages by clicking or by typing four tildes "~~~~"; this will automatically produce your name and the date. If you are already loving Wikipedia you might want to consider being "adopted" by a more experienced editor or joining a WikiProject to collaborate with others in creating and improving articles of your interest. Click here for a directory of all the WikiProjects. Finally, please do your best to always fill in the edit summary field. Happy editing! --Jza84 |  Talk  13:18, 13 July 2009 (UTC)[reply]
Getting Started
Getting Help
Policies and Guidelines
The Community
Things to do
Miscellaneous

Flying Scotsman

[edit]

Just a quick note to acknowledge your correction to my Nigel Gresley edit. I didn't know about it being originally an A1. Thanks. Mike Marchmont (talk) 07:11, 24 October 2025 (UTC)[reply]

@Mike Marchmont: There were 52 built as Class A1 of which 51 were rebuilt to Class A3; a further 27 were built as Class A3. Dates of conversion from A1 to A3 are in List of LNER Class A1/A3 locomotives, column headed "Rebuilt". If there's no date, it's one of the 27 that were Class A3 from new. --Redrose64 🌹 (talk) 20:21, 24 October 2025 (UTC)[reply]

Loading gauge restoring

[edit]

Hello Redrose,

Thanks for healing the page on loading gauges. Somehow I managed to mess upp the table. However, I would like to see the Swedish sets of loading gauges (A/SEa and C/SEc) in the table with widths and heights. I see no reason to omit this relevant information.

We could also introduce the UK standard loading gauge W6A as a reference – I do not see it now.

I have returned to Wikipedia and some years back there was a visual editor available but I cannot see that one now unfortunately.

Kind regards,

Magnus Gajje (talk) 20:01, 26 October 2025 (UTC)[reply]

VisualEditor is still available, but even after nearly thirteen years, it's still buggy. Personally, I never use it. --Redrose64 🌹 (talk) 22:29, 26 October 2025 (UTC)[reply]

Apologies for the RfC ID mixup

[edit]

Your ID fix got mixed up in another editor dumping the contents of the prior discussion into the current RfC. Thanks for fixing it again. signed, Rosguill talk 23:30, 26 October 2025 (UTC)[reply]

Guide to temporary accounts

[edit]

Hello, Redrose64. This message is being sent to remind you of significant upcoming changes regarding logged-out editing.

Starting 4 November, logged-out editors will no longer have their IP address publicly displayed. Instead, they will have a temporary account (TA) associated with their edits. Users with some extended rights like administrators and CheckUsers, as well as users with the temporary account IP viewer (TAIV) user right will still be able to reveal temporary users' IP addresses and all contributions made by temporary accounts from a specific IP address or range.

How do temporary accounts work?

Editing from a temporary account
  • When a logged-out user completes an edit or a logged action for the first time, a cookie will be set in this user's browser and a temporary account tied with this cookie will be automatically created for them. This account's name will follow the pattern: ~2025-12345-67 (a tilde, year of creation, a number split into units of 5).
  • All subsequent actions by the temporary account user will be attributed to this username. The cookie will expire 90 days after its creation. As long as it exists, all edits made from this device will be attributed to this temporary account. It will be the same account even if the IP address changes, unless the user clears their cookies or uses a different device or web browser.
  • A record of the IP address used at the time of each edit will be stored for 90 days after the edit. Users with the temporary account IP viewer (TAIV) user right will be able to see the underlying IP addresses.
  • As a measure against vandalism, there are two limitations on the creation of temporary accounts:
    • There has to be a minimum of 10 minutes between subsequent temporary account creations from the same IP (or /64 range in case of IPv6).
    • There can be a maximum of 6 temporary accounts created from an IP (or /64 range) within a period of 24 hours.

Temporary account IP viewer user right

How to enable IP Reveal

Impact for administrators

  • It will be possible to block many abusers by just blocking their temporary accounts. A blocked person won't be able to create new temporary accounts quickly if the admin selects the autoblock option.
  • It will still be possible to block an IP address or IP range.
  • Temporary accounts will not be retroactively applied to contributions made before the deployment. On Special:Contributions, you will be able to see existing IP user contributions, but not new contributions made by temporary accounts on that IP address. Instead, you should use Special:IPContributions for this (see a video about IPContributions in a gallery below).

Rules about IP information disclosure

  • Publicizing an IP address gained through TAIV access is generally not allowed (e.g. ~2025-12345-67 previously edited as 192.0.2.1 or ~2025-12345-67's IP address is 192.0.2.1).
  • Publicly linking a TA to another TA is allowed if "reasonably believed to be necessary". (e.g. ~2025-12345-67 and ~2025-12345-68 are likely the same person, so I am counting their reverts together toward 3RR, but not Hey ~2025-12345-68, you did some good editing as ~2025-12345-67)
  • See Wikipedia:Temporary account IP viewer § What can and can't be said for more detailed guidelines.

Useful tools for patrollers

  • It is possible to view if a user has opted-in to view temporary account IPs via the User Info card, available in Preferences → Appearance → Advanced options → Tick Enable the user info card
    • This feature also makes it possible for anyone to see the approximate count of temporary accounts active on the same IP address range.
  • Special:IPContributions allows viewing all edits and temporary accounts connected to a specific IP address or IP range.
  • Similarly, Special:GlobalContributions supports global search for a given temporary account's activity.
  • The auto-reveal feature (see video below) allows users with the right permissions to automatically reveal all IP addresses for a limited time window.

Videos

  • How to use Special:IPContributions
  • How automatic IP reveal works
  • How to use IP Info
  • How to use User Info

Further information and discussion

Most of this message was written by Mz7 (source). Thanks, 🎃 SGrabarczuk (WMF) (talk) 02:47, 31 October 2025 (UTC)[reply]

Welsh Lifeboat Stations

[edit]

Thanks for the edits. Just wondering why you stopped there? All the other welsh stations are all the same, I'm just eliminating <br which apparently causes issues with screen readers??

I should add: Contrary to what you may think of me, (I saw you highlight my name some while ago), I'm a reasonable chap. I'm working hard to get stuff correct and presented well, as you will see from my edit history. There is no need to highlighting your disapproval of me at every edit.

I would very much prefer that someone message and say, Why are you doing that?, have you considered there's a better of different way?

Martin Ojsyork (talk) 23:30, 2 November 2025 (UTC)[reply]

Why did I stop? Because I was seriously behind on more pressing matters. Later this week, when I have time, I will look at other Welsh lifeboat station articles, and fix those where necessary. BTW, this edit of yours was not eliminating <br />, it was overloading the |name= parameter. --Redrose64 🌹 (talk) 23:13, 3 November 2025 (UTC)[reply]
@Redrose64
There is a genuine reason for making the welsh name text the same size as english name text, as I have been asked to do so by the folks at some welsh stations who know I edit pages. If you think I'm doing things wrong, then as I said earlier, I would very much prefer that someone message and say,
Why are you doing that?, Have you considered there's a better or different way? Rather than getting all angry trying to make a point.
I'm not perfect by any means, just trying hard to get stuff right.
Martin Ojsyork (talk) 00:29, 4 November 2025 (UTC)[reply]
First, in the edit that I linked above, you didn't make it the same size - you used <small>...</small>. Second, you have stuffed two values into one parameter, this is known as overloading and should be avoided. Separate parameters for each name have been provided for a very good reason. Third, non-English text should be marked up with the appropriate language code, this is what |native_name_lang=cy does. --Redrose64 🌹 (talk) 22:01, 4 November 2025 (UTC)[reply]
@Redrose64
Updates.
I wanted to say thanks for the Map updates. I always seem to have struggled with the correct maps, as the source confuses me
Maybe it needed a review of each one as you went along, as there are a couple that just don't work, or make things clear, (like Vale of Glamorgan), which may get a revisit, but generally, its a huge improvement.
I wanted to ask, if <br causes issues with screen readers, what else would you use instead of ubl, to create a page break?
Martin Ojsyork (talk) 10:11, 9 November 2025 (UTC)[reply]
The <br /> tag, of itself, doesn't cause any issues with screen readers. The problem is when it's being used for the wrong purpose. It's absolutely fine when used in a position that a normal space would be valid; but when it's being used as a separator between two items of what is intended to be a list, screen readers won't recognise it as a list - they will treat it as running prose. That is to say, if something is intended to be interpreted as a list, it must be marked up as a list. More at MOS:NOBR.
Similarly, the opposite situation also applies: the {{ubl}} template must be used only to create a list - it mustn't be used to introduce forced line breaks into longer phrases. --Redrose64 🌹 (talk) 10:27, 9 November 2025 (UTC)[reply]
@Redrose64
That conflicts with everything I have been told about <br
So recently I've been trying to remove <br at all costs (primarily to suit one other particular editor, who to be honest has been the bain of my life since I started editing 2 years ago).
Now I understand better, it will be approached differently. I can still use <br to present things more clearly, with the understanding that in those cases, screen readers will still see all the info properly, even if its not presented properly.
But treat proper lists with ubl
Thankyou
Martin Ojsyork (talk) 10:44, 9 November 2025 (UTC)[reply]
First, please don't use bare less-than signs to describe markup, even if unclosed. Much better methods exist, for instance there is Template:Tag which I used above. Second, who has told you not to use <br /> "at all costs"? --Redrose64 🌹 (talk) 11:39, 9 November 2025 (UTC)[reply]
I have a feeling he’s referring to the bizarre argument that happened about sortable tables on @10mmsocket’s talk page (now in his archive 3) a few months back… Danners430 tweaks made 12:10, 9 November 2025 (UTC)[reply]
@Danners430
@Redrose64
Yes, correct, although its much deeper than sortable tables.
(I don't use bare less-than signs, it was only for the purpose of the conversation - (now learned how to <br /> )
Who? - don't get me started! :o)
When I started editing Lifeboat fleet pages, all the stations and dates per boat were listed as, for example...
Amble<br />Fleetwood<br />Poole
Being inexperienced at that time, I just continued with what went before, but I had one editor following me round, absolutely slating the use of <br />, highlighting its problems with screen readers. (I don't know, I've never seen one!)
He set about replacing with Rowspans, but that doesn't work, as the format can be way out of line, and presents information wrongly.
He also went on to amend virtually everything I did, following me round, re-editing text, changing format, etc. Didn't matter what I did, he changed it, even going against his own earlier formatting techniques, just to make it different. One page, the text update was re-edited within 6 minutes. Often it was less than 24 hours. There wasn't anything wrong, it just wasn't written how he preferred. I've spent hours sorting out lifeboats and stations, (particularly appledore and lizard, for him to re-edit into one big mixed up list.
If I complained that it was vandalism, or edit waring, he just strategically waited 2 or three months.
I added Station honours to each page as a simple list of easily readable awards. Where he can, he replaces with a whole load of wordy text.
There isn't an edit I've made on any of the south west lifeboat pages that hasn't been modified / deleted ('his' area!).
SO - regarding the use of <br />, when someone showed me <ubl /> a few weeks ago, it seemed like the logical replacement to try in some way to appease this person.
I don't need to say who - you already know.
Martin Ojsyork (talk) 12:16, 9 November 2025 (UTC)[reply]
Just a note - other people's talk pages are NOT the places to discuss a third party's conduct; indeed, it's frowned upon. If you have a complaint about a user, you either raise it at the relevant noticeboard, or discuss it with them. Talking behind their back is just as uncivil as stalking, as you're accusing them of doing. Danners430 tweaks made 12:21, 9 November 2025 (UTC)[reply]

@Ojsyork: What I wanted to do was see the actual advice that you were given, to see if it was bad advice, or good advice that you were misinterpreting. But let's leave that for a moment. I don't know which article was being referred to either, so I've had a look at this edit. I didn't pick it at random: it's the most recent edit of yours that has an edit summary reading Remove all < br / >. There's quite a lot going on, but looking through it I find the first removal of <br /> has the old version as follows: 

|-
| SC-T05
| HF14 HLJ
| Supacat
| {{small|Unnamed}}
| Relief fleet<br/>{{Lbs|Lytham St Annes}}<br/>Relief fleet
| {{nowrap|2014–2019}}<br/>2019–2021<br/>2021–
|

and the new version as follows: 

|-
| SC-T05
| HF14 HLJ
| {{small|Unnamed}}
| {{ubl|{{nowrap|2014–2019}}|2019–2021|2021–}}
| {{ubl|Relief fleet|{{Lbs|Lytham St Annes}}|Relief fleet}}
| Supacat
|

Both of these are bad for accessibility. The first version makes a table row like this:

Op.No. Reg No. Manufacturer Name Station In service Comments
SC-T05 HF14 HLJ Supacat Unnamed Relief fleet
Lytham St Annes
Relief fleet 		2014–2019
2019–2021
2021–

and the second version makes a table row like this:

Op.No. Reg No. Name In service Station Manufacturer Comments
SC-T05 HF14 HLJ Unnamed
  • 2014–2019
  • 2019–2021
  • 2021–
Supacat

For a sighted reader, it's easy to associate the date range 2019–2021 with the Lytham St Annes station in both versions of the table. But for a screen reader user, it's not. In the old version, they will hear something like "Relief fleet Lytham St Annes Relief fleet" and then "2014–2019 2019–2021 2021–"; in the new version, they will hear something like "List of three items. First item, 2014–2019. Next item, 2019–2021. Next item: 2021–. End of list." and then "List of three items. First item, Relief fleet. Next item, Lytham St Annes. Next item: Relief fleet. End of list." It should be clear that in neither case is there any association between 2019–2021 and Lytham St Annes. Now consider it as three table rows instead of one. The markup is as follows: 

|-
|rowspan=3 | SC-T05
|rowspan=3 | HF14 HLJ
|rowspan=3 | {{small|Unnamed}}
| {{nowrap|2014–2019}}
| Relief fleet
|rowspan=3 | Supacat
|rowspan=3 |
|-
| 2019–2021
| {{Lbs|Lytham St Annes}}
|-
| 2021–
| Relief fleet

and the rendered table is as follows:

Op.No. Reg No. Name In service Station Manufacturer Comments
SC-T05 HF14 HLJ Unnamed 2014–2019 Relief fleet Supacat
2019–2021 Lytham St Annes
2021– Relief fleet

All the information is still there, and for a sighted reader, it's pretty much in the same positions. But the significant difference is when it's put through a screen reader: each station name is read out directly after the date range to which it relates. This is much better for accessibility. --Redrose64 🌹 (talk) 14:24, 9 November 2025 (UTC)[reply]

@Redrose64
Have a look at Watson-class_lifeboat
  • Particularly, ON 535
It looks to me like Charlie Medland is the name at the first two locations,
and Reserve No.7E is the name in the reserve fleet and Brighton
Except of course, Charlie Medland is the name used in Brighton.
  • If you then look at ON 581
Looks like Maria Stephenson is just Buckie
But it was Maria Stephenson at Moelfre and Penrhyn Du as well.
Martin Ojsyork (talk) 15:11, 9 November 2025 (UTC)[reply]
There's a very simply solution here - move the Reserve note into the Comments field for the rows to which it applies, and apply the name across all four rows. Danners430 tweaks made 15:18, 9 November 2025 (UTC)[reply]
Agree with Danners there. --Redrose64 🌹 (talk) 15:44, 9 November 2025 (UTC)[reply]
We'll have to see how it goes.
I'm not sure I have that many years left in me, and I'm only 61
Not to mention I find creating Rowspan incredibly difficult!
Martin Ojsyork (talk) 15:55, 9 November 2025 (UTC)[reply]
Have you tried the visual editor? Danners430 tweaks made 15:56, 9 November 2025 (UTC)[reply]
No, but just had a look,I'm not sure it will help me!
Need some practice.
I'll see how things evolve.
Martin Ojsyork (talk) 16:10, 9 November 2025 (UTC)[reply]
I primarily use it for tables - visual editor has controls to merge and unmerge cells in a WYSIWYG style, like Excel or Word, rather than using code to merge cells. Danners430 tweaks made 16:12, 9 November 2025 (UTC)[reply]
I never use VE - it still has unfixed reported bugs fifteen years after launch (e.g. phab:T60488 is from twelve years ago). I use rowspan perfectly happily, as I did above. How old did you think I am then? --Redrose64 🌹 (talk) 16:44, 9 November 2025 (UTC)[reply]
How old, 61 and from Bolton!
While we here, which school?
Martin Ojsyork (talk) 17:12, 9 November 2025 (UTC)[reply]
Sorry
I guess that was a question too far?
I'll just say Rivington & Blackrod, and leave it there!
Thanks for all the advice. All I ask, please don't judge me on previous difficulties elsewhere!
Martin Ojsyork (talk) 21:09, 9 November 2025 (UTC)[reply]

A big red 30 at the top of the page.

[edit]

No, YOU amend footnotes whitelist, you're the one who know how. DuncanHill (talk) 23:32, 10 November 2025 (UTC)[reply]

Even better, you tell Mackensen to do it. They're the one causing the problem, not me. DuncanHill (talk) 23:33, 10 November 2025 (UTC)[reply]
@DuncanHill: If you would care to look at my contribs, you would see that I fixed it before reverting your edits. I didn't count them; maybe there were 30, maybe not. But using {{sfn whitelist}} on each of 30 (or thereabouts) pages instead of one edit to a single page clearly indicates that the issue was approached in the wrong way. Did you drop a note on Mackensen (talk · contribs) pointing out the errors? --Redrose64 🌹 (talk) 07:06, 11 November 2025 (UTC)[reply]
I haven't the faintest idea how to edit the whitelist. Perhaps you could show me? Even better, perhaps you could show the people who need to know, namely the people making the templates that generate the error messages? User:Mackensen went back and made more edits to all those articles, and more, using another way of hiding the error after your reversions, like this . And I can see from your edits that you haven't mass-undone them, and you haven't used mass edit-summaries to tell them off for it. But they are an admin, as are you, and I ain't, so guess who gets the mass edit-summary negativity? I shall ignore the error, and you, as much as possible in future. DuncanHill (talk) 11:48, 11 November 2025 (UTC)[reply]
I know about the whitelist, but had forgotten to update it. I did so for Dow's third volume. The edit you reference there wasn't me avoiding the whitelist problem, but rather dealing with the fact that all three of the Dow reprints were published in the same year, 1985, and there are numerous articles where multiple volumes are referenced. The default short references (Dow1985) couldn't be used because they would be ambiguous.
Anyway, the whitelist is at Module:Footnotes/whitelist. It's an arcane bit of knowledge, but the right place to address these issues when source templates are used. Mackensen (talk) 11:54, 11 November 2025 (UTC)[reply]
@Mackensen: Then why did all those edits appear on my watchlist as you removing articles from the no-target category? That's literally the only reason I knew you did them. DuncanHill (talk) 11:56, 11 November 2025 (UTC)[reply]
The no-target issue in that case is because the {{Dow-GC3}} template previously gave a date of 1965, which is what the {{sfn}} templates referenced. When I corrected the date on the template to 1985, that created a legitimate no-target error until I had a chance to update it. Because that article used two volumes of Dow with the same date, I had to use different anchor names to disambiguate. On other articles, where only one volume is in use (see Special:Diff/1321509879), that wasn't necessary. Mackensen (talk) 12:07, 11 November 2025 (UTC)[reply]

Lint errors

[edit]

Please fix bogus image options -- ~2025-31117-12 (talk) 22:52, 12 November 2025 (UTC)[reply]

They're not "bogus image options", they're perfectly valid. Compare this: super with this: bottom - do you see the difference? --Redrose64 🌹 (talk) 22:59, 12 November 2025 (UTC)[reply]
Hmm. Now we have this]. What's going on? -- ~2025-31117-12 (talk) 23:06, 12 November 2025 (UTC)[reply]
What's going on is a bug in the linter, turning out false positives. --Redrose64 🌹 (talk) 23:09, 12 November 2025 (UTC)[reply]
That's a problem. Has this been escalated? -- ~2025-31117-12 (talk) 23:51, 12 November 2025 (UTC)[reply]
Appears there's an error when the captions are equivalent to a command word parameter, so it thinks there's either two vertical-alligns or two captions, whichever's got the higher priority parameter. For now, I've put the captions of the images within the vertical-alignment section on the WP:EIS page in "quotes" to differentiate them from the vertical-alignment parameters to clear the errors, and left an edit comment. About to ask about this to the Linter community next. I wouldn't be surprised if there's a phab ticket on this, I just hadn't been aware of this particular error until today since most people aren't captioning images as bottom or sup, so apologies for erring with my edit the other day, just have seen too many cases where people doubled up on a parameter or tried to have multiple captions so thought it was a human error and not a bug. Zinnober9 (talk) 00:28, 13 November 2025 (UTC)[reply]

Taxonomic categories

[edit]

Hi, You reverted my edit to add the genus Psalidodon to its own category. I have reverted that edit. It is normal practice in articles on taxa to include the higher taxon in its eponymous category, alongside the "daughter" articles, and to use the style [[Genus| ]] or [[Family| ]]. Taxonomy works in nested heirarchies (unless you are a Creationist!) and I think this reflects that. Quetzal1964 (talk) 08:08, 13 November 2025 (UTC)[reply]

@Quetzal1964:, Yes, it is indeed normal practice in articles on taxa to include the higher taxon in its eponymous category. But that's about categorising articles, not about categorising categories. You should never put a category inside itself; more generally, you should not create category loops. Accordingly, I have reverted you again. --Redrose64 🌹 (talk) 21:35, 13 November 2025 (UTC)[reply]
“The article itself should be a member of the eponymous category. It should be sorted with a space, so that it appears at the start of the category listing” from WP:Categorization. Please restore my edit. Quetzal1964 (talk) 21:43, 13 November 2025 (UTC)[reply]
Exactly: The article itself. This edit does not categorise the article; it categorises the category page. I will not be restoring your edit. --Redrose64 🌹 (talk) 22:27, 13 November 2025 (UTC)[reply]
I agree, I was confusing myself. Apologies. I have now corrected my edit, to what I meant to do. Thank you for your patience. Quetzal1964 (talk) 22:52, 13 November 2025 (UTC)[reply]

Question

[edit]

Hello! I'm in the process of analyzing recent changes data, and I came across some strange technical element across all your (and a few others') edits. If you don't mind, can you tell me if you are using any scripts or gadgets that modify/augment the editing process, the skin you are using, and also if you have JavaScript disabled? Again, this is not a bad thing, just something I haven't found a way to explain yet. Thanks, Children Will Listen (🐄 talk, 🫘 contribs) 01:40, 16 November 2025 (UTC)[reply]

@ChildrenWillListen: Which "strange technical element" are you referring to? Which pages or edits has this occurred on? --Redrose64 🌹 (talk) 08:06, 16 November 2025 (UTC)[reply]
I've investigated this myself, and with @4meter4's help, found out that it is because you either have JavaScript disabled or have disabled the 2010 wikitext editor in Special:Preferences. It's a minor tagging issue and isn't a big deal, and it probably isn't a bug either. Children Will Listen (🐄 talk, 🫘 contribs) 08:15, 16 November 2025 (UTC)[reply]
What if I have done either of those (and I'm not saying that I have)? Where is the problem? Please indicate some bad edits that I've made. --Redrose64 🌹 (talk) 08:34, 16 November 2025 (UTC)[reply]
There is no problem, it's a technical quirk that's invisible to the naked eye and does not affect content in any way. All your edits have it. Children Will Listen (🐄 talk, 🫘 contribs) 13:03, 16 November 2025 (UTC)[reply]
So why bring it up? I edit the same way that I've done for 16+ years, as least as far as I can within the constraints imposed by occasional changes to the MediaWiki software. If you want to know why I don't use Visual Editor, it's because it's a heap of crap. When I make an edit, I want to know exactly what I'm changing. I don't want something in the background trying to guess what I intended and then saving something that is at 90° to what I wanted. --Redrose64 🌹 (talk) 20:29, 16 November 2025 (UTC)[reply]

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:31, 18 November 2025 (UTC)[reply]

CfD nomination at Wikipedia:Categories for discussion/Log/2025 November 28 § Jet skiing at the 2025 SEA Games

[edit]

Categories you have created have been nominated for possible deletion, merging, or renaming. A discussion is taking place to decide whether this proposal complies with the categorization guidelines. If you would like to participate in the discussion, you are invited to add your comments at Wikipedia:Categories for discussion/Log/2025 November 28 § Jet skiing at the 2025 SEA Games on the categories for discussion page. Thank you. Place Clichy (talk) 12:04, 28 November 2025 (UTC)[reply]

Cowley Branch Line

[edit]

I tried to wikilink to Cowley Branch Line, only it doesn't exist. As it your back yard (I think?), would you like to do the honours? Or you can leave it to me, I'll make a mess of it, you'll have to correct it and it will take longer than if you had done it in the first place. 𝕁𝕄𝔽 (talk) 19:40, 28 November 2025 (UTC)[reply]

And more specifically, I'm trying to make sense of

Following wider support for the Cowley Plus scheme from the local community, Network Rail and the government, we’re currently working on our designs on the basis that the Cowley Branch Line will be reopened, as proposed by Oxford City Council. This would mean that platform capacity will be freed up at Oxford station, allowing the full EWR service to run to Oxford station. More details will be provided when we consult in 2026.

— East West Rail, November 2025 report, §4.5.1

Does it make sense to you? --𝕁𝕄𝔽 (talk) 19:47, 28 November 2025 (UTC)[reply]

@JMF: It's not so much a branch line, more a truncated portion of the Wycombe Railway (qv). I think that the original proposal was for EWR services to terminate at Oxford, but the new proposal is that they would now continue to Cowley and terminate there. This will result in far less platform occupation at Oxford, and therefor better utilisation. This is because when a train terminates, the time at platform is much longer than for a train that merely calls: for one thing, staff need to board the terminating train in order to clear out the inattentive passengers. At Oxford, there are only four platforms - two through, and two north-facing bays. Some terminating trains remain in platform to form the next service back to wherever they came from, but some will be parked in sidings for some time until required for a return trip. This means that people intending to catch a later train from the same platform need to be deterred from boarding; this also occupies staff. I often see that a terminating train from Didcot will occupy platform 4 for far longer than might be expected (perhaps somebody wouldn't wake up), with the result that a Bournemouth to Manchester service has to wait outside the station for the now-empty Didcot train to run to the sidings allowing platform 4 to be released. --Redrose64 🌹 (talk) 23:46, 28 November 2025 (UTC)[reply]
Tyvm, that makes sense. It probably also explains the reason for Cambridge East being added to the plan - to keep Cambridge (Central) clear. There is a fairly large vacant site for new sidings there (off Coldham's Lane, west of Cherry Hinton). 𝕁𝕄𝔽 (talk) 10:27, 29 November 2025 (UTC)[reply]

Clayton & Shuttleworth

[edit]

Yeah I think that's due to people importing flickr albums from events. At least its means we've got the stuff and in decent weather (Bedfordshire Steam & Country Fayre was rather wet this year). Traction engines aren't usually out much in November mind.©Geni (talk) 20:58, 30 November 2025 (UTC)[reply]

"Surya Namask?r" listed at Redirects for discussion

[edit]

The redirect Surya Namask?r has been listed at redirects for discussion to determine whether its use and function meets the redirect guidelines. Anyone, including you, is welcome to comment on this redirect at Wikipedia:Redirects for discussion/Log/2025 December 3 § Surya Namask?r until a consensus is reached. Steel1943 (talk) 23:52, 3 December 2025 (UTC)[reply]

RfC - Airport destination lists

[edit]

Hi, for your information, as you were involved in the previous discussion at Wikipedia:Village pump (policy)/Airport destination lists or the RfC on consensus of WP:DESTNOT at WT:NOT, I wanted to let you know that the discussed broader RfC has been opened at WP:VPP#RfC - The inclusion of destination lists in Airport articles. If you wish to contribute, please feel free. Many thanks! Danners430 tweaks made 20:42, 7 December 2025 (UTC)[reply]

A Very Merry Christmas to you!

[edit]

Hello there. 'Tis the season again, believe it or not, the years pass so quickly now! Your contributions to Wikipedia in 2025 are greatly appreciated! Wishing you a Very Merry Christmas, and here's to a happy and productive 2026! ♦ Dr. Blofeld 19:13, 18 December 2025 (UTC)[reply]

Thank you Blowers. --Redrose64 🌹 (talk) 20:10, 18 December 2025 (UTC)[reply]

Season's Greetings!

[edit]
Season's Greetings
Wishing everybody a Happy Holiday Season, and all best wishes for the New Year! The The Dream of Saint Joseph (1640s) by Philippe de Champaigne is my Wiki-Christmas card to all for this year. Johnbod (talk) 17:36, 19 December 2025 (UTC)[reply]
Thank you Johnbod. --Redrose64 🌹 (talk) 20:53, 19 December 2025 (UTC)[reply]

Season's greetings

[edit]
Season's Greetings
Wishing everybody a Happy Holiday Season, and all best wishes for the New Year! Dowth, a neolithic passage tomb in Ireland is my Wiki-Solstice card to all for this year.
("During the winter solstice, the light of the low sun moves along the left side of the passage, then into the circular chamber, where three stones are lit up by the sun. The convex central stone reflects the sunlight in to a dark recess, lighting up the decorated stones there.") --𝕁𝕄𝔽 (talk) 11:11, 19 December 2025 (UTC)[reply]
Thank you JMF. --Redrose64 🌹 (talk) 20:53, 19 December 2025 (UTC)[reply]

Seasons greetings!

[edit]

Snowy winter landscape with trees at Shipka Pass

Wishing you and yours a fantastic Christmas (or holiday season for those who don’t celebrate) and all the best for 2026. 🎄 ❄️☃️

Here’s to a collaborative, constructive year ahead — with good faith, good edits, and just enough discussion to get things done!

(and here's Sir Nils Olav inspecting his troops... one of my favourite POTDs)

Cheers  — Amakuru (talk) 15:12, 21 December 2025 (UTC)[reply]

Penguin inspecting uniformed soldiers

 — Amakuru (talk) 15:12, 21 December 2025 (UTC)[reply]

Thank you Amakuru. --Redrose64 🌹 (talk) 17:56, 21 December 2025 (UTC)[reply]

CS1 error on John Fowler & Co.

[edit]

Hello, I'm Qwerfjkl (bot). I have automatically detected that this edit performed by you, on the page John Fowler & Co., may have introduced referencing errors. They are as follows:

  • A missing title error. References show this error when they do not have a title. Please edit the article to add the appropriate title parameter to the reference. (Fix | Ask for help)

Please check this page and fix the errors highlighted. If you think this is a false positive, you can report it to my operator. Thanks, Qwerfjkl (bot) (talk) 22:07, 22 December 2025 (UTC)[reply]

Nomination for discussion of Template:Editnotices/Page/The Enchanted Wood (novel)

[edit]

Template:Editnotices/Page/The Enchanted Wood (novel) has been nominated for discussion. You are invited to comment on the discussion at the entry on the Templates for discussion page. –LaundryPizza03 (dc̄) 09:46, 24 December 2025 (UTC)[reply]

Nomination for discussion of Template:Editnotices/Page/The Folk of the Faraway Tree

[edit]

Template:Editnotices/Page/The Folk of the Faraway Tree has been nominated for discussion. You are invited to comment on the discussion at the entry on the Templates for discussion page. –LaundryPizza03 (dc̄) 09:47, 24 December 2025 (UTC)[reply]

Nomination for discussion of Template:Editnotices/Page/The Magic Faraway Tree (novel)

[edit]

Template:Editnotices/Page/The Magic Faraway Tree (novel) has been nominated for discussion. You are invited to comment on the discussion at the entry on the Templates for discussion page. –LaundryPizza03 (dc̄) 09:51, 24 December 2025 (UTC)[reply]

Happy New Year, Redrose64!

[edit]
Happy New Year!

Redrose64,
Have a prosperous, productive and enjoyable New Year, and thanks for your contributions to Wikipedia.
Abishe (talk) 14:31, 31 December 2025 (UTC)[reply]

   Send New Year cheer by adding {{subst:Happy New Year fireworks}} to user talk pages.

Abishe (talk) 14:31, 31 December 2025 (UTC)[reply]

Thank you, Abishe! --Redrose64 🦌 (talk) 12:13, 1 January 2026 (UTC)[reply]

My apologies

[edit]

I really thought your account was hacked, hence the WP:AIV report. It turned out the "user gone rogue" was @TattooedLeprechaun:, who has been blanking talk pages; you were reverting their edits. Really should have looked before I lept. Mvcg66b3r (talk) 14:51, 31 December 2025 (UTC)[reply]

@Mvcg66b3r: I suggest that you look at Wikipedia:Administrators' noticeboard/Incidents#TattooedLeprechaun, which is what I was acting upon in my capacity as an administrator. --Redrose64 🦌 (talk) 15:04, 31 December 2025 (UTC)[reply]

WIkiProject Doctor Who: December 2025 Newsletter

[edit]
The Space-Time Telegraph
Volume III, Issue III — December 2025
Brought to you by the editors of WikiProject Doctor Who
Help! We've been robbed... of a new Doctor Who Christmas special this year :(
2025... I Let You Go
*vworp vworp, vworp vworp*
The Space-Time Telepgraph is back again with our final issue of the year. With 13-episodes of Who-related content broadcast in 2025, it marked the biggest year in the Whoniverse since 2017! Take a quick read below for all the Wikipedia-related (and non-Wikipedia-related) Doctor Who news that you missed, and everything you have to look forward to. Happy New Year! 🥳🎉

Would you like a jelly baby Good or Featured article?

It's been several months since the last newsletter, and a number of new GAs have been added to the quality content list. In total we have promoted nearly 50 Good Articles this year, on top of one Featured Article, making this the year with the largest amount of promoted Doctor Who-related content in Wikipedia history (Beating our previous record of 2012's 36 by a significant margin).
Congratulations to all of our editors who have contributed to quality content this year, and we hope to see the number of quality articles under our project grow as time goes on.

Intelligence Bulletin from the Subwave Network

  • A five-part miniseries and spin-off of Doctor Who, The War Between the Land and the Sea concluded airing this month on BBC One. The series will release on Disney+ next year. The conclusion of that series on Disney+ will officially mark the end of the co-production deal between the Beeb and the Mouse House that was first announced in 2022. While Doctor Who has been confirmed to continue with a 2026 Christmas Special written by Russell T Davies, its status in international markets has yet to be announced. CBeebies has also found an animation partner for a 52-part animated spin-off set to begin production next year and air across two series from 2027–2029.
  • The War Between will also receive a DVD and Blu-ray release on 27 February. A physical release of the soundtrack album for that series from Lorne Balfe will precede it on 30 January; however, it is already available on digital platforms. On 12 December, the long-awaited and long-requested tenth series soundtrack from Murray Gold was published.
  • Season 21 will receive a "Collection" release on 16 March, featuring a remastered episodes with new special features. Additionally a plethora of new audio and print stories are due for publication in early 2026.

Their songs have ended... but their stories never end 🌹

Since the previous issue was published, a number of people related to the Whoniverse have sadly passed away and some who passed away before the previous issue only had their deaths announced recently:

2019

2020

2021

2022

Their songs have ended... but their stories never end 🌹 (continued)

2023

2024

  • 10 March - Conrad Monk, 87, actor (The Daleks' Master Plan)
  • 25 July - Brian White, cameraman (regular from 1960s onwards, work includes the Dalek POV at the end of The Daleks - "The Dead Planet")

2025

Notes

  1. ^ The reported birth date doesn't match any birth record so the accuracy of this age is uncertain.


Contributors:


If you wish to contribute to future editions of the newsletter, leave a message on the WikiProject talk page or reach out to one of the current contributors listed above.
If you do not wish to receive future editions of the Space-Time Telegraph, please remove your name from our our mailing list.

MediaWiki message delivery (talk) 19:37, 31 December 2025 (UTC)[reply]

Happy new year

[edit]

Happy New Year!

Hello Redrose64: Thanks for all of your contributions to Wikipedia, and have a great New Year! Cheers, Iggy (Swan) (Contribs) 11:30, 1 January 2026 (UTC)[reply]



Send New Year cheer by adding {{subst:Happy New Year snowman}} to people's talk pages with a friendly message.

Thank you, Iggy the Swan! --Redrose64 🦌 (talk) 12:12, 1 January 2026 (UTC)[reply]

January music

[edit]
story · music · places

300 years ago, a Bach cantata was born: happy new year! - Thank you cleaning up greetings! -- Gerda Arendt (talk) 20:06, 1 January 2026 (UTC)[reply]

Ooops, sorry; I was listening to some Strauss earlier - quite by chance, and not because I watched 2001 twice last week. --Redrose64 🦌 (talk) 20:15, 1 January 2026 (UTC)[reply]

Nomination for discussion of Template:The Faraway Tree editnotice

[edit]

Template:The Faraway Tree editnotice has been nominated for discussion. You are invited to comment on the discussion at the entry on the Templates for discussion page. –LaundryPizza03 (dc̄) 21:28, 5 January 2026 (UTC)[reply]

Ayton railway station

[edit]

The navbox in the body of the article only shows the Berwickshire Railway information.

Can you please add the inforormation to that navbox that will also show the preceding and following stations on the main line of the North British Railway

Heald Green (talk) 23:43, 5 January 2026 (UTC)[reply]

@Heald Green: Ayton station is a settlement in Canada, and has nothing about railways. It's also a location that I know nothing about. There are also no clues in your editing history. Please provide the exact page name in the form of a Wikilink. --Redrose64 🦌 (talk) 00:22, 6 January 2026 (UTC)[reply]
Thanks for your reply. The railway station to which I made reference to was the one in Scotland, situated on the main line of the North British Railway near to Reston. It opened on 22 June 1846 and closed on 8 Feb 1962. Heald Green (talk) 06:53, 6 January 2026 (UTC)[reply]
But what is the exact name of the article? Reston is a disambiguation page. --Redrose64 🦌 (talk) 09:18, 6 January 2026 (UTC)[reply]
The name of the Wikipedia article about this railway station in Scotland is Ayton railway station. Heald Green (talk) 10:15, 6 January 2026 (UTC)[reply]
OK,  Done, see here. --Redrose64 🦌 (talk) 23:19, 6 January 2026 (UTC)[reply]