Talk:Main Page

Page contents not supported in other languages.
Page semi-protected
From Wikipedia, the free encyclopedia
Archives: Sections of this page older than three days are automatically relocated to the newest archive.

001 002 003 004 005 006 007 008 009 010 011 012 013 014 015 016 017 018 019 020 021 022 023 024 025 026 027 028 029 030 031 032 033 034 035 036 037 038 039 040 041 042 043 044 045 046 047 048 049 050 051 052 053 054 055 056 057 058 059 060 061 062 063 064 065 066 067 068 069 070 071 072 073 074 075 076 077 078 079 080 081 082 083 084 085 086 087 088 089 090 091 092 093 094 095 096 097 098 099 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207

Main Page error reports

To report an error in content currently or imminently on the Main Page, use the appropriate section below.

  • Where is the error? An exact quotation of the text in question helps.
  • Offer a correction if possible.
  • References are helpful, especially when reporting an obscure factual or grammatical error.
  • Time zones. The Main Page runs on Coordinated Universal Time (UTC, currently 13:21 on 24 May 2024) and is not adjusted to your local time zone.
  • Can you resolve the problem yourself? If the error lies primarily in the content of an article linked from the Main Page, fix the problem there before reporting it here. Text on the Main Page generally defers to the articles with bolded links. Upcoming content on the Main Page is usually only protected from editing beginning 24 hours before its scheduled appearance. Before that period, you can be bold and fix any issues yourself.
  • Do not use {{edit fully-protected}} on this page, which will not get a faster response. It is unnecessary, because this page is not protected, and causes display problems. (See the bottom of this revision for an example.)
  • No chit-chat. Lengthy discussions should be moved to a suitable location elsewhere, such as the talk page of the relevant article or project.
  • Respect other editors. Another user wrote the text you want changed, or reported an issue they see in something you wrote. Everyone's goal should be producing the best Main Page possible. The compressed time frame of the Main Page means sometimes action must be taken before there has been time for everyone to comment. Be civil to fellow users.
  • Reports are removed when resolved. Once an error has been addressed, determined not to be an error, or the item has rotated off the Main Page, the report will be removed from this page. Check the revision history for a record of any discussion or action taken; no archives are kept.

Errors in the summary of the featured article

Please do not remove this invisible timestamp. See WT:ERRORS and WP:SUBSCRIBE. - Dank (push to talk) 01:24, 29 September 2022 (UTC)[reply]

Today's FA

Tomorrow's FA

Day-after-tomorrow's FA

Errors with "In the news"

  • More a social error than anything factual or technical, but I think it's time to picture Hossein Amir-Abdollahian. The president presides, so should have gone first, but the foreign minister is at least the secondmost famous (to "global" audiences). InedibleHulk (talk) 10:20, 24 May 2024 (UTC)[reply]

Errors in "Did you know ..."

Current DYK


  • ... that the chief editor of the United States' Telegraph allegedly gouged a rival reporter's eyes inside a Senate office?

DYK hooks are supposed to report definite facts but the weasel word "allegedly" tells us that this is not definite. The allegation was made by the rival whose article says "The Intelligencer reported that Green viciously assaulted Sparhawk, while the Telegraph insisted that any physical altercation was minor and that Sparhawk has barely been hurt." It doesn't appear that any serious injury was done, the complaint was not upheld and so the sensational talk of eye-gouging appears to be improper and unbalanced. Andrew🐉(talk) 07:46, 24 May 2024 (UTC)[reply]

MOS:ALLEGED says: ...although alleged and accused are appropriate when wrongdoing is asserted but undetermined, such as with people awaiting or undergoing a criminal trial; when these are used, ensure that the source of the accusation is clear. The page could be updated to state the source of the allegation. Otherwise, I see this as more of a problem if it was WP:RSBREAKING than for something in the 1800s thats still (presumably) being described as alleged by a modern source.—Bagumba (talk) 09:41, 24 May 2024 (UTC)[reply]


This stat comes from a single porn site which is neither a reliable source nor an adequate survey of the entire globe. This is tabloid trash. Andrew🐉(talk) 07:55, 24 May 2024 (UTC)[reply]

  • The stat is related specifically to searches on Pornhub, so I have added that qualifier to the hook, otherwise it's simply inaccurate. I'm not too bothered about the whole subject though, Vice is listed as no consensus at WP:RSP, so it's not automatically barred, and I would assume the stat originates from Pornhub itself... (although quite how they would know whether someone searching their site is a woman or a man is another matter). I'd think this meets WP:V and is interesting enough so I'm inclined to leave as is.  — Amakuru (talk) 08:54, 24 May 2024 (UTC)[reply]
    I also updated the page to make it clear that Pornhub is also the source of the stat, not some independent source. As for the hook, DYK doesnt seem to consistently provide inline attribution, so I'll leave it to others to determine if that is an issue for this hook. —Bagumba (talk) 09:24, 24 May 2024 (UTC)[reply]
    What would Heinrich Böll say? -- Sca (talk) 12:54, 24 May 2024 (UTC)[reply]
    I always use my weekend alias "Penny" when I search for clown porn... Martinevans123 (talk) 13:16, 24 May 2024 (UTC)[reply]


Noting I have tagged Axel Downard-Wilke for undisclosed COI editing, for reasons explained at WP:Conflict of interest/Noticeboard#Axel Downard-Wilke. – Teratix 08:32, 24 May 2024 (UTC)[reply]

It appears there was Wikipedia:Articles for deletion/Axel Downard-Wilke, which was closed per speedy keep #6 for being linked on the MP. SK6 says:

If the problem is urgent, consensus should be gained at WP:ERRORS to remove the link before nominating for deletion.

Bagumba (talk) 09:13, 24 May 2024 (UTC)[reply]
minus Pulled. Given that the article is now Orange-tagged (which is not permitted for DYK content), and also the fact that we take WP:COI cases seriously, I have removed this hook from DYK for the time being, and replaced with an alternative picture hook and also added in an old hook from last year for main page balance.
Obviously there hasn't been a lot of discussion here or at WP:COIN so far, so perhaps consensus might later emerge that the hook is OK, but I'm acting on the precautionary principle here. If there's later a consensus to reinstate Downard-Wilke's hook then I've listed the image at Commons auto-protection so it could go straight up without needing re-protection.  — Amakuru (talk) 09:55, 24 May 2024 (UTC)[reply]
Also notifying @Marshelec, Xoak, PrimalMustelid, and Premeditated Chaos: who were involved with this hook, FYI. Sorry should have done this earlier.  — Amakuru (talk) 12:35, 24 May 2024 (UTC)[reply]
@Amakuru, When I approved the hook, there were no COI concerns raised. I remember noticing a COI disclosure on the talk page, but now I realize it was from the subject themselves (Mr. Wilke), who had nothing to do it either the DYK or the article. Good thing you did there, pulling it out from the main page. Prompt action. Now that we're past that, we may participate on the COIN discussion. X (talk) 13:21, 24 May 2024 (UTC)[reply]

Next DYK

Next-but-one DYK

Errors in "On this day"

Today's OTD

Tomorrow's OTD

Day-after-tomorrow's OTD

Errors in the summary of the featured list

Friday's FL

(May 24, today)

Monday's FL

(May 27)

Errors in the summary of the featured picture

Today's POTD

Tomorrow's POTD

General discussion

Dark mode is coming!

If you haven't seen the news, natively-supported dark mode is coming. I think if you want to try it without opting in etc. this is a link you can try (it worked for me in private mode of Firefox).

This means the main page needs some styles. Previously it was basically how any old page in the main space looks (e.g. Facebook: just a black background and borders). I took an hour or two to give it a color theme reminiscent of light mode with some use of this web theme maker (I got the "value" for the light mode colors in the spectrum, then flipped them relative to 1000) and then made a single tweak (the purple used for TFP). Wikipedia:Main Page/styles.css has the colors (which are duplicated for the "OS" selection) if you want a readable summary.

Visited links are not necessarily accessible currently, but they aren't accessible on the current dark mode either (contrast of 3.5), so I don't think it's worth spending a ton of time on that.

If anyone thinks things aren't ideal (and I suspect they aren't), feel free to nudge things in the relevant style sheet with an admin request (who has to nudge them twice). Ignoring the link accessibility, I think right now the border for section headers on the blue side and TFP aren't great, and the TFP header background is too bright. Also, bullets aren't visible but that's going to be fixed in the next deployment. Izno (talk) 23:49, 19 May 2024 (UTC)[reply]

One of the tools that's essential for my main page work is User:Anomie/linkclassifier.js (documentation) and it's important that with coloured backgrounds, this still works. Schwede66 00:43, 20 May 2024 (UTC)[reply]
Not directly relevant to this section, but if you want to ensure that looks some reasonable way, you should discuss with Anomie. All the link colors are the default here. Izno (talk) 01:03, 20 May 2024 (UTC)[reply]
Finally. MJGTMKME123 (talk) 14:03, 20 May 2024 (UTC)[reply]
I'm not a fan of the literal SEAOFBLUE on the right side, maybe the colors need to be a bit muted (especially for the background)? Sohom (talk) 17:28, 20 May 2024 (UTC)[reply]
Happy to implement suggestions. I thought it was good enough. Izno (talk) 20:09, 20 May 2024 (UTC)[reply]
@Izno I've created a alternate colorscheme (it's effectively the same colors, but very very muted) at Template:TemplateStyles sandbox/Sohom Datta/styles.css, let me know if that works. Sohom (talk) 21:02, 20 May 2024 (UTC)[reply]
The homepage updates look like they're coming along really well. It's great to see all those bright white outlines gone. If it would be helpful, I could help out with a design and send the spec to you for implementation. :-) JScherer-WMF (talk) 02:04, 22 May 2024 (UTC)[reply]
I think it would be helpful. Our current "featured list pink" is uh... iiiinteresting. Snowmanonahoe (talk · contribs · typos) 02:49, 22 May 2024 (UTC)[reply]
Ok! I'd love to help. I filed a ticket on the web backlog to continue the discussion about design specifics so as to not clutter this space. I'd love to hear more about folks' goals for a design—a design brief, essentially. Thanks! JScherer-WMF (talk) 15:24, 22 May 2024 (UTC)[reply]
Picture of how the page should look

Per above. Please replace the contents of WP:Main Page/styles.css with Template:TemplateStyles sandbox/Sohom Datta/styles.css. Thanks. Sohom (talk) 23:20, 20 May 2024 (UTC)[reply]

Did this a couple hours ago. Izno (talk) 23:24, 20 May 2024 (UTC)[reply]
Ah shoot, looks like I did not WP:BYPASS :( Sohom (talk) 23:25, 20 May 2024 (UTC)[reply]
Will this dark mode work in Monobook, or is it only for Vector? Modest Genius talk 14:19, 22 May 2024 (UTC)[reply]
Only Vector and Minerva (the mobile skin). Snowmanonahoe (talk · contribs · typos) 14:20, 22 May 2024 (UTC)[reply]
Only Vector22 right? Is is supposed to come to Vector legacy? Sohom (talk) 14:38, 22 May 2024 (UTC)[reply]
Only Vector 2022. Izno (talk) 21:27, 22 May 2024 (UTC)[reply]

Changing the 'Did you know...' section title

I have notice that in the did you know section all bullet points start with '...that', and I personally think that the 'that should be moved to the section title, making the title 'Did you know that...' and remove the 'that's from the bullet points, streamlining the page by a slight bit and making things a tad bit less redundant. Gantnitsa (talk) 16:34, 20 May 2024 (UTC)[reply]

Maybe, but first of all, four-letter abbreviations which lack the potential to double as easy-to-pronounce acronyms are awkward at best. There's also the issue of the need for consensus-building as to how to handle it in the uncommon-but-far-from-unheard-of cases in which "that" would be less than ideal to serve as the otherwise-initial word of a hook. Again, while admittedly uncommon, it hardly seems unlikely to an extent in which consensus-building would be best addressed on a case-by-case basis. This proposal seems like a creepy, albeit well-intentioned solution in search of a problem. Joefromrandb (talk) 21:07, 20 May 2024 (UTC)[reply]
This is something to discuss at Wikipedia talk:Did you know. Snowmanonahoe (talk · contribs · typos) 23:39, 20 May 2024 (UTC)[reply]
See this discussion in August 2020, which produced some consensus against this very proposal. — RAVENPVFF · talk · 15:18, 23 May 2024 (UTC)[reply]

header broken in monobook

2024-05-23 problems

Haven't been able to check this yet, possible WP:THURSDAY issue? In monobook, the page layout is broken now, see example - with the "welcome to wikipedia" being moved, a "," on a line by itself, bad font/size as well. — xaosflux Talk 09:34, 23 May 2024 (UTC)[reply]

@Izno: just in case you are working on this via Wikipedia:Main Page/styles.css. — xaosflux Talk 09:35, 23 May 2024 (UTC)[reply]
Fixed the comma break by moving the comma in to the h1 element; not seeing that causing breaks on vector or vector22. The h1 styling here seem to be the primary problem now. — xaosflux Talk 09:44, 23 May 2024 (UTC)[reply]
Seems to be styles associated with the mw-heading1 div around that h1.. — xaosflux Talk 10:11, 23 May 2024 (UTC)[reply]
I'm seeing the same issue - it looks very ugly. Thanks for looking into this! Modest Genius talk 11:15, 23 May 2024 (UTC)[reply]
The gap between Welcome to Wikipedia and "the free encyclopedia that anyone can edit." is too big on Monobook. The line at the top cuts off the bottom of the P. I suggest you do "Welcome to" in smaller letters at the top and then just Wikipedia in large. "Welcome" looks a bit silly being that big.♦ Dr. Blofeld 11:23, 23 May 2024 (UTC)[reply]
  • Getting these reset may be enough: #mw-heading1
border-bottom: none;
margin-bottom: none;
font-size: 100%;
xaosflux Talk 12:02, 23 May 2024 (UTC)[reply]
 Doing... font size fix first, waiting for sync. — xaosflux Talk 12:30, 23 May 2024 (UTC)[reply]
 Done font size fixed in MediaWiki:Monobook.css; margin/border to do. — xaosflux Talk 12:36, 23 May 2024 (UTC)[reply]
 Doing... border/margin - waiting for sync. — xaosflux Talk 13:24, 23 May 2024 (UTC)[reply]
 Done I'm not sure I love these CSS hacks though. Suggestions for improvement (here or upstream) are more than welcome. — xaosflux Talk 13:28, 23 May 2024 (UTC)[reply]
Specifically I'm not liking that the parser is building the ID from the content and including "," in the element id now. (That is the one thing that will affect all skins). — xaosflux Talk 13:31, 23 May 2024 (UTC)[reply]
Xaosflux Fixing this in Monobook.css was not appropriate (fixing it in WP:Main Page/styles.css is sufficient), nor was I believe moving the comma necessary. The relevant change is phab:T363597. It will be coming to the other skins Soon so we will need to fix it for all skins. Please remove the Monobook.css styles and revert your main page change so we can fix this correctly. Monobook being broken for a day or two is not a reason to... hack. Izno (talk) 16:44, 23 May 2024 (UTC)[reply]
@Izno looks like phab:T363597 is going to be 2 weeks out? Do you have a fix for /styles.css ready to go, in which case certainly we can pull this out of monobook.css. Also, do you know what the "breaking" change # is for reference? — xaosflux Talk 17:23, 23 May 2024 (UTC)[reply]
I do not have such a change. I'm not going to work on it until you revert yourself. It's a pain to sort things out when you're starting from the wrong state. Izno (talk) 17:29, 23 May 2024 (UTC)[reply]
And no, it is definitely live in Monobook. Izno (talk) 17:30, 23 May 2024 (UTC)[reply]
@Izno OK, I've restored the broken version - we certainly shouldn't leave this broken for weeks though. — xaosflux Talk 17:32, 23 May 2024 (UTC)[reply]
I will take care of it today. :) Izno (talk) 17:34, 23 May 2024 (UTC)[reply]
Thanks! Semantically, not sure about that comma - it is floating between the header and the end of a div that encompasses the header - certainly not a big deal other than the header handling breaking it there. — xaosflux Talk 17:37, 23 May 2024 (UTC)[reply]
This is fixed. Padding/margin between the top of the box and the welcome line looks off so that needs some investigation. I'll take a look later to see if that's just my imagination.
The comma is outside for the same reason you felt gross about it being on the inside earlier, except it matters for screen readers. IDK how the comma inside would even sound but it would probably be awkward. Izno (talk) 17:40, 23 May 2024 (UTC)[reply]