Wikipedia talk:Talk page guidelines/Archive 15

How best to make it clear when a Collapse is not intended to end a discussion.
Thank you to Thinker78 for reverting my edit at WP:TALKOFFTOPIC. Why am I thanking a reverter? Because the revert shows that my edit could be read to have the opposite effect of what I intended. The revert leaves open the question of how to phrase offers a way for editors to make it clear when a Collapse is not intended to end a discussion. Any suggestions before I give it another try? Butwhatdoiknow (talk) 02:07, 9 August 2021 (UTC)
 * Typically when someone collapses a section of text, they include a short description explaining the rationale, which clarifies the intended paths for future discussion. Thus personally I haven't seen any issues of this nature. Do you have some specific examples in mind? isaacl (talk) 05:44, 9 August 2021 (UTC)
 * An example: a Collapse with the description of "Refactoring discussion" met with a revert supported by the comment that "once a portion has been collapsed, no new edits (including additional replies) should be added to it any more." A solution: what I have in mind is text that incorporates your understanding ("Typically when someone collapses a section of text, they include a short description explaining the rationale, which clarifies the intended paths for future discussion."). Butwhatdoiknow (talk) 16:39, 9 August 2021 (UTC)
 * As I understand it, [//en.wikipedia.org/w/index.php?title=Wikipedia_talk:Red_link&diff=1010260850&oldid=1010214233 your edit introduced the collapsed text], with the edit comment "Collapse off topic discussion", which is an indication that the discussion within the collapsed portion has concluded. Thus your [//en.wikipedia.org/w/index.php?title=Wikipedia_talk:Red_link&diff=1010263127&oldid=1010260850 subsequent edit] that added text to the collapsed portion was indeed counter to convention. Active discussion invariably occurs in uncollapsed text. The only situations I can think of where collapsed text is updated is when some working info has been collapsed for convenience, such as collected links, statistics, or some other verbose data. This is generally accompanied with a description indicating that the data is being updated. isaacl (talk) 22:28, 9 August 2021 (UTC)
 * WP:TALKOFFTOPIC does not say: (a) a "Collapse off topic discussion" edit summary indicates the collapsed off-topic discussion has concluded, (b) active off-topic discussion invariably occurs in uncollapsed text, (c) the only exception to that rule is adding to off-topic working info, or (d) the edit summary for an addition to collapsed pff-topic working info should indicate that the data is being updated. And with regard to practice, at least one other editor (Thinker78) thinks a Collapse of an off-topic discussion does not indicate an ed of discussion.
 * I propose that we recommend to editors that they make it clear in the title of a Collapse of an off-topic discussion when they do not intend the collapse to end the discussion. Butwhatdoiknow (talk) 05:46, 11 August 2021 (UTC)
 * Other editors are welcome to join in discussion to say if they think active discussions should take place within a collapsed section of text. As I said, my experience is that users don't expect to have to open up collapsed sections of text to check if new comments have been made within them. When a digression occurs within a discussion thread and users want to pursue it without interfering with the flow of the original conversation, a new thread is started on that topic, keeping all comments visible without additional effort. isaacl (talk) 06:12, 11 August 2021 (UTC)
 * As I said, WP:TALKOFFTOPIC does not say that (a) active discussions should not take place within a collapsed section or (b) when a digression occurs within a discussion thread and users want to pursue it without interfering with the flow of the original conversation, a new thread is started on that topic. Butwhatdoiknow (talk) 18:44, 11 August 2021 (UTC)
 * I think collapsed text should be treated like any other edit, unless it is placed by an administrator. It should be clear to readers and editors that the collapse can be reverted if not placed by an administrator. I have seen cases of it being used by biased editors who simply don't agree with some personal opinion of a new editor who otherwise made a legitimate comment according to Wikipedia standards. Then some editors who have the potential to get engaged in helping in the project, just leave disenchanted due to perceived censorship in Wikipedia. --Thinker78 (talk) 17:52, 13 August 2021 (UTC)
 * I agree with the general point - I have a few times seen editors collapse things as a means to get their own way without proper discussion - but we need to add a proviso. Such an edit should only not be subject to reversion if it is performed by an administrator as a clearly administrative action. Admins are, for much of the time, mere mortals like you and me who do not have any extra privileges. Phil Bridger (talk) 19:25, 13 August 2021 (UTC)
 * Because WP:TALKOFFTOPIC says continuing an off-topic discussion in a Collapse is not the "normal" practice, I am proposing we say that editors should make it clear in the title of a Collapse of an off-topic discussion when they do not intend the Collapse to end the off-topic discussion. Do you object to that instruction? If so, why? Butwhatdoiknow (talk) 18:44, 11 August 2021 (UTC)
 * There are decreasing returns in benefit with adding more words to any guidance. I've not seen any issues requiring additional written guidance along the lines you suggest. isaacl (talk) 19:20, 11 August 2021 (UTC)
 * Well, you've seen my issue (above). But I concede that if the community doesn't report other instances then perhaps my proposal would be wp:CREEP. Butwhatdoiknow (talk) 20:13, 11 August 2021 (UTC)
 * The format of a discussion is subject to consensus agreement of the participants, as with most things on English Wikipedia. There wasn't agreement in your example to have ongoing discussion in a collapsed section of text, so it doesn't support a need for additional written guidance. isaacl (talk) 21:10, 11 August 2021 (UTC)
 * For the record, the reason there wasn't agreement was because the editor who un-Collapsed believed there was a rule that "once a portion has been collapsed, no new edits (including additional replies) should be added to it any more." Perhaps the outcome would have been different had WP:TALKOFFTOPIC made it clear that there is no such rule. Butwhatdoiknow (talk) 22:12, 11 August 2021 (UTC)
 * The editor was describing community practice, which is accurately referred to in this guidance page. No indication was given that this page was the reason, as you put it, to disagree with continuing an active discussion in a collapsed section of text. To wit, it's because that's the community expectation that this page has that guidance. isaacl (talk) 22:25, 11 August 2021 (UTC)
 * You want an indication? I offer this quote from the editor describing my conduct as "disruptive, or at least not in accordance with WP:TPG." No mention of community expectations. Butwhatdoiknow (talk) 00:01, 12 August 2021 (UTC)

I have just put back into the page (11:55, 26 October 2021‎) a probibition that prevents an involved editor closing down a discussion on a talk page by using one of the collapse templates. The prohibtion states "."

I think it needs to be there so if someone wants to explain how such templates ought to be used can by linking to WP:TALKOFFTOPIC or WP:COLLAPSENO showing that if they object to the refatoring done by collapse, then it should be reverted (as refactoring states "". It is really dumb to start an edit war on the talk page, and to prevent one the status quo ante should always be the default—unless another guideline overrules it.

So if someone wishes to collapse part of a thread (although, I find it difficult to understand when that would be desirable, because it is usually done with a sub-heading), it can be done, but if someone objects the refactoring ought to be rewound. So I do not think any additional wording needs to be added to the bullet point covering this very unusual use of the collape templates on talk pages. Covering every possibility in the guidlines would bloat them to the point that they were contradictory and probably unreadable. -- PBS (talk) 12:30, 26 October 2021 (UTC)

Why spacing is needed, in non-bullet same-indenting posts of different editors
If one doesn't create a spacing between one's post & the preceding post, when they're both indented the same & not bullet pointed? Confusing will occur, with two posts appearing as one post. GoodDay (talk) 05:13, 9 December 2021 (UTC)
 * There is a space between adjacent unbulleted list items. For example, there is a space between this comment and
 * This following comment. isaacl (talk) 05:49, 9 December 2021 (UTC)
 * I've seen posts mixed together by different editors in discussions, due to not spacing, when they're responding to the same editor (thus requiring identical indenting). GoodDay (talk) 06:18, 9 December 2021 (UTC)
 * Some example markup would help better illustrate the issue. isaacl (talk) 15:06, 9 December 2021 (UTC)
 * Such issues are the result of using software that is not designed for discussions for that purpose. We end up with lists all over the place where screen readers do not do the same job as visual browsers in clarifying who said what to whom. This has long been recognised as a problem on Wikipedia. Surely there is some free forum software out there that would support, maybe via an extension, copying Mediawiki markup into posts? I understand that that has been the stumbling block with previous attempt at fixing this. Phil Bridger (talk) 15:16, 9 December 2021 (UTC)

Listing of a aboriginal group with the wrong location
I was reading a article that had wrong regions for an aboriginal group. Métis. The Métis are from the prairies. There is no Metis from Atlantic Canada. This article is misleading and disrespectful to the Métis people as the Métis Nation and homeland is very well defined and legally accept by the Canadian government. Also there are many false groups pretending to be Métis and this article promotes cultural appropriation and false ideas of who they are as a distinct aboriginal group your help with remediation of this article would be much appreciated and expected from a organization of such influence. Thanks. A member of the Métis Nation 2001:569:5269:900:39DE:DB24:A853:2B5E (talk) 02:10, 23 December 2021 (UTC)


 * Welcome to Wikipedia! The talk page for the Métis article may be the best place to discuss these issues. ClaudineChionh (talk – contribs) 05:51, 23 December 2021 (UTC)

Can you add a new rule about copyright image posting policy in the talk pages?
To the wikipedia staff and users.

Can I ask you to add a new rule regarding the copyright images on talk pages? I need to see the rule regarding posting images copyright or my own drawings or photos I've taken on the talk pages. I got into trouble earlier in 2021 for blindly posting copyright images in the talk pages and I have since reframed from doing it anymore, because I don't want to get banned on Wikipedia. I want to be able to help out on Wikipedia talk pages and be respectful.

Also, am I allowed to post my own drawings in my personal talk page as long as I keep it appropriate on being rated G?

And I'll work on trying to keep my talk pages on topic. I'm not perfect, I'm autistic and I make mistakes and I'll try not to make any more mistakes with being off topic in the talk pages. CrosswalkX (talk) 17:02, 9 January 2022 (UTC)


 * It is WP:NFC. Non-free images can only be used in mainspace articles. --M asem (t) 17:07, 9 January 2022 (UTC)
 * As regards your own drawings or photos you have taken yourself, you own the copyright, so you can simply release them under a free licence (the upload feature should tell you how) and there will be no copyright problem with using them anywhere on Wikipedia. The only problems you could have using them is if they are totally irrelevant to the discussion, but that is not a copyright issue. Phil Bridger (talk) 17:35, 9 January 2022 (UTC)

Red link for the current section template
Hello! SO while looking through this, I noticed that where it mentions WP:CURRENTSECTION, the template results in a red link. Is this on purpose or is this something that's no longer used? ― Blaze WolfTalkBlaze Wolf#6545 20:09, 14 January 2022 (UTC)

Critical race theory
Could you please elaborate on the theory of critical race as it applies to the study of American History, which has always been one of many subjects taught as required study for each and every school from Elementary to High? Specifically, what has caused a line to be drawn in the teaching of racial inequality that is part of the framework of America's identity? I'm sensing a bit of political rhetoric instead of factual discourse. Wikipedia Slavery in the United States — Preceding unsigned comment added by 2601:4A:C801:1890:84D7:3AA6:704B:1C2F (talk) 05:29, 11 February 2022 (UTC)
 * Welcome to Wikipedia! The talk page for the critical race theory article may be the best place to discuss these issues. Butwhatdoiknow (talk) 15:53, 11 February 2022 (UTC)

Untitled discussions
Hello, I have a question about article talk pages. This guide, especially when used with WP:ARCHIVE, can be very helpful for editing and archiving talk pages, but nowhere in either guide, nor in the talk page archives of these guides, to what I can find, has the answer I'm looking for. When inspecting a talk page, I've noticed some discussions, especially very old ones, have been posted without a section header simply as plain text below the talk page's banners. While this guide deals with the subject of editing other users' talk page discussion headers as a way to section off, remove duplicates, or clarify, I cannot find a definitive answer for what to do when it comes to discussions without any header whatsoever. I have considered using a plain "Untitled" as the unnamed section's title when editing/archiving article talk, but I don't know if the community has a more preferred approach. So my question would be, what should I do in this scenario? Thanks. — Paper Luigi  T • C 23:03, 3 February 2022 (UTC)
 * One approach is to do nothing if there is no actual problem. However, if the month/year is readily known (for example, if the old discussion has a working signature), inserting == Month Year == is a good approach. Or, if there is a bunch of old stuff, one == Old discussions == before all of it is fine. Johnuniq (talk) 00:46, 4 February 2022 (UTC)
 * Thank you for your reply. Yes, I have considered doing nothing, but this approach leaves me questioning whether talk discussions without headers should take precedence over other talk page discussions in the talkpages or their archives. Now, personally, I don't see anything wrong with adding month/year dates if the signature of the original poster includes that info. That approach is fine with me. Up until now, before I asked the question, all I have done is add "Untitled" as the default talk page discussion thread title (in the sense of MS Paint's or Notepad's default titles). Usually there is no actual problem because the users from 10, 15, or even 20 years ago have long since gone elsewhere, and those are the ones usually in question when this subject arises. I'm sure the original persons have long forgotten their conversations at the length of a decade or more. I was just making sure I wasn't overstepping my boundaries as a non-involved-with-the-discussion Wikipedian by changing/archiving these persons' discussions with an "Untitled" or date approach. —  Paper Luigi  T • C 01:06, 4 February 2022 (UTC)
 * I assume you're only changing before archiving. I guess that this is covered by Fixing layout errors: "... adding a heading to a comment not having one ...", and WP:SHOWN: "... It is generally acceptable to change headings when a better heading is appropriate, ...". assuming something is better than nothing. But you'd have to be awfully certain that a comment isn't really intended to be part of a previous section, and adding "Unittled" could be non-unique and "not specific as to the article topic discussed", so it seems like a lot of thankless trouble. Peter Gulutzan (talk) 15:15, 4 February 2022 (UTC)

Just about the only problem with "untitled" talk comments is the same as for unsigned talk comments - automatic archiving fails. I would not mind if our guidelines tell editors what to do here. Please note: I would much prefer a guideline that offers a standard way to format the talk page correctly (so the bot will properly archive some time in the future) rather than, say, manually archiving. CapnZapp (talk) 08:20, 14 February 2022 (UTC)
 * Yes, changing before archiving was what originally brought me here, but I also feel like these types of discussions without titles should be separated with a header even when they remain on the main article talk. I have seen these discussions grouped under the "Untitled" header a time or two in the past and was curious if this format was standardized or more loosely utilized. I agree that the MOS could benefit by including guidelines for what to do with this type of discussion. The lack of such guidelines is what brought me here. IMO, the MOS should be amended to include a standard procedure for dealing with untitled discussions, including a suggested title format for consistency.  —  Paper Luigi  T • C 03:34, 22 February 2022 (UTC)
 * Maybe I'm repeating myself, but presence of an "unheaded" section (i.e. no section at all) is not in itself a problem in my opinion. Doesn't MOS already contain general guidelines on how to format talk pages? The problem is if it won't autoarchive. I think the MOS should offer a suggestion on how to ensure proper autoarchiving even when posts are added by editors that forget headers and/or signatures (even if the page is not currently set up for autoarchiving, it might in the future). These instructions can be minimal as long as autoarchiving starts working again. CapnZapp (talk) 09:43, 22 February 2022 (UTC)

Dairy of a Wimpy kid ( Old School )
September

Saturday — Preceding unsigned comment added by 62.68.231.197 (talk) 09:57, 7 March 2022 (UTC)


 * Not sure what you are trying to say. If it relates to Diary of a Wimpy Kid then you should post it here: Talk:Diary of a Wimpy Kid. Also, you should provide more of an explanation than "September Saturday." Butwhatdoiknow (talk) 15:32, 7 March 2022 (UTC)

Peer review for Iulia&Delia Zanoschi page
I would like a review before publishing the sandbox page. I have checked with similar pages, have provided citations and data, but i am unsure if this is sufficient. The page is https://en.wikipedia.org/wiki/User:Wackwagon/sandbox I have had multiple people look through it and some have added  comments incorporated in already Wackwagon (talk) 06:14, 18 April 2022 (UTC)
 * I've added a template to you draft that has a link to request a review. I'm not sure how to access that process without the template. Perhaps another editor can educate us both about that. - Butwhatdoiknow (talk) 16:53, 20 April 2022 (UTC)

Can the protection be increased?
I'm a new wikipedia editor. I don't know a lot about wikipedia editing, I regularly break wikipedia guidelines without knowing (though I do my research), but I do know that this page is easy for newbies like me to unintentionally "vandalise" by changing the contents into untruths without knowing. Could the semi-protection be switched to extended confirmed protection? If not, please give a comprehensive explanation for why not. BragmArcus (talk) 09:27, 23 February 2022 (UTC)
 * I forgot to mention how I can change other people's comments. BragmArcus (talk) 09:35, February 23, 2022
 * Can you give an example of "changing the contents into untruths without knowing"? Butwhatdoiknow (talk) 16:58, 23 February 2022 (UTC)

I believe the OP is seeing how easy it would be to change the comments of other editors. I furthermore believe it is incredibly easy for us experienced Wikipedians to forget how much we rely on Wikipedia's (very robust) version management system (=page histories), that basically means that any bad-faith attempt to put words in the mouths of others will be caught. To the OP: it just isn't a problem. I know it can seem like it must be, but it really isn't. This explains why page protection is relatively rare. Cheers CapnZapp (talk) 11:35, 14 May 2022 (UTC)

WP:ENGLISHPLEASE
After a discussion where a user approached Wikipedia with the expectation that linking to foreign-language information is alright; my best summary of his reasoning is: since Chrome comes with built-in translation tools people will have no problem reading a machine-translated version of the linked page.

First off: I am assuming this reasoning does not fly here at English Wikipedia. If you want something to be read and analyzed, say it in English. Or provide your own translation; which again means you are saying it in English. Assuming this is consensus, I have boldly edited the WP:ENGLISHPLEASE paragraph to clarify that, no, it is not reasonable to expect readers of English Wikipedia to translate content themselves. Either you translate it, or you don't expect people to read it.

I am open to other phrasings and overall discussion. Cheerio CapnZapp (talk) 09:35, 13 February 2022 (UTC)
 * The existing If using another language is unavoidable, try to provide a translation, or get help at Embassy seemed sufficient (if not also diplomatic).—Bagumba (talk) 12:55, 13 February 2022 (UTC)
 * Linking to non-English sources is absolutely allowed. We write in English, but we cite sources in any language. Providing a translation is an encouraged courtesy, but not a requirement (except when quoting the source… then we give both). Blueboar (talk) 13:17, 13 February 2022 (UTC)
 * WP:ENGLISHPLEASE is limited to talk page behavior. Not what will "fly here at English Wikipedia" generally. Perhaps try Verifiability for that. Butwhatdoiknow (talk) 23:01, 13 February 2022 (UTC)
 * To avoid misunderstandings, User:Blueboar and User:Butwhatdoiknow: I am talking about talk page discussions - perhaps I could have been more clear on that. Furthermore, I do not mind links to content written in other languages. However, my concern is when an editor includes such content (or links to it) and expects the readership to read that content and take it into consideration for the discussion at hand. I wanted our ENGLISHPLEASE policy to be more clear: if you wish people to take your information and arguments into account, you need to inform and argue in English . You cannot expect people involved in a talk discussion to translate the stuff you supply - not even in an age where some browsers have machine-translation built-in. tl;dr: If you want people to listen, you need to supply the translation yourself. Hope that clarifies my aim for this talk section. Regards CapnZapp (talk) 08:14, 14 February 2022 (UTC)
 * How curious! You had strenuously expressed your objections to my link to nl:Wikipedia:De kroeg/Archief/20200709, on the grounds that English is strongly preferred in such discussions ... while repeatedly making the point that your reminders were just intended to be helpful, because many people might ignore such non-English content. Did I mention that you repeatedly made that point?
 * To be clear, I am not bothered if some people choose to ignore my arguments. People will ignore arguments simply because they're unsympathetic to them, they are absolutely free to whine about the language (though it seems like you were the only one helpfully complaining about it).
 * Now I notice you have modified ENGLISHPLEASE to state "Do not expect readers to translate your content themselves, not even when modern browsers have machine translation built-in." So you seem to be taking the position that one should avoid linking to foreign-language content (rather than to a translation) while trying to imply that guidance also applies to linked content (which is in fact disputed). Fabrickator (talk) 10:52, 14 May 2022 (UTC)
 * It appears that - even though I have certainly done my best to clarify - my position still remains unclear to you. Let me try one more time, somewhat differently. Do I object to your foreign-language links? No. Do I think you are breaking any rule or policy? No. Do I want to stop you or sanction you in any way? No.
 * What then? I am trying to give you information, and persuade you it is in your interest to really listen. Please do not rely on arguments presented in foreign languages. This is the English Wikipedia - do not expect readers to make an effort (any effort, really) to take in arguments not stated in English. In fact, I believe editors are well within their rights to simply bypass/ignore such arguments much like if they were not made in the first place.
 * I *am* trying to be helpful. I am not stopping you from adding these links; I am trying to make you realize you can't rely on them. That's not the same as saying there's anything wrong with them. As additional information, or deeper background info for the interested, I'm sure they're great. An editor that really wants to know more will make the effort to cross the language barrier. But that's not the case here. You didn't offer up links as additional info for the curious, you added it support your arguments, implicitly expecting editors to cross the language barrier. (Full disclosure: I honestly don't remember the specifics of the above discussion any longer).
 * Please accept that English Wikipedia editors can be very "provincial"; if you talk to them in other languages, you might be wasting your time. I have been open with my efforts to clarify the relevant policy. I am not doing so to spite you. I am doing so in a genuine effort to help future editors that might - like you - come here with the assumption arguments made in Dutch carry the same weight as arguments stated in English. Since in my experience that just isn't true, I wanted the policy to make that more clear. I did not intend any CHANGE in policy, just to clarify what (I believe) is already common practice. The change went through with no objections; which I take to confirm that I am not an outlier; I really am giving you advice consistent with consensus.
 * I can certainly agree perhaps a more precise phrasing would be "Do not rely on readers to translate your content themselves..." making it (even more) clear nothing is forbidden (or even discouraged) here.
 * Have a nice day CapnZapp (talk) 11:32, 14 May 2022 (UTC)
 * You wrote: "You didn't offer up links as additional info for the curious, you added it support your arguments, implicitly expecting editors to cross the language barrier." Hmmmmm, actually, I just pointed out that there was an extensive discussion elsewhere of the topic under discussion ("links to articles in other languages").  So there it is, for people who are interested in the topic, they can see what's already been said, and either not bother to repeat it, or call out those arguments that they find appealing, and perhaps refine them further that we might improve on them. (In other words, I was not citing any particular arguments from that discussion.)
 * Now rather than reinforcing the idea of taking the time to view those arguments, or even to actually disparage the content of that discussion, you chose this as an opportunity to assert your agenda, which is pretty clearly expressing an opposition to non-English content, no matter how much you claim you were simply trying to be helpful.
 * And of course, that's what you did. Rather than review the discussion to see if it had pertinent content that would be on point with the discussion, you made it all about the fact that not everybody would want to go through the effort of obtaining a translation of that discussion (which would be fine ... the real point was to consider this as additional input, perhaps containing interesting point or points which were better expressed).  But no, every time, it was just an opportunity to express your sense that non-English content is to be disparaged in such discussions, even when it is linked to, rather than quoted inline.  (So presumably according to you, I should have copied over the entire translated content into our discussion, instead of letting interested editors use this as a source of appealing aguments.)  In fact, that discussion could always have been subsequently extended, so it could be quite confusing to have a translated version as of a certain time.  Anyway, the emphasis in ENGLISHPLEASE is certainly on inline foreign language content, if one wanted to incorporate specific content into a discussion, then translation would have been pertinent, but raising the issue of translating content which is linked to is merely an effort to distract from the discussion at hand. Fabrickator (talk) 13:14, 14 May 2022 (UTC)
 * At this time I will simply ask: do you still have any lingering issues with my conduct or can I assume my position is clear to you? It's important to mention you do not need to agree. I'm not trying to change your conduct here, just provide information. I'm not actively opposed to foreign-language arguments. However, I am (or rather, was) concerned about your expectations on them. You are free to argue in any language you like. Just don't say I didn't warn you if you ever get the feeling people ignore you. Regards, CapnZapp (talk) 16:13, 14 May 2022 (UTC)
 * To start with, I have no such expectations. Some people may choose to ignore the foreign-language content, people who find this to be a roadblock are effectively self-filtering... there's no reason to consider this a problem.  However, you continue to miss the point that none of the input you provide is on point, inasmuch as there is no plausible interpretation of accepted guidance which suggests that one is advised to provide a translation of linked content.
 * For that matter, the edit which originally mentioned the need to translate content is from June 2006, actually pre-dating Chrome, and even then, there was no mention that a link to non-English content ought to be accompanied by a link to an English translation of that content, which logically would have been all the more important given the limitations of translation tools of the time.
 * The primary effect of your input is to detract from relevant feedback, while you cover yourself by claiming you're only trying to help improve the conversation.  Any reasonable observer will see that the effect is quite the opposite. Fabrickator (talk) 04:09, 15 May 2022 (UTC)
 * If you want to discuss your opposition to my February edit, please do it below where visibility is greater: . If you want to keep avoiding being thankful for the time and energy I spent helping you become aware that "people have Google translation built into Chrome, I'll simply assume they read my Dutch material" (paraphrased) is an unreasonable assumption, that discussion can still be had here - I doubt anyone else is interested. CapnZapp (talk) 09:57, 15 May 2022 (UTC)

WP:ENGLISHPLEASE 2
Continued from above.

Since a user (Fabrickator) appears to dislike the edit I made back in February, I have started this fresh talk section where arguments can be made. His edit summary was As suggested at Wikipedia_talk:Talk_page_guidelines#WP:ENGLISHPLEASE, the emphasis is unnecessary, resulting in wording that is "less diplomatic" which suggests precvious discussion somehow ended in consensus, which of course is not true. For the record, I find the wording MORE diplomatic, and if I did not think the emphasis to be necessary, I would not have added it. Instead I think this is Fabrickator's attempt to ignore what I believe to be long-standing policy: if you want to argue on English Wikipedia, do it in English. In the earlier talk section, I helpfully point out to Fabricator that the existence of machine translation does not mean (in any way shape or form) that you can expect our editors to digest foreign-language material; which led me to make my February addition that you guys all have found reasonable since the edit has remained stable for three months. But I'll give the scene to Fabrickator now. Best regards CapnZapp (talk) 09:53, 15 May 2022 (UTC)


 * Let's not confuse things. The pre-existing explanation of thisrule had been sufficient for a decade or so. Nobody has endorsed the change CapnZapp made as a brilliant improvement, it is simply additional verbiage.  The desired behavior is that people should provide a translation of content, which is clear enough w  ithout this additional wording.
 * Someone else had made a fair comment about his change. While it's perfectly normal that editors are expected to follow guidelines, it is essentially excessive verbiage to elaborate on the benefits of doing so.
 * In fact, in his comments about my edits, he repeatedly asserted the benefits of my following certain guidelines (specifically, a guideline he extrapolated from this rule, that linked content ought to be translated). In that case, the comment was not justified, and his persistent statements were repetitive ... e.g. he said I ought to include a translation of the linked content, my response being that there's no rule to this effect. To go by his claimed interpretation of the rule, I presume that I would have needed to insert a translation of the extended discussion (a couple of thousand words or so) right into the existing discussion!  Please advise if you think that sounds like a good idea!
 * Rules should not be elaborated on unnecessarily. The benefits of a translation are quite clear without his additional comments. Certainly let's have some discussion and see how many people are willing to provide a glowing endorsement of the advantages of spelling out some guidance that few people would even argue with.  Conciseness is generally a preference, especially when the extra verbiage adds nothing that isn't fairly apparent to begin with. My point will terminate with this: by not presenting a bold case against this, you will be endorsing the idea that every guidance ought to be followed by just a few more words of encouragement about the benefits of abiding by that rule.  Such redundant rationalization of rules would be expanded over the entire set of guidance. Does that sound helpful?  When would it end?  Fabrickator (talk) 17:13, 15 May 2022 (UTC)

Bot notices
I don't see anything regarding bot-notices on here, I sometimes notice that people remove bot-notices on talk pages. I often wonder should people be removing those? Govvy (talk) 23:00, 6 June 2022 (UTC)

Changes to Sasha Roseneil's profile
Can we change her current occupation from 'Executive Dean of Social & Historical Sciences Professor of Interdisciplinary Social Science' to 'Vice Chancellor of the University of Sussex' pease?

Many thanks, Charlie Charlie Littlejones (talk) 09:36, 5 September 2022 (UTC)


 * That is a question to ask on the talk page for her article. Or, perhaps, be wp:BOLD and see whether anyone objects- Butwhatdoiknow (talk) 15:29, 5 September 2022 (UTC)


 * Item 1: The suggestion to make this request on Talk:Sasha Roseneil has not happened.
 * Item 2: The proposed edit to Sasha Roseneil has not happened.
 * Item 3: A plausible source for the (anticipated at the time) change is https://www.sussex.ac.uk/broadcast/read/57215.
 * Item 4: Wikipedia: Gotta love it! Fabrickator (talk) 02:15, 30 October 2022 (UTC)
 * Item 4: Wikipedia: Gotta love it! Fabrickator (talk) 02:15, 30 October 2022 (UTC)

Archive size
WP:TALKCOND states, "archive closed discussions when a talk page exceeds 75 KB". Is this size of the HTML document, Wiki text, prose including all HTML code, or just prose text?--Thinker78 (talk) 17:19, 16 June 2022 (UTC)
 * NewsAndEventsGuy, I just noticed your revert. I did ask before I made the edit as you can see here and no one replied. Can you explain the rationale of your revert more please? Thanks in advance. -- Thinker78   (talk)  16:04, 13 July 2022 (UTC)
 * It's easy to assume everyone is on a highspeed connection but this is a global platform and that just ain't true. Some talk pages are at times graphics intense. In my 10+ years here. this has happened at times in certain science topics. Way back whenever I understood the rule of thumb to be bytes of everything, including imagery. NewsAndEventsGuy (talk) 17:41, 13 July 2022 (UTC)
 * Ok, I was thinking article talk pages where usually there are no images. But user talk pages can indeed have a lot of graphics, more than articles. Thinker78   (talk)  22:49, 13 July 2022 (UTC)
 * NewsAndEventsGuy It looks like the measure is in wikitext, not HTML, according to the Template:Archive request function (not mentioned in the instructions though). I previewed the template in the talk page of Christianity to verify an edit of another editor who was pointing out it was too long. According to the tool Prosesize, the talk page length there is 33kb in wikitext, the same number that the Archive Request template provided. Thinker78  (talk) 16:14, 27 July 2022 (UTC)
 * If the community is happy I'm happy NewsAndEventsGuy (talk) 23:12, 27 July 2022 (UTC)

Should bots be setup to completely blank talk pages when archiving?
I came across this recently at Talk:Ryanair Flight 4978 and it surprised me (so in this case - I changed it). Aside from inconveniently relocating the entire talk history behind an extra click and page load, the perception this may create among new or unseasoned editors might not be helpful. In particular for articles where the same topics may come up in related forms, this practice could be "hiding" useful context in the archives that would otherwise illustrate a topic has recently been addressed.

I'm of the opinion that the talk page is more useful when it always has the most recent discussions at a minimum. I've been here long enough however to assume there's some benefit to the "blanking" practice that I'm not seeing. Can anyone elucidate the reasoning here? --N8wilson 🔔 00:42, 3 September 2022 (UTC)
 * You changed the archiving  from 0 to 6. Zero might be too few but six is definitely too many. However, that is up for debate on each talk page and is not something that needs a centralized discussion. One size does not fit all. Leaving old comments leads to unproductive chatter (WP:NOTFORUM) where people reply to ancient messages thereby hitting other editor's watchlists and prolonging long-forgotten issues. Johnuniq (talk) 00:57, 3 September 2022 (UTC)
 * Regarding the comment above about unproductive chatter, I see WP:NOTFORUM frequently being cited as the basis for discouraging discussion on talk pages, but the major point of the rule is that one should not take discussion into articles. This aspect of the rule would only be violated by the most clueless editors.
 * Admittedly it does also state "article talk pages exist solely to discuss how to improve articles." Is it possible that merely posting this comment is violating that portion of the rule?  I would say "no", because I'm making the point that use of the article talk page is not restricted to discussing specific claims of the article.  Here, I am suggesting that WP:NOTFORUM is frequently cited erroneously, and that some effort ought to be made to avoid confusion on this point, perhaps requiring a change to WP:Talk page guidelines. But has this misinterpretation of the rule become so ingrained that experienced editors will be inclined to deny the rule's plain language? Fabrickator (talk) 05:53, 17 November 2022 (UTC)
 * Although I'm sure this section is abused from time to time, you haven't convinced me that it is, in your words, "frequently" abused. I have an open mind about making tweaks to the section, though.  The trouble is, your comment is just sort of an alleged issue-raising sort of remark.  I've zero notion of exactly how you would change the wording.  You would need to share some draft text to demonstrate.   Finally, we already have the means to deal with abuse of any WP:P&G... see WP:Gaming the system NewsAndEventsGuy (talk) 07:57, 17 November 2022 (UTC)
 * Setting aside whether this happens frequently or not, I have previously encountered objections to discussions on the talk page if they do not state a particular claim and also provide a reliable source for the claim. Here we have a case where WP:NOTFORUM is cited to dismiss certain discussion on the talk page as unproductive chatter.
 * I'm not trying to take a position on what problems leaving old comments on the talk page may cause, just making the point that WP:NOTFORUM isn't particularly specific about the structure of article talk page content, in spite of claims to the contrary that are sometimes made. Fabrickator (talk) 04:02, 19 November 2022 (UTC)
 * Wikipedia works on the I know it when I see it principle, as opposed to a bureaucracy with precise rules that govern (or not) all situations. It is almost always easy to recognize NOTFORUM posts, and seeing that they are unhelpful is similarly easy. Johnuniq (talk) 04:32, 19 November 2022 (UTC)
 * Wikipedia operates on the I know it when I see it principle??? There is always the point at which some kind of personal perspective is all that you have, but if that were the standard, then why bother with having rules requiring "reliable sources" and the like?
 * But my issue isn't with WP:NOTFORUM, it's with editors who cite it to restrict discussion (e.g. on article talk pages) beyond what the policy says. The discussion should pertain to improving the article, but that doesn't necessarily mean that the initial discussion must involve adding a claim and concurrently providing supporting sources, i.e. we might want to gain consensus that some sort of information should be added to the article, with the details dependent on what the sources support.  But I have encountered situations where doing this is claimed to be a violation of WP:NOTFORUM. Fabrickator (talk) 20:43, 19 November 2022 (UTC)

When a comment has no heading?
I recently noticed that there is a comment on Talk:The Great Ray Charles from 2007, which is not under a heading. I don't see anything under WP:TALKHEADING that indicates what should be done in a case like this. Leave it alone, heading-less? Contact the user and say, "hey, could you make a heading for this comment you made?" In the aforementioned case, the user in question hasn't been active since 2011. Make a heading yourself? And if that last option, what should the heading be? — Matthew  - (talk) 05:21, 18 June 2022 (UTC)
 * In a similar circumstance I've taken the "make a heading yourself" approach. Since you're the one doing the fix you can be the one who decides what it says (at least that's what I did in my case). - 06:16, 18 June 2022 (UTC)
 * go for it, and the guidance is found elsewhere in Talk page guidelines at "section headings"... shortcut to that part is WP:SHOWN NewsAndEventsGuy (talk) 11:47, 6 July 2022 (UTC)
 * , WP:SHOWN is about "ownership" of headings.
 * The applicable guidance is three bullets up, at "Fixing layout errors", which lists as appropriate behavior. Paradoctor (talk) 14:22, 4 January 2023 (UTC)
 * A good rule of thumb for stuff like this… go ahead and edit in good faith… 90% of the time no one will object (and they might even thank you)… and for that 10% where someone DOES object, just be friendly and don’t press it. Blueboar (talk) 14:42, 4 January 2023 (UTC)
 * ,, Thank you all for your answers! — Matthew  - (talk) 04:42, 5 January 2023 (UTC)
 * It is unquestionably hilarious to be pinged six months after the fact! Go forth, edit, and sin no more. NewsAndEventsGuy (talk) 04:09, 9 January 2023 (UTC)
 * PS see WP:SOFIXIT NewsAndEventsGuy (talk) 04:10, 9 January 2023 (UTC)
 * The longest gap between edits I've had on Wikipedia was ~17 years. Casting a wider net, I've participated in discussions resumed after a sizable number of years, and more than once. 21st century, baby! ;) Paradoctor (talk) 09:31, 9 January 2023 (UTC)

Superhatting
I have noticed a strange (and concerning) trend lately, usually on politically contentious talk pages. I haven't seen this prior to a few months ago, and it doesn't seem like it has been discussed very often, so I wrote an essay (WP:Superhatting). Essentially, what this consists of is the use of collapse top or hidden archive top to close discussions, with the header text set to be an inflammatory comment on the content of the discussion. Generally, it looks something like this:

What is the deal on this? I've looked through the obvious places (this page, WP:REFACTOR, and the template documentation for hat and cot) and not seen a whole lot about this practice. I am curious whether there are specific policy provisions for using the headers of collapse templates to issue (basically non-respondable) salvos in arguments with people commenting in the section. It seems like an obvious misuse of the templates, and it seems like it may warrant at least a mention somewhere (whether here, in the template documentation, or somewhere else I don't know). jp×g 09:22, 29 January 2023 (UTC)


 * When you say "inflammatory", are we talking about inappropriate closes, or about appropriate closes with an inapproprate title? If the latter, just edit the title. If the former, revert.
 * Either way, the relevant guidance is at and WP:Closing discussions. Paradoctor (talk) 15:33, 29 January 2023 (UTC)
 * Well, what I have seen is stuff like this, where if a comment is removed from a hat, it will lead to a revert war. I think it may be worth putting some note to clarify whether this is acceptable to do. jp×g 10:46, 1 February 2023 (UTC)
 * That was a bad closure, so I removed it.
 * "if a comment is removed from a hat, it will lead to a revert war" Only if at least two editors ignore WP:CONSENSUS. Paradoctor (talk) 11:29, 1 February 2023 (UTC)
 * P.S.: WP:TALKHEADPOV: HTH Paradoctor (talk) 11:51, 1 February 2023 (UTC)

Correcting an editor's typo
The section Editing others' comments says "there is no need to correct others' spelling errors" but does that include (innocently) correcting typos?

— Massmediazealot (talk) 12:06, 4 February 2023 (UTC)


 * Yes. Just leave it. Blueboar (talk) 12:26, 4 February 2023 (UTC)

White space between paragraphs - tech & format stds
The section Technical and format standards advises the following:

"Separate multiple paragraphs with whitespace: If a single post has several points, it makes it clearer to separate them with a paragraph break (i.e. a blank line)."

I have found recently that when I try to do this on talk pages, no white space appears, no matter how many times I hit to create blank lines.

Yet I see here, in this post, that's not the case. What is happening? When I use this new editor, I usually can't add that white space. Longer discussions, especially those involving more than one reply to a single post, can become difficult to read, and identifying distinct posts can be difficult. Thanks! Dcs002 (talk) 03:04, 8 February 2023 (UTC)

how to get semi protection
Ben Dover 23 (talk) 01:35, 3 April 2023 (UTC)
 * Please see WP:RFPP - note also that this is not the appropriate venue to look for help - if you need help in the future, please try the help desk. Tollens (talk) 02:01, 3 April 2023 (UTC)

signature
hello guys,how can I signature in talk page MICHAEL 942006 (talk) 10:48, 31 May 2023 (UTC)


 * Try WP:SIGHOW. Happy editing, Paradoctor (talk) 11:20, 31 May 2023 (UTC)

Propose removing Wikilnk to WP:MUTUAL from Guidelines .
Per this search, very few users have invoked WP:MUTUAL and it seems odd to cite something that isn't followed as consensus of the community. Indeed, it looks like addition of that essay was not even discussed here. voorts (talk/contributions) 01:02, 29 September 2023 (UTC)


 * Pinging @Steel1943 (who added the link to MUTUAL to the guidelines) and @Swpb and @Alalch E., who co-wrote the essay. voorts (talk/contributions) 01:07, 29 September 2023 (UTC)


 * It's not controversial that comments can be edited with the permission of the person who wrote them; MUTUAL is just a framework for doing so. There's nothing here (or in WP:MUTUAL) saying MUTUAL should be used, just that it can. So I'm not sure what position you want consensus on – that it's acceptable to propose a mutual withdrawal? I doubt anyone would say it isn't. — swpb T&#8201;•&#8201;beyond&#8201;•&#8201;mutual 02:38, 29 September 2023 (UTC)
 * Agreed. MUTUAL is provided as an example, not a recommendation, so there is no issue to resolve here.  — SMcCandlish ☏ ¢ 😼  04:49, 29 September 2023 (UTC)
 * I think the issue is that this is the first thing in the list of examples, nobody uses it, and the guidelines are already quite long and this is instruction creep. voorts (talk/contributions) 12:01, 29 September 2023 (UTC)
 * Except it isn't an instruction, it's an example. And it being an essay isn't proof no one uses it. I don't actually feel strongly about retaining this; I just don't find the deletion rationales so far to be exactly "compelling".  — SMcCandlish ☏ ¢ 😼  12:33, 29 September 2023 (UTC)
 * "If you have their permission" was first on the list before I added the MUTUAL example to it, so presumably someone thought it was important, but if moving it lower to make the mention of MUTUAL less prominent eases your concerns, so be it. — swpb T&#8201;•&#8201;beyond&#8201;•&#8201;mutual 13:57, 29 September 2023 (UTC)
 * I think in context, it suggests that MUTUAL should be used, but I take your point that I don't think anyone would argue that MUTUAL isn't an appropriate way of removing talk page comments. I'll withdraw this request and close the thread. voorts (talk/contributions) 20:07, 29 September 2023 (UTC)

Can we collaborate or can we not?
It seems like throughout Wikipedia, contributing to Wikipedia is described as a collaborative effort. But the talk page guidelines state you must not use the talk page as a forum for discussing the topic. I have a particular point that I think ought to be made in an article, but the sources I've found so far are not as good as I would like. On the article's talk page, I explain the point that I'm trying to make, asking for help in locating a good source, but somebody accuses me of discussing the topic, and I can't really dispute that, but evidently it's prohibited. IMO, this prohibition on discussing the topic is wrong. Is there anyplace on Wikipedia we can discuss that? Fabrickator (talk) 03:50, 4 July 2023 (UTC)


 * Asking for help in sourcing a potential edit is not discussing the topic. If you unveiled the location, maybe someone could head over to add their WP:3O? Paradoctor (talk) 04:57, 4 July 2023 (UTC)


 * So suppose there exists some particular term which allows itself of a "strong meaning" and a "weak meaning". It is alleged that the phrase encompasses the "strong meaning" which presumably is a conspiracy theory.  So you would like to discuss the validity of stories that support the "weak meaning". But the phrasing is the same ... it's unacceptable to just add "(weak form)" to the phrase, as the academic community defines the phrase to have only the strong (presumably implausible) meaning, and any attempt to claim this other thing even exists gets you instantly banned and likely subject to additional sanctions.
 * Sorry about being so obscure, any direct mention will be immediately dismissed, there is no possibility of one phrase having multiple distinct meanings, as academia has ruled that the phrase has only the strong meaning, and inasmuch as the underlying goal is the same (i.e. it is only the means of achieving the goal which differs), you can't really avoid mentioning the weaker form without reference to the stronger form.
 * In the instant case (and before I had grasped this weak vs. strong form), I found sources supporting the strong form, but I was told these sources were no good.  Try to discuss the weaker form, that's not really allowed, because reliable sources have defined the phrase to refer only to the strong form.   Fabrickator (talk) 18:06, 4 July 2023 (UTC)
 * Uh, this is off-topic here. What I meant by "unveiled the location" was that you please link to the talk page in question. Otherwise, WP:DR is the way to go for you. Paradoctor (talk) 18:27, 4 July 2023 (UTC)

Can I delete my comment from the archive?
The wiki rules say: Wikipedia:Talk page guidelines#EDIT

'''Striking out text with  or strike or marking text as deleted with  constitutes a change in meaning. It should be done only by the user who wrote it, or as otherwise provided in this talk page guideline.'''

'''Moving edits to closed discussions: A discussion which has been closed with the {{subst:Archive}} or similar template is intended to be preserved as-is and should not be edited. Subsequent edits inside of an archive box should not be removed for this sole reason, but may be moved below the box to preserve the integrity of the closed discussion.'''

There is a contradiction. Admins. Can anyone give a definitive answer? LandsGates (talk) 09:05, 1 March 2023 (UTC)


 * It's not a contradiction, the latter is simply an exception to the former: . HTH, Paradoctor (talk) 18:33, 4 July 2023 (UTC)

The subject's election attempts
The phrasing currently conveys that the subject attempted to be elected 9(nine) times.

It should be changed to clearly state the the Subject ran for election a total of 3(three) times. The subject ran for elected office each time as a Republican. 2605:6000:9FC0:51:893D:6150:F164:571D (talk) 18:09, 27 July 2023 (UTC)


 * You should post this concern on the talk page of the article that you believe is improperly phrased. - Butwhatdoiknow (talk) 18:25, 27 July 2023 (UTC)

Usage of "tomboy"
Remove the word "tomboy." It os outdated and many find the word offensive. Antonia2323 (talk) 05:08, 21 August 2023 (UTC)


 * You seem to be in the wrong place, the guideline doesn't use "tomboy" anywhere. <span style="display:inline-block;position:relative;transform:rotate(-3deg);bottom:-.1em;">Paradoctor (talk) 06:38, 21 August 2023 (UTC)
 * They're taking offense proactively. <b style="color:red;">E</b><b style="color:blue;">Eng</b> 06:44, 21 August 2023 (UTC)

Improve lead sentence
Our current and rather confusing lead sentence is:

I think this would be better as:

Virtually everything in this guideline applies to talk pages of policies, essays, templates, etc., and it has nothing to do with wikiprojects in particular (much less should there be a weird insinuation that discussion on talk pages has anything to do with changes to make at a wikiproject.  — SMcCandlish ☏ ¢ 😼  13:52, 6 November 2023 (UTC)
 * I went ahead and added the text. I tried to simplify it (to remove parentheticals). Obviously, please feel free to update/modify, as appropriate. - jc37 15:01, 6 November 2023 (UTC)
 * Looks goodful to me. I would have gone with shorter wording like that, but suspected there might be some desire to include the word "article" in there.  — SMcCandlish ☏ ¢ 😼  17:51, 6 November 2023 (UTC)

not blank lines
As the page notes, don't put blank lines where they don't go. Someone, some time ago, told me about putting lines with only the colons. Usually the same number as the following line. I often do that, and it seems to work fine. It also makes it more readable when editing, to separate the different comments. Gah4 (talk) 02:52, 9 December 2023 (UTC)

...as here, but producing less spacing. If you want the more spacing, then  will also work, as...
 * What works for you may not work for others. See WP:TALKGAP. <span style="display:inline-block;position:relative;transform:rotate(-3deg);bottom:-.1em;">Paradoctor (talk) 08:00, 9 December 2023 (UTC)
 * WP:TALKGAP says to avoid blank lines, i.e. lines with nothing on them at all, because each one starts not a new list item (as it should), but actually an entirely new list. But if you are in the middle of a chat with three colons for indenting, and you insert between two of these lines a line with three colons and nothing else, my understanding is that it does not have these negative impacts. Thus, you get the positive benefit of separation in the wiki markup without the negative impact that completely empty lines cause. YBG (talk) 05:18, 10 December 2023 (UTC)
 * Still not ideal, since it creates an empty list item, which a screen-reader would probably announce. Worse, it actually results in invalid markup due to a parser problem; it (sometimes, under conditions I've not narrowed down yet, though I was able to do it on purpose yesterday in a preview of this very discussion) creates an empty which never closes and which encloses anything that comes after it. And it produces no blank line in the rendered output anyway, only in the wikicode, which pretty much no one cares about in the first place. If you want rendered vertical spacing between list items without breaking the list, you can use either  or, on the same line as other text, not on its own line, and follow it (again, on the same line) with a   so it is not "erased" by the parser.  Demonstration, part 1:
 * Demonstration, part 2.
 * Demonstration, part 3. Notice that there is more space between parts 1 and 2 than between 2 and 3. Another technique is to use  between what are intended to be paragraphs, but keep it all inline......as I just did there. Using a  tag will also do this...

...shown here. A more tedious vesion is to use elements, and keep them all inline in the same list item, as done with all this following material, including a demo of using HTML comments to show spacing in the wikicode, too: Basically, when spacing in a list item, do whatever it takes to keep the parser from seeing a line break (carriage return, linefeed) that tells it "this list item has ended". And when spacing between list items, do whatever it takes to not introduce an actual blank line (other than one enclosed in an  HTML comment ), since such a blank line tells the parser "this entire list has ended". — SMcCandlish ☏ ¢ 😼  11:26, 10 December 2023 (UTC); note added 19:46, 11 December 2023 (UTC)
 * My comment above was based on the presumption that what was desired was a spacing in the wiki text, not in the rendered text. My experience is that on talk pages many editors wish to space the wikitext to make it more readily editable. I think I recall being told that the empty list item is NOT rendered but swallowed up and so causes no issue for screen readers. I might easily be wrong because (1) I have never verified this (2) I might have mis-remembered and (3) I cannot recall when or where I heard it. Pppppppp YBG (talk) 22:51, 10 December 2023 (UTC)
 * The MediaWiki software detects when a list item has no content and adds a class to it so it isn't displayed. Graham87 has previously confirmed that these undisplayed list items aren't announced by screen readers. So while the semanticist in me isn't a fan of empty list items, pragmatically, they don't affect those using screen readers or the visible rendered output. isaacl (talk) 01:42, 11 December 2023 (UTC)

When to archive
The guidelines say that a page should be archived when it gets over around 75kb, but this seems adapted to the age of dial-up internet. If the constraint is based on loading speed, I propose significantly increasing the guideline - perhaps to something like 200kb. Riposte97 (talk) 23:16, 19 October 2023 (UTC)


 * Loading speed is not just download. Rendering also takes time, and memory. And bandwidth costs money, on both sides of the connection. Carbon footprint should also be a consideration. Then there are still regions with very low bandwidth, even in rich countries like Germany. Last mile restrictions limit my parents to 2 Mbit. 🤷 <span style="display:inline-block;position:relative;transform:rotate(-3deg);bottom:-.1em;">Paradoctor (talk) 00:08, 20 October 2023 (UTC)
 * P. S.: And yes, there are still people on dial-up: "A survey conducted in 2018 estimated that 0.3% of Americans were using dial-up by 2017.[16] The CRTC estimated that there were 336,000 Canadian dial-up users in 2010.[17]" <span style="display:inline-block;position:relative;transform:rotate(-3deg);bottom:-.1em;">Paradoctor (talk) 20:14, 21 October 2023 (UTC)
 * Data from, respectively, 6 and 13 years ago doesn't seem particularly pertinent. But it is correct that rendering time and capacity are a factor. Weaker platforms can crap out entirely, and even on my honkin' fast desktop PC with stupid amounts of RAM, excessively long and code-complex articles can take an annoyingly long time to load, both in reading and in editing mode.  — SMcCandlish ☏ ¢ 😼  21:54, 21 October 2023 (UTC)

On the other end of the spectrum, when is an article talk page overarchived? Is it OK to have a totally blank talk page? (This came up inconclusive here a while back.) I dearchived the last four threads of Talk:30 (album), the latest of which was less than a week old, and got blowback.  Aside from linking to a move request discussion that had just closed and not finding it, a blank talk page just looks weird, especially in this case with a single archive at only 24K. — <span style="border:1px solid #93010b;background:#ef0000;padding:2px;color:#efe6e6;text-shadow:black 0.2em 0.2em 0.3em; font-family: Georgia;"> AjaxSmack 08:19, 11 January 2024 (UTC)


 * I don't like a blank talkpage either (and default to 4 remaining threads as well), but not to the point that I revert when others archive beyond that. I speculate that having a couple helps newer editors/IPs know what a talkpage section should look like. CMD (talk) 09:37, 11 January 2024 (UTC)

Meaning of collapse
I think the "hiding" is more important than the "ending". I.e., editors need not and should not be discouraged from continuing within the collapsed portion. Sometimes the OT (usually a related tangent) is important enough to discuss among interested editors, but not important enough for a separate thread. Editors can easily bypass a collapsed portion, so it's not a distraction. The text in the collapse box should briefly describe the nature of the collapsed content, so editors can decide whether to read it and possibly add to it. &#8213; Mandruss  &#9742;  02:06, 20 December 2023 (UTC)

As for ending entire threads, that's what closure (usually ) is for. Or should be; we don't need two or more ways to accomplish the same thing. We could easily do without, for example, but that's a separate discussion for a different venue.If guidelines are to be descriptive, this one sorely needs updating to reflect the common usage of collapse, without objection, for less than an entire thread. (If it already supports that, it could use clarification; "discussion" usually equates to thread.) &#8213; Mandruss  &#9742;  03:36, 20 December 2023 (UTC)
 * Seems like a WP:Be bold matter to me. I routinely fix bone-headed policy and guideline wording and rarely get reverted as long as it's not a substantive change (i.e., making a meaningfully different rule).  — SMcCandlish ☏ ¢ 😼  03:29, 13 January 2024 (UTC)
 * I think removal of the "ending" part would be a substantive change and meaningfully different; hence this discussion. I'm also looking for input as to new wording. &#8213; Mandruss  &#9742;  16:13, 14 January 2024 (UTC)

Standardize indentation of threads?
brings up another issue, he/she/they refuse to abide by what to me is the canonical indentation used as WP:THREAD and possibly also break for some purposes the "lists" used to store threads.

The standard format is this:
 * Comment, December 31
 * Reply, January 1
 * Reply to reply, January 1
 * Reply to reply, January 3
 * Reply, January 2
 *  EEng's User 's reply, January 3

EEng does Some people do this:


 * Comment, December 31
 *  EEng's User 's reply, January 3
 * Reply, January 1
 * Reply to reply, January 1
 * Reply to reply, January 3
 * Reply, January 2

Does this affect any screen readers or such which are relying on the format of the list? To me, I don't see why EEng any user 's comments are so import they should be inserted out of time order and before all prior responses. It's confusing, and not only that, EEng does this double indentation which is apparently his/her/their own concoction.

Should we enforce a standardized indentation for replies per the examples at WP:THREAD? I.e. if someone wants to reformat the page to adhere to that, should they be allowed to without being considered to have modified someone else's comments? This would codify the way the  link works and to my mind support further automation of talk pages. —DIYeditor (talk) 15:44, 11 January 2024 (UTC)


 * support, per "there's a button for that, it takes one click to do the thing right, use it"  cogsan (nag me)  (stalk me) 16:26, 11 January 2024 (UTC)
 * Oppose In the example given, it appears that EEng positioned their reply to be adjacent to the comment to which it was a direct response. If their reply had been positioned further down, as the OP suggests, then the context would have been lost and so the comment would have been more difficult to follow and make sense of.  I've done the same thing myself more than once for much the same reason and used the same double indent to indicate that it was a tangent.  My own usage is an independent invention and this indicates that it's a commonsense way of handling such threading when there are multiple lines of conversation. The Reply tool is a more recent innovation which is still shaking down and we are not required to use it or follow its logic slavishly. Andrew🐉(talk) 16:52, 11 January 2024 (UTC)
 * There are a few editors who do this; it's not a scalable approach (if more than one person decided their response was a more direct response that the current subsequent response, there would be an escalating race of nesting levels), so it relies on the goodwill of editors to not dispute which comment is most fitting for the immediately following spot. It causes screen readers to make extra list start/end announcements, but since the point of the extra nesting level is to give the comment more prominence, this might be considered an aural equivalent. isaacl (talk) 17:09, 11 January 2024 (UTC)
 * Discussions on Wikipedia are generally not scalable and usually collapse into incoherence once the coefficient of inefficiency is reached. That's not so much due to the technical issues as it is a consequence of everyone trying to talk at once.  Serious committees usually have a chair and rules of order to ensure that the business gets done.  Here's an example:"Then Compton, for example, would explain a different point of view. ... So everyone is disagreeing, all around the table. I am surprised and disturbed that Compton doesn't repeat and emphasize his point.  Finally, at the end, Tolman, who's the chairman, would say, "Well, having heard all these arguments, I guess it's true that Compton's argument is the best of all, and now we have to go ahead."   It was such a shock to me to see that a committee of men could present a whole lot of ideas, each one thinking of a new facet, while remembering what the other fella said, so that, at the end, the decision is made as to which idea was the best—summing it all up—without having to say it three times.  These were very great men indeed."

- R. P. Feynman Andrew🐉(talk) 18:41, 11 January 2024 (UTC)
 * Yes, I've written previously about the problems with Wikipedia's unmoderated, multi-threaded discussions. Editors deciding on their own that their comment is best suited to be the first to follow a given comment is a different problem, though. It doesn't help foster consensus-building when there is a disagreement on the placement. isaacl (talk) 22:02, 11 January 2024 (UTC)
 * Oppose. Talk page formats are for the benefit of the people communicating to each other, not a cage we must keep rigid to prevent them from communicating to each other. —David Eppstein (talk) 17:47, 11 January 2024 (UTC)
 * Comment: I worry about rule creep. Doing anything on Wikipedia for the first time is intimidating. There are already a million rules and guidelines and essays spread across hundreds of pages, and it's hard to know which are important. Talk_page_guidelines is already 6500 words, and might take 20 minutes or so to read. Every additional guideline is another thing for a newbie to trip over, and another reason to worry "Will I get in trouble for screwing this up" instead of feeling encouraged to jump in and contribute. As I'm typing this right now, part of my mental energy is worrying I'm replying wrong :) . This isn't a reason for total anarchy, of course, but I think we should have a stronger rationale than "One guy does this and it's slightly annoying" or "This might cause problems for a hypothetical screen reader".Ghosts of Europa (talk) 17:51, 11 January 2024 (UTC)
 * The "hypothetical screen readers" are actually real people like myself who are unable to edit, or even read, these talk pages. Thank you. Chaotıċ Enby   (t · c) 20:58, 11 January 2024 (UTC)
 * Sorry if my comment sounded dismissive. The proposal framed the possibility of broken screen readers as an open question, like there were no clear examples of it happening. If you're actively hitting a severe accessibility problem, that's a much stronger case for a rule. Ghosts of Europa (talk) 21:58, 11 January 2024 (UTC)
 * <li style="list-style:none;">And, of course, I did end up replying to this thread incorrectly. I meant to reply to the top-level comment :) . This kind of thing isn't always straightforward for newer editors. Ghosts of Europa (talk) 17:55, 11 January 2024 (UTC)</li>
 * It's not like you would be punished for the making the mistake. The question is whether someone else is allowed to go back and fix it. —DIYeditor (talk) 18:54, 11 January 2024 (UTC)
 * Precisely. I'd love to see one solitary case where an editor has gotten in trouble for misplacement or misindentation of a reply (is this a reply to DIYeditor, or Ghosts of Europa?). Absent such an example, the concern is greatly overblown. &#8213; Mandruss  &#9742;  19:17, 12 January 2024 (UTC)
 * If someone wants to discuss talk page guidelines, of course that's fine. But starting the opening post with yet another "EEng refuses" to do something-or-other is highly inappropriate. This is not a talk page for editors to post about whatever in particular rubs them the wrong way about any particular editor. --Tryptofish (talk) 18:05, 11 January 2024 (UTC)
 * Yeah, I realized that, and I had thought about going back and stripping the post of that context. Too late now. —DIYeditor (talk) 18:52, 11 January 2024 (UTC)
 * Comment I've occasionally done the same thing as shown in the example. When the response thread under "reply to Jan 1" is really long, it makes it confusing to put another reply to Dec 31 a mile down the page and I thought it it would solve that issue. And I think that the extra indent meets the intent of the chronological rule?   <b style="color: #0000cc;">North8000</b> (talk) 18:29, 11 January 2024 (UTC)
 * English Wikipedia has a talk page tradition of putting new comments at the end, though, so interjecting one's response ahead of earlier ones isn't what readers are generally expecting, particularly if they're reading the thread for the first time and so will be reading the first level of direct responses out of order. (It is true that with the relatively recent thread subscription feature, it's easier to find new comments wherever there are. But this still involves scrolling through the thread to find highlighted comments, or going back to your notification list and selecting each new comment one at a time. Alternatively, history diffs can be used (and I find the visual diff mode makes it more readable), but it only lets you see part of the surrounding context.) isaacl (talk) 22:15, 11 January 2024 (UTC)
 * For as long as I remember being here, top-posting has been something that editors do. Personally, I don't feel like it's unexpected when I see it. If the post is something where there's a logic to putting it up there, I'm not that bothered by it. --Tryptofish (talk) 22:20, 11 January 2024 (UTC)
 * And if (generic) you disagree with the logic of someone putting a post above your response, which you carefully crafted to respond directly to the initial comment? Usually it would be just a distraction to argue about it, so you grit your teeth and live with it, even as it adds a bit of friction to the discussion. isaacl (talk) 22:27, 11 January 2024 (UTC)
 * (Note that I'm top posting above North!) Generic me agrees with you about that, and I've certainly experienced that from time to time. But there's friction, and there's friction, so to speak. Some kinds of friction really get in the way of what editors are here to do. This kind of friction strikes me as usually being something where the most sensible reaction is to shrug it off. --Tryptofish (talk) 23:56, 11 January 2024 (UTC)
 * Yes, I agreed that not doing anything about it is the best approach, in interest of fostering a productive discussion. (Outdenting a comment makes it hard to continue the usual list nesting traditions in English Wikipedia discussion threads. Usually I will reset the conversation with no nested list levels.) isaacl (talk) 00:06, 12 January 2024 (UTC)
 * For review: posting style. Viriditas (talk) 00:00, 12 January 2024 (UTC)
 * I think that that is a good tradition, albeit it only applies for comments at the same indent. For example, in:

Jan 1 post
 * Jan 2 response to Jan 1 post
 * Jan 3 response to Jan 1 post
 * Jan 5 response to Jan 3 post
 * Jan 4 response to Jan 1 Post

The Jan 5 response is supposed to be higher up than the Jan 4 response. <b style="color: #0000cc;">North8000</b> (talk) 22:31, 11 January 2024 (UTC)
 * Oppose. No set of rules will be both sensible and simple. And who is going to police it?  There are occasional newbies who need to be taught how to indent, but otherwise this is a solution in search of a problem. Zerotalk 01:52, 12 January 2024 (UTC)
 * My question is am I allowed to reformat pages to adhere to the format the [ reply ] link uses, or is it ok to be subjected to "don't ever fuck with my comments again" in response to doing so? —DIYeditor (talk) 14:03, 12 January 2024 (UTC)
 * I believe the spirit of TPG (can't put my finger on the letter) is that you can BOLDly do that, but should let the user have their way if they subsequently object. I don't think it's reasonable for any editor to ask you to maintain a list, mental or written, of editors who never want their comments fucked with. If they don't want that, they should have to object repeatedly, case by case. &#8213; Mandruss  &#9742;  19:28, 12 January 2024 (UTC)
 * One might be "allowed" to reformat in that way, but it's also prudent to evaluate ahead of time whether doing so is worth it. If one suspect that the response will be an angry one, it's not worth the drama to poke at it. --Tryptofish (talk) 20:04, 12 January 2024 (UTC)
 * Agreed. Angry editors are a fact of life around here, and that's not going to change until we repeal human nature. &#8213; Mandruss  &#9742;  20:13, 12 January 2024 (UTC)
 * (I'm half-expecting that someone will propose that we repeal human nature.) But seriously, this is an important point. (In fact, it's one Talk Page Guideline that I could gladly get behind.) Part of what WP:IAR really means is that maintaining a collegial editing environment, with a focus on improving mainspace content, is more important than rules for rules sake. Just being "right" about talk page indenting, or talk page length, is something that should be balanced against how counterproductive it can be to have a multi-day drama-fest. --Tryptofish (talk) 21:51, 12 January 2024 (UTC)
 * Vehemently oppose. We have better things to do that act as "posting cops" against other editors just to be anal/obsessive. Sometimes it makes sense to inject a reply higher up than one would normally do it, though the cases when this is useful are not all that common. But we have no reason to refactor list formatting other than to comply with MOS:LISTGAPS problems (blank lines between list items, or switching list formats mid-stream, like replying to  with   for no damn' reason). If you really care about misuse of list formatting, read MOS:DLIST, and then go around  (not talk pages) fixing abuse of   for non-list, purely visual indentation of material, replacing it with .  would actually serve a real user-facing purpose, including for those with screen readers. While you're at it, replace abuse of   for non-list, purely visual boldfacing, using   (or  if it is semantic emphasis, though the majority of the latter can and should be replaced with  instead, per MOS:TEXT). NB: Sometimes an extra linebreak is needed, if the   is being abused for a MOS:PSEUDOHEADING and is butted up against the content that immediately follows (the   format injects a line-break, but   does not).  — SMcCandlish ☏ ¢ 😼  03:43, 13 January 2024 (UTC)
 * Comment - I've lost count, the number of times editors failed (deliberately or not) to follow correct "indenting" & more so "outdenting", in discussions. GoodDay (talk) 22:32, 16 January 2024 (UTC)

User talk page size
There's recently been discussion about ANI about a user's talk page that is very long and causes some browsers to crash. There was (correctly, I think) no consensus to enforce archiving on their talk page through a bespoke editing restriction, but very large talk pages do cause accessibility issues and I think it's worth discussing whether there should be a maximum acceptable size for user talk pages. I'd be willing to support an addition to this guideline along these lines:

I'm not putting this forward as a formal proposal yet because it definitely needs some work, but I think it's worth discussing. Thoughts? — Callitropsis🌲&#91;talk · contribs&#93; 06:29, 9 January 2024 (UTC)
 * I'm not convinced that this problem is a significant one. I've checked almost a dozen machines, and the only one that had issues opening EEng's talk page was an ancient Samsung Galaxy S5 - and that also has trouble opening the main page, so I don't consider its failure indicative. BilledMammal (talk) 06:44, 9 January 2024 (UTC)
 * My computer (bought less than a year ago) has trouble opening it, so I don't think your experience is necessarily the most representative. Chaotıċ Enby   (t · c) 07:47, 9 January 2024 (UTC)
 * Maybe it is not your computer the problem but your internet connection. And maybe it was a temporary problem at that? Regards, Thinker78  (talk) 22:17, 10 January 2024 (UTC)
 * No, I have both a good computer and a good internet connection. Tested again today, same results. Possibly due to various factors, but the point is that some people do have difficulties accessing it. Chaotıċ Enby   (t · c) 18:27, 11 January 2024 (UTC)
 * I agree with Enby, especially if you have a userscript that processes talk pages. Aaron Liu  (talk) 14:35, 9 January 2024 (UTC)
 * I'm strongly against the idea of someone else messing with an editor's talk page. I do archive mine, but if I were to not do so, then it's my choice, and WP:OWNTALK applies here. With that said, yes, there should be some restrictions on how long a talk page may be.  Liliana UwU  (talk / contributions) 12:17, 9 January 2024 (UTC)

100kb of wikitext was proposed as an upper threshold, which is roughly analogous to articles (which tend to be pruned or split out at that size). The main problem already reported is using the desktop site on mobile, which can give "repeated problem occurred" messages on iOS.

Additionally, the desktop site has a tendency to jump to the wrong place on large discussion pages, possibly before all templates are transcluded and the final HTML rendered. For example, clicking on the last section in User talk:EEng from browsing its history left me looking at a conversation from August 2023. <b style="color:#7F007F">Ritchie333</b> <sup style="color:#7F007F">(talk) <sup style="color:#7F007F">(cont)  09:36, 9 January 2024 (UTC)
 * Another metric, leaving this comment took 25 seconds, above the general 15 second limit beyond which users think the site's dead or crashed. <b style="color:#7F007F">Ritchie333</b> <sup style="color:#7F007F">(talk) <sup style="color:#7F007F">(cont)  09:43, 9 January 2024 (UTC)
 * Can't load "EEng's" talk page at all. Moxy -Maple Leaf (Pantone).svg 23:57, 10 January 2024 (UTC)

I think the last sentence is a little problematic. Every opportunity should be given to the editor to archive the talk page themselves, or at the very least, give a compelling reason as to why they require a talk page that is 939,878kb long.<b style="font-family:Times New Roman; color:black"> Isaidnoway </b><b style="font-family:Times New Roman; color:#FF5F1F">(talk)</b> 10:00, 9 January 2024 (UTC)


 * I absolutely support enforcing a reasonable limit on talk page size. Talk pages are primarily intended for communication; if they load slowly they are not serving that function. Since this was triggered by EEng's talk page; on a fiber-optic broadband connection the page was noticeably slow to load; on a phone with a 5G internet connection in the middle of the city it was almost impossible. If someone wishes to preserve content in userspace that they like to look at, the userpage and any subpages are available. I don't love enforcing this via a mandatory bot; that is bound to trigger edit-warring over the bot code. Escalating blocks are simplest. Vanamonde93 (talk) 10:47, 9 January 2024 (UTC)
 * I would imagine enforcement to be analogous to somebody who the community thought should change their signature, but declined to do so. <b style="color:#7F007F">Ritchie333</b> <sup style="color:#7F007F">(talk) <sup style="color:#7F007F">(cont)  11:31, 9 January 2024 (UTC)
 * I'm open to being convinced otherwise, but I'm not sure blocks are the best idea. I imagine any action on that would descend into an ANI thread with people incredulous that an admin would block over something as small (as they would see it) as a talk page. A bot creating standardized archives likely has less potential for drama. Ed [talk] [OMT] 17:34, 9 January 2024 (UTC)
 * For a typical case study, see Administrators' noticeboard/IncidentArchive1027 <b style="color:#7F007F">Ritchie333</b> <sup style="color:#7F007F">(talk) <sup style="color:#7F007F">(cont)  17:43, 9 January 2024 (UTC)
 * I'm actually not opposed to archiving being enabled on all talk pages, no exceptions. My issue is with allowing someone else to add archival code to your talk page, because if you are a recalcitrant editor who is being difficult about archiving, I'm fairly certain you would just revert the addition and dare us to block you. Whereas, if we codify talk page size within the TPGs, a passing admin would be able to block with a solid backing in policy. Vanamonde93 (talk) 19:40, 10 January 2024 (UTC)
 * Yes, a passing admin absolutely should block the busybody jerk who came along and decided to archive somebody else's talk page. --Tryptofish (talk) 19:43, 10 January 2024 (UTC)
 * , I assume you meant that sarcastically, but I want to respond to your broader point below since it's clear I've been misunderstood. I'm not in any way suggesting that immediate blocks be handed out at the slightest sign of a length issue. I'm suggesting that if an editor is being difficult about archiving an inaccessible talk page, allowing an admin to block them via TPG is a superior and more direct solution compared to allowing another editor to add archival code to their talk page. That latter option will only engender drama. Of course we should talk to them first; I'm willing to bet most inaccessible talk pages are accidents, and EEng's might be somewhat intentional but is certainly not malicious. But if I were hypothetically formatting my talk page posts so they displayed in a non-readable color (fairly trivial to do) and if I ignored reasonable requests not to do so, I would be rightfully blocked. If I had an obnoxious signature and refused to change it, I would be rightfully blocked (many experienced editors have been, over this). How is page length any different? Vanamonde93 (talk) 19:57, 10 January 2024 (UTC)
 * Yeah, I was indeed being sarcastic, and I appreciate your thoughtful reply, especially in the way that it gets more nuanced than what you had said before. Sure, I agree with you over those examples, and I can agree over what may need to happen in the (rare) instance when an editor really is unfriendly about being helpful to other editors who want to post at their talk page. At the same time, I also meant what I said, to the extent that someone who self-appoints to go to another editor's talk page and set up archiving without consent really is being a jerk, and the fact that the editor might revert that should not be taken as having risen to the point where it's time to hit the block button. --Tryptofish (talk) 20:04, 10 January 2024 (UTC)

For the record, I don't want the discussion to be specifically about EEng. User talk:Tagishsimon is another example of a lengthy talk page, where the editor has been asked about archiving, to no response. <b style="color:#7F007F">Ritchie333</b> <sup style="color:#7F007F">(talk) <sup style="color:#7F007F">(cont)  11:30, 9 January 2024 (UTC)
 * I agree and it's a problem I've seen with other user talk pages, which is why I specifically avoided mentioning EEng by name. Perhaps it's just dancing around the elephant in the room, but I think the ANI thread should probably just be closed at this point and I don't want to give him any more grief. — Callitropsis🌲&#91;talk · contribs&#93; 17:00, 9 January 2024 (UTC)

Agreed with Isaidnoway and Ritchie, I think this is a very sensible guideline to put in place, given how painful it is to navigate some of the really long talk pages on mobile. Any addition to the guidelines should make it clear, however, that any intervention ought to come after an unsuccessful discussion with the editor. WindTempos (talk • contribs) 12:06, 9 January 2024 (UTC)

Editing talk pages on mobile is quite a pain in the ass, so we should pragmatically enforce/strongly encourage every measure that makes collaboration easier. I strongly support enforcing a page size limit, and allowing other users to boldly implement an archive solution if after being pinging an active user does not do anything about it. That said, I also find this other situation quite difficult, where editors remove text without archiving it, for example User talk:thewolfchild who insists on talking on other Users' talk pages but will not host a conversation on their talk page. That said, their general preference for talking on Article talk pages is certainly reasonable. ~ 🦝 Shushugah (he/him • talk) 13:52, 9 January 2024 (UTC)

I would say to forget creating a rule and instead impose an artificial technical limit at around 350k, with automated warnings at thresholds approaching that level, and automated archiving of the page upon reaching that threshold. Make it impossible to save an edit that takes the page over that number. BD2412 T 14:41, 9 January 2024 (UTC)
 * I don’t think that’s something we should entrust to WMF bureaucracy to develop, and you’d have to define the rules for automatic archiving. I’d rather we create a rule. Aaron Liu  (talk) 14:58, 9 January 2024 (UTC)


 * Support This absolutely should happen, and treated like we do article size; rules of thumb that we bring in as needed. We already police user pages, user signatures, and user talk pages for various reasons, and considering editing another user's talk page is a requirement for certain actions (pinging isn't considered acceptable), then that's something where users are technically inhibiting other's ability to engage with them. That's unacceptable, and "just get a new computer (which may or may not solve the problem", or "well turn off the scripts that are causing trouble (just for these one or two users who refuse to be courteous)" are unacceptable defenses. Der Wohltemperierte Fuchs  talk 15:10, 9 January 2024 (UTC)
 * I agree with the people in favor of this above, and think that the comparison to user signatures is appropriate. 100k might be a bit low for an upper limit, but 350k sounds fine. Ed [talk] [OMT] 17:34, 9 January 2024 (UTC)
 * Support This really should've been a policy before, but most users are willing to voluntarily archive their pages when asked. I expect we'll have very few instances where this policy is needed, but it absolutely needs to be put in place, as we've seen that a handful of editors will just refuse to archive their pages for whatever reason. These large pages make it difficult to even read the discussions occurring there, much less interact with the user, and communication is a requirement. Whether it's enforced by users/admins manually archiving the page, or by making bot archiving universal across the wiki, it needs to happen. &mdash;  The Hand That Feeds You :Bite 17:40, 9 January 2024 (UTC)
 * Oppose. Actually, I don't absolutely oppose this, but I figure that putting that bold font label at the beginning, just after some bold-font supports, will get more people's attention. I'll say that I'm sympathetic to concerns that some users encounter technical problems with accessibility, and that all members of the community have some obligation to make it accessible to contact them via their user talk pages. So this isn't a strict oppose. But I'm strongly put off by the draft language in the proposal, that "any uninvolved editor may set up automatic archiving of the user's talk page as an administrative action." If that means "administrative" in the sense of what Wikipedia admins are entrusted to do, that would be the worst kind of back-door unbundling. And I'm strongly opposed to self-appointed busy bodies going around and enforcing what they think are Teh RulzTM (see also WP:MALVOLIO). Vanamonde93, whom I respect very much as someone with a lot of clue, nonetheless gives me the chills when whipping out "escalating blocks". If we're getting to the point of blocking editors for stuff like that, well, sheesh. The draft proposal sensibly doesn't define a number for when the line is crossed. So I suggest this bit of homework, before we get to the point of making anything formal in policy. Let's do some empirical study of how many kb it takes to really interfere with accessibility in a meaningful way. Not just one editor saying something anecdotal. Then see how many talk pages exceed that. And then see how many of the editors of those talk pages will or will not archive after a friendly request. --Tryptofish (talk) 17:46, 9 January 2024 (UTC)
 * Let's do some empirical study of how many kb it takes to really interfere with accessibility in a meaningful way
 * Completely impractical, given the wide array of different computers, phones/tablets, internet connections, and ISPs involved.
 * And then see how many of the editors of those talk pages will or will not archive after a friendly request.
 * The entire reason for this proposal is ANI's failure to deal with the worst example of this problem on the site. This proposal is intended to prevent that kind of mess happening in the future. It needs a bit of tweaking for language and scope, agreed, but "let's wait and see what happens" is just kicking the can down the road, when it's been kicked down the road for years already. We can absolutely ask people to archive it themselves, but this proposal is for what to do when people just refuse & things get unwieldy. &mdash;  The Hand That Feeds You :Bite 17:55, 9 January 2024 (UTC)
 * Reply to me like that, and I'll switch to a strong oppose. If it's so completely impractical, I'm spectacularly impressed with your genius at determining that it was the worst example site-wide, not the second worst or the third worst, but the worst. Really, that's amazing! --Tryptofish (talk) 18:00, 9 January 2024 (UTC)
 * Guys, chill out. As I understand it, Tryptofish agrees with the general principle but not the specific resolution. So, to be clear, Tryptofish, would you be okay with the wording except for the part starting "If a user talk page exceeds this size...." In which case, I'm happy with leaving this up to administrator discretion. <b style="color:#7F007F">Ritchie333</b> <sup style="color:#7F007F">(talk) <sup style="color:#7F007F">(cont)  18:07, 9 January 2024 (UTC)
 * Thanks, Ritchie. Yes, I would feel a lot better with that revision. But I still want to insist that we need more of an empirical basis for this to become meaningful as policy. Tamzin says correctly below that we should not base this on anecdotes, so it's not just me that feels this way. And Ivanvector makes a very good point that image files are very important to consider, as opposed to just page size. --Tryptofish (talk) 18:38, 9 January 2024 (UTC)
 * Basing it on numbers should not need much testing; it should only need an agreement on a measurement for how much is too much, and users opinion on if a limit is too small, for which I think 350kb is big enough. Aaron Liu  (talk) 18:44, 9 January 2024 (UTC)
 * I'm neutral as to whether it needs "much" testing. I certainly don't feel strongly that it has to be a lot of testing. But it needs to be more substantive than you just saying that you "think" a particular number is big enough. --Tryptofish (talk) 18:48, 9 January 2024 (UTC)
 * Tryp, I don't recall now if it was you who complained in the EEng civility parole proposal (I wasn't watching closely before it was wisely closed) that doing things like that just creates an unreasonable burden on the sanctioned editor and makes them a target for the "civility police", but aren't arbitrary size limits on talk pages a form of the same thing? If we write into the guideline that users' talk pages cannot exceed &lt;some number>, we will certainly have threads at ANI about users whose talk pages are &lt;some number plus a bit> but which nobody has identified as a problem for any other reason. That's another reason my preference is to word this as an advisory and deal with complaints case-by-case, rather than relying on a hard limit. Or as I pointed out yesterday, an SEO optimization tool I consulted suggested that properly accessible pages should not exceed 5MB in download size, and the same tool had EEng's talk page downloading just under that limit. Further evidence that page size does not correlate with usability, neither database text size nor data transfer size. Ivanvector (Talk/Edits) 19:43, 9 January 2024 (UTC)
 * We could also set up an ANI thread for things similar to the InedibleHulk situation said above. Aaron Liu  (talk) 20:16, 9 January 2024 (UTC)
 * Ivanvector, I agree entirely with everything you said there. As I keep trying to get across, the last thing that we need are talk page police, and whatever we do should be based upon empirical reality rather than somebody's hunch of The Right NumberTM. And since editors are continuing to give personal anecdotes, I might as well report that my own computer is getting a little old and buggy (come to think of it, so am I), and I find that EEng's talk page loads more slowly for me than other pages, but it has never made my computer literally crash (in the sense of freezing up or of causing my browser to become unresponsive) or made me feel unable to post there or read what other editors post there. --Tryptofish (talk) 00:08, 10 January 2024 (UTC)
 * Have you tried any talk page–enhancing user scripts like Convenient Discussions and Factotum? Aaron Liu  (talk) 00:47, 10 January 2024 (UTC)
 * No. --Tryptofish (talk) 01:10, 10 January 2024 (UTC)
 * Well, I can tell you that the page requires more than twenty seconds to load. And I have a Ryzen 2700. Aaron Liu  (talk) 01:41, 10 January 2024 (UTC)
 * Ivanvector, a couple of comments: "users whose talk pages are &lt;some number plus a bit> but which nobody has identified as a problem for any other reason" already a reason, so who cares? There is no "there must be two or more reasons" rule with regard to any noticeboard. This being an ANI matter is extremely unlikely unless someone stubbornly refuses to comply, and the entire matter would be made moot by having a bot auto-comply for them.  — SMcCandlish ☏ ¢ 😼  03:27, 13 January 2024 (UTC)
 * If a lot of people agree that it's big enough, it'd be big enough, and that would be substantive enough by Wikipedia standards. Aaron Liu  (talk) 20:16, 9 January 2024 (UTC)
 * Reply to me like that
 * What? You're acting like I kicked a puppy, when all I did was disagree with your points. Fuck it, I'll leave this to everyone else, I don't need your impressed with your genius insults and hollow "threat" to change your !vote. &mdash;  The Hand That Feeds You :Bite 18:16, 9 January 2024 (UTC)
 * That is not an ANI failure at all; EEng is aware of the technical issues with his very large talk page and has been more than willing to archive his page when asked to do so, but he prefers to do so manually. He has offered to do so now, but can't because he's blocked for completely unrelated reasons. Saying that this proposal is entirely the result of EEng's failure or refusal to comply is wholly unreasonable. Ivanvector (Talk/Edits) 18:07, 9 January 2024 (UTC)
 * I recall at various points over the years EEng flatly refusing to archive when asked. But regardless, I'm bowing out of this discussion now. &mdash;  The Hand That Feeds You :Bite 18:16, 9 January 2024 (UTC)

PAGE ]]) 21:03, 1 February 2024 (UTC)
 * Rules for page size should really be based on the actual amount of data transferred when loading, not the "page size" visible in a page's history/information, which is just a measure of text on the page. The actual size includes images, scripts, templates, etc. which must load in the browser even if they only constitute "File:filename.jpg" in the "official" page size. Here's one way to measure: in Chrome, open an incognito window or log out, right click the page, "inspect", click the "network" tab, ensure "disable cache" is selected, then reload the page and wait. Look at the bottom. "Transferred" is the actual amount downloaded. "Resources" is the size of the page content once it's uncompressed (what's loaded in the browser). When logged in, your user scripts, gadgets, etc. can increase the size/time. For me, EEng's talk page transferred 4.6 MB and occupies 12.0 MB in resources. Tagishsimon's talk page transfers 2.9 MB and takes up 7.1 MB in resources. For me, while yes it's annoying to deal with a massive page, the difference is primarily on mobile. In the past, EEng's talk page crashed my mobile browser. Today, it doesn't crash but takes a long time to scroll, for different parts of the page to appear, etc. (and that's without trying to edit). There are people for whom amount transferred or resources loaded matter more or less, of course (connections and devices vary), but that's the sort of thing we should probably be going by. Talk pages, unlike a user page, have an essential function -- to facilitate communication. I'd therefore support an intervention to ensure the normal functioning of those pages. The balance is to ensure highly active users can have a functional talk page. Highly active users may have many conversations happening at once, frequent bot notices, etc., with autoarchiving challenging. I retain a handful of old conversations as something like a to-do/reminder/unresolved list, for example. I suppose there are things like DNAU to prevent autoarchiving, but many of our talk pages will inevitably go fairly long. What we should do is figure out a number rather than an "I know it when I see it" system that's wildly unevenly applied. &mdash; Rhododendrites  <sup style="font-size:80%;">talk \\ 18:05, 9 January 2024 (UTC) Adding, for the record, that I support some kind of clear limit. The only questions are (a) what that limit should be based on, (b) what that limit should be, and (c) how is it enforced. &mdash;  Rhododendrites  <sup style="font-size:80%;">talk \\ 16:41, 10 January 2024 (UTC)
 * That would be ideal from a technical standpoint, but it seems way too impractical to be good in practice. Page size in the history is definitely less accurate, but it seems "good enough" and has the advantage of being easy to check on any browser or device including mobile. Not every editor will be able to access a Desktop browser with a Chromium-based browser at all times to verify. The Wordsmith Talk to me 18:35, 9 January 2024 (UTC)
 * Like I said at ANI (or maybe it was somewhere else, I don't know any more) the computer that I am currently using regularly cannot load EEng's talk page, but has not had a problem with any other page on Wikipedia. Like Rhododendrites tries to explain, that's not a function of the page's database size but of the amount of (mostly media) content that needs to be transferred and then rendered into memory; my old backup laptop just can't handle it. It does, however, run media-intensive web apps like Youtube and Plex and Netflix with no problem at all other than not being able to hear the tiny speaker over how fast the fans spin. My point is that this should not be based strictly on page size; I've seen many talk pages that were much longer than EEng's, but had no trouble loading them as they were primarily text. ANI itself is a good example. If we're going to require users to maintain accessibility of their talk pages, and we should, it should be complaint-based as each one is likely to be a bit different, and we can help a user to set up archiving if page size is the issue or to troubleshoot the problem otherwise, and maybe we should impose automatic archiving for users who won't cooperate or break their talk pages on purpose, but we should not do any of this with arbitrary size limits. Ivanvector (Talk/Edits) 18:19, 9 January 2024 (UTC)
 * For starters, I wish people would stop commenting, essentially, "Works on my machine". Cool. Good for you. That's not how discussions about technical issues work. If long talk pages crash on a significant portion people's machines (as they do on my Chromebook), no one cares if they don't crash on yours. So I agree that the guideline should be given some teeth here. For numbers, I would endorse 100kB advisory, 350kB mandatory. (Personally, I'd be between these two numbers, currently 272kB.) This could be worded, as a slight amendment to Callitropsis' proposal, as ... users are encouraged to keep their user talk pages and associated archives below 100 kilobytes of wikitext. Leeway is allowed past this, but if a user talk page exceeds 350 kilobytes, any uninvolved editor ... -- Tamzin  &#91;<i style="color:#E6007A">cetacean needed</i>&#93; (they&#124;xe&#124;she) 18:24, 9 January 2024 (UTC)
 * That also sounds like a reasonable guideline to me, though maybe further amended with warnings before forced archiving. Aaron Liu  (talk) 18:31, 9 January 2024 (UTC)
 * Sure, could add and the user does not archive it upon request. -- Tamzin  &#91;<i style="color:#E6007A">cetacean needed</i>&#93; (they&#124;xe&#124;she) 19:24, 9 January 2024 (UTC)
 * A lot of people have been debating the particulars of how this should be implemented and/or disagreeing with aspects of my suggestion, so I'd like to make it clear that my suggestion was intended to be an example of a possible addition to the guideline and I'm really not at all attached to any one part of it. I suppose I should have made it clear in my initial comment, but I started this discussion with two principles in mind:
 * There should be an upper limit to user talk page size. I'm certainly no technical expert so I don't have any strong opinions as to how this should be measured (wikitext or file transfer data, for example) or what the limit should be, although I used wikitext in my rough draft because it seems easier to measure. Tamzin's suggestion for a discretionary range seems reasonable, although I don't have an opinion on the specific range they suggested.
 * This limit should be enforceable. Again, I don't particularly care how it's enforced as long as it has teeth. I wrote any uninvolved editor because at the time it seemed unnecessary to me to gatekeep maintaining talk pages to admins only. As far as I'm aware, one doesn't need to be an admin to remove 30/500 violations from people's user pages, for example (please correct me if I'm wrong). With that said, I think Tryptofish's comments about overly zealous busybodies are reasonable, and I wouldn't be opposed if we decided that setting up auto-archiving on the talk pages of other editors without their explicit consent is something that only admins should do. I do think blocks should be on the table as a last resort because this restriction would otherwise be practically toothless, but I don't think such needs to be said in this guideline because Disruptive editing Blocking policy is a policy and authorizes the use of the blocking tool to enforce policies and guidelines.To reiterate, I really don't care if someone decides to rewrite my suggested language from scratch as long as it follows these principles. I went to great lengths to avoid using the word "proposal" in this comment because the language I used in my initial comment was intended to be a rough idea to kick-start the discussion, not any sort of concrete proposal. I would welcome any workshopping and/or rewriting that people think is appropriate (although I obviously don't want people editing my initial comment and I'd prefer if people instead made new comments with their proposed language). Hope that clears things up. edited 19:17, 9 January 2024 (UTC) — Callitropsis🌲&#91;talk · contribs&#93; 18:51, 9 January 2024 (UTC)
 * Strongly support this. My own browser was one of the ones that crashed out on the page in question, and I have more RAM than god. There have to be some technical limits on this, and the sky is in no way going to fall if we have a bot auto-archive old stuff off a talk page of insane length. Our weird fetish for treating user talk pages as a magically special fairyland has to end.  — SMcCandlish ☏ ¢ 😼  19:44, 9 January 2024 (UTC) PS: I'm fine with the alternative wording below. As long as we get this done in some enforceable form.  — SMcCandlish ☏ ¢ 😼  03:32, 13 January 2024 (UTC)
 * Support a formal limit, although also suggest an alternate wording. With the suggested wording, an editor can swoop in and impose a style of archiving that a user might disagree with once a magic limit is hit.  We should trust editors to set up whatever archiving system they prefer, instead, and save the imposed version for the combination of a very long talk page and a refusal by the editor to do anything about it.  Suggested revision:  SnowFire (talk) 20:06, 9 January 2024 (UTC)
 * That sounds a bit too unverbose for just a simple "they've been warned". I think Tamzin's version would be enough:  Aaron Liu  (talk) 20:21, 9 January 2024 (UTC)
 * In between, I like the idea, but I'm not so sure about the wording. Specifically the wording . To me this reads like "If there is refusal you can simply just set up archiving anyway." Not exactly sure what a solution to this would be, as if they refuse there's not a whole lot to do. What, should we suggest we take them to ANI? That seems rather extreme for something like this. ― <b style="background:#0d1125;color:#51aeff;padding:1q;border-radius:5q;">Blaze Wolf</b>Talk<sub title="Discord Username" style="margin-left:-22q;">blaze&#95;&#95;wolf 20:51, 9 January 2024 (UTC)
 * I mean, the idea is to enforce archiving. Aaron Liu  (talk) 21:05, 9 January 2024 (UTC)
 * Oh, God no, to any of that. The last thing that we need is for self-appointed busy bodies to go around as the talk page police. --Tryptofish (talk) 23:59, 9 January 2024 (UTC)
 * Why not? We already have janitor police, signature police, and the civility police. Aaron Liu  (talk) 00:48, 10 January 2024 (UTC)
 * There's always been this tension between a prescriptive and a proscriptive approach. I'm not a fan of fear-based, negative outcomes.  For example, I don't speed on the highway, not because I'm afraid of getting a ticket, but because I want to avoid accidents, give animals on the road more time to survive the crossing, and generally want to get from point A to point B in safety.  So the idea of outside enforcement rather than self-enforcement doesn't work with me. Viriditas (talk) 01:44, 10 January 2024 (UTC)
 * Not everyone can be served by prescriptives, which is why we have highway police. Aaron Liu  (talk) 01:54, 10 January 2024 (UTC)
 * That kind of argument falls apart when you look closely at it, and it raises other issues, some of which have to do with using the highway police as local tax collectors and criminalizing normal human behavior. And there's the counterargument of the German autobahn, most of which has no speed limit, but safety is still guaranteed due to other factors. It's not as black and white as you think.  Letting people do what they want has certain advantages. Viriditas (talk) 02:04, 10 January 2024 (UTC)
 * Maybe it's because I've lived under an authoritarian state for quite a while, but I don't see how there'd be much subjectiveness that would lead to criminalization or what part of this fits the metaphor of tax collectors. From a cursory glance at search, the autobahn has safety because it has quite a bit of other rules. That'd be like "there's no size limit but you must archive threads more than 3 months old". Aaron Liu  (talk) 02:09, 10 January 2024 (UTC)
 * In the US, the police often act as tax collectors, and use the rule of law to extort money from drivers for local coffers, often with confusing speed traps that are designed to target travelers from out of town who pass through their communities. This is a big problem in certain parts of the country.  It's not really a metaphor so much as it is one of many examples of the law being used to oppress people. Viriditas (talk) 03:23, 10 January 2024 (UTC)
 * Strong support. My devices struggle to open this user's extremely long talk page, and it is clear to see that this is the case for many other contributors here, also. Talk pages should be accessible; not ensuring that they remain so is disruptive. Patient Zerotalk 00:26, 10 January 2024 (UTC)
 * Support in concept. I've long found it puzzling why user talk pages are treated the way they are; their purpose is for communication, and anything that impedes that purpose is undesirable. However, I oppose the "any uninvolved editor may set up automatic archiving" part. That is only going to cause problems and drama. Any "enforcement" is fraught with risk, but I think with a reasonable guideline established (Tamzin's 100kb advisory, <350kb mandatory is a good starting point, but I'd consider going lower), a polite "Your user talk page exceeds the size limit, please archive it" would be enough in 90+ percent of cases. For the rest, yes, they will probably end up at AN/I, but that's where "User:Example set up archiving on my talk page that I didn't want" is going to end up anyway. And an editor who'd refuse to archive their talk page would also probably just revert the auto-archiving - therefore also likely to end up at AN/I. Best not to open that can of worms, and simply let it be handled like other user conduct issues. --Sable232 (talk) 00:44, 10 January 2024 (UTC)
 * Support Why is this even a discussion?
 * first sentence of the lead of WP:MOS: provisions related to accessibility apply across the entire project, not just to articles
 * lead of WP:USER: User pages are available to Wikipedia users personally for purposes compatible with the Wikipedia project and acceptable to the community; Wikipedia is not a blog, webspace provider, or social networking site. Wikipedia policies concerning the content of pages can and generally do apply to user pages, and users must observe these policies. <span style="display:inline-block;position:relative;transform:rotate(-3deg);bottom:-.1em;">Paradoctor (talk) 00:46, 10 January 2024 (UTC)
 * P.S.: For those complaining about uninvolved editors setting up archiving: That's in keeping with the Spirit of WP:TALKO™. <span style="display:inline-block;position:relative;transform:rotate(-3deg);bottom:-.1em;">Paradoctor (talk) 00:53, 10 January 2024 (UTC)
 * Comment: I want to personally thank User:EEng for forcing me to buy a new computer.  If it wasn't for his long talk page, I don't think I would have made an effort.  I am happy to report that his page loads in less than a second now.  I think I have a different opinion about these things than most people.  If it wasn't for people like EEng and Tryptofish giving us the ability to benchmark and check our systems, some of us might never do what needs to be done.  I think these users perform a valuable service and should be allowed to keep their talk pages as long as they want because of the beneficial impact it has on the economy. Viriditas (talk) 01:17, 10 January 2024 (UTC)
 * Yes, we're making America great again. In the interests of changing the subject, I'm going to link to this: . Anyone want to block him posthumously? --Tryptofish (talk) 01:30, 10 January 2024 (UTC)
 * A good point, which I was about to make less pithily. Blocks are meant to be preventative, and we should almost never block anyone for failing to make an edit.  In particular, I shouldn't be able to get someone blocked just by dumping a 101 kB wall of text on their talk page next time they take a holiday. Certes (talk) 13:58, 11 January 2024 (UTC)
 * If they’re on holiday, they wouldn’t be able to respond to a request for archiving and won’t get blocked, plus dropping a wall of text would probably be against some policy by itself. Aaron Liu  (talk) 14:01, 11 January 2024 (UTC)
 * I would hope any sysop would just ignore the block request under IAR, even if they don't consider 101kb disruptive editing. Sincerely, Novo TapeMy Talk Page 02:09, 15 January 2024 (UTC)
 * Support in some formulation. The variability in computing power and other factors that impact opening such pages makes specific limits difficult to pin down. What should happen is that someone notes they have an issue accessing a page, and in response that issue is resolved. That this does not happen, despite much previous attention to the matter, means apparently a policy is needed (a similar point was made above by The Hand That Feeds You). I'm not sure Wikitext is the best metric for addressing issues (variability etc.), given there are other items that can cause lag, but it seems a better proxy than having nothing. I'd consider a certain number of talkpage sections as another proxy. Agree the signature precedent works here, for things that appear minor but are long-term disruptive. CMD (talk) 01:28, 10 January 2024 (UTC)
 * Oppose. Wikipedia is not a bureaucracy, and user talk pages are also the most important locus of our community. Advocating for roving policing of people's talk pages, not even for content but for length, will be corrosive to that community beyond its benefits, which are debatable: note the wide range of experiences loading EEng's talk page reported both at AN/I and here (including Ritchie333's own mention here that he was able to leave a note on the page, but had to wait longer than is recommended in usability guides). And I struggle to see how it can be anything but a huge legislated exception to WP:TALKO;, you claim above that it would be in keeping with [its] Spirit, can you explain please? am I being dense? We may have a gathering problem with access for (some) cellphone users; I wouldn't know, I am fortunate enough not to have to use one to edit. We maybe should encourage users to create talk page subpages and move the season's greetings templates, convivial/joke discussions, and things that some editors have on their talk pages instead of their suer pages such as transclusions of Main Page sections, RfA and and deletion alerts, and highly formatted achievement lists to those, leaving the main talk page for businesslike discussions, Contentious Topic alerts, AN/I notices, and the like. We could also deprecate fancy borders, slanting text, and floating widgets on user talk pages as opposed to user pages. But as it is we don't even strongly suggest archiving rather than blanking, which makes checking an editor's history difficult. Implementing this proposal will be a huge change from the status quo and will disproportionately affect editors who collaborate, who respond to concerns raised on their talk pages, and who are sought out for advice and discussion, and won't impact those who seek to escape answerability by simply deleting ... or who haven't been around long enough to discover that talk pages are more than where templates get dumped informing you you did something bad. To start with, please: more polite requests to people to archive. And maybe an easy help page on setting up auto-archiving, if there isn't already one? ( Someone set it up for me many years ago, back when I didn't even realise those numbers in the history of the page were byte counts, and I am only slightly more technically competent now; can anyone explain how you get a double column of archive numbers in the display box, rather than the great long tail I've got? ) IOW: substantially per Trypto. Yngvadottir (talk) 09:57, 10 January 2024 (UTC)
 * Perhaps Paradoctor means that the meaning isn’t changed? Notburo means that most rules do not need to be strictly adhered to, not that we shouldn’t regulate things. Yes, it disproportionally affects people who don’t remove stuff from there talk pages, and how is that bad? There are already a bunch of guides on archiving. Help:Archiving (plain and simple) is the short, default version, while Help:Archiving a talk page is the longer, configurable version. By default, archives will automatically format subpages into columns. Aaron Liu  (talk) 14:09, 10 January 2024 (UTC)
 * am I being dense? [...] problem with access for (some) cellphone users; I wouldn't know, I am fortunate enough not to have to use one to edit. [...] Someone set it up for me many years ago
 * Well...
 * Irony aside, it's good to see that you acknowledge that you are privileged in that respect. I'm getting the feeling, though, that you don't realize that puts you ahead of others. About two out of three users use phones to access Wikipedia. You can bet your ass that a significant fraction of them is lucky to use old/low end hardware.
 * Accessibility is not merely a nicety. In effect, it is the prime goal of this project: make existing knowledge accessible to everyone. Technical accessibility is an indispensible prerequisite for that. Can't access knowledge if you can't display it, now can you? (Or listen to it, if that works better for you.)
 * If you mention WP:NOTBURO, you should always mention WP:NOTANARCHY/WP:NOTDEMOCRACY.
 * more polite requests to people to archive That's reasonable. So we modify the proposal to say that setting up archiving should be preceded by asking the user to do it themselves beforehand. That do it for you? <span style="display:inline-block;position:relative;transform:rotate(-3deg);bottom:-.1em;">Paradoctor (talk) 15:20, 10 January 2024 (UTC)
 * I can't let this go without pointing out that the statistic on accessing Wikipedia above is just that ... it refers to reading, not editing. This discussion concerns user talk pages, which aren't even indexed by search engines. The sometimes quite long wait while my browser loads some of our increasingly template-heavy articles (and the issue of accessibility to screenreaders of those articles) is not the focus of this discussion, but yes, it's ironic from one perspective. Part of my point was that apparently even EEng's user talk page does not present an insurmountable obstacle to those using less than current mobile tech, rather than the less than current desktop and laptop tech I use. We should distinguish between impossibility and difficulty / slowness; but I do recognize that some have said the page crashed their browsers. Yngvadottir (talk) 22:23, 10 January 2024 (UTC)
 * We have existing guidelines and practices in place to deal with articles. We know specifically that template-heavy articles break things (WP:PEIS). I've even seen editors substitute citation templates to reduce the load on an individual page. There's no irony and no need to focus on that, because those processes already exist. CMD (talk) 01:39, 11 January 2024 (UTC)
 * I'm curious, how do you substitute a cite template? Last time I tried that I got "empty citation". Or do you mean changing it to a template-less format? Aaron Liu  (talk) 02:23, 11 January 2024 (UTC)
 * That is one option. I've also seen editors wrapping citation templates in an #invoke...| function specifically to avoid PEIS (Help:Template says this doesn't work, whether the people using it know otherwise I'm not sure). CMD (talk) 03:16, 11 January 2024 (UTC)
 * @CMD What Help:Template is trying to say is that if you wrote a module that just called the cite web template and spat out the output, it wouldn't reduce PEIS. However, since cite web is aready a wrapper for, replacing it with a direct call to does cut the PEIS in half. --Ahecht ([[User talk:Ahecht|<span style="color:#FFF;background:#04A;display:inline-block;padding:1px;vertical-align:-.3em;font:bold 50%/1 sans-serif;text-align:center">TALK
 * Thank you, that's very clarifying. CMD (talk) 09:16, 3 February 2024 (UTC)
 * In fact, Tamzin made a wording that includes the last part. Aaron Liu  (talk) 16:10, 10 January 2024 (UTC)
 * I actually agree with you about most of that, but being able to load a talk page is critical to its use for collaboration, no? If I can't write to you, it's a real problem. I've noted my opposition to the third-party-bot-archival above, but the size limit itself I see as no different from (for instance) requiring your posts not be in colors and fonts that are inaccessible. Vanamonde93 (talk) 19:50, 10 January 2024 (UTC)
 * 100% agree. critical part of collaboration. And on the theoretical arguments brought by Yngvadottir. We have all of this: User_pages with things that people seem to really care about ppl not doing on their pages, so I don't see the problem with adding one more rule. There already is plenty bureaucracy on Wikipedia we are not crossing some sort of magical line in that regard. —Th e DJ (talk • contribs) 09:47, 12 January 2024 (UTC)
 * Oppose Insofar as there's a technical problem, it's a general one with all types of page – see Database reports/Long pages. This general problem should be addressed in a general way as a standard part of the MediaWiki software which is supported by a huge technical staff who are paid to solve such problems.  For example, if a page is large then perhaps the interface software should offer the reader an option of delivering it section by section or with dynamic pagination.  Ad-hoc local kludges are a bad idea because they generate complexity and confusion across the projects and languages.  Volunteer users should not be harassed or burdened by this in the meantime, per WP:BURO, WP:CHOICE, WP:CREEP, etc. Andrew🐉(talk) 10:25, 10 January 2024 (UTC)
 * "This general problem should be addressed in a general way as a standard part of the WikiMedia software which is supported by a huge technical staff who are paid to solve such problems." It SHOULD, but the odds that it WILL are, in my view, about as likely as Boris Johnson being a credible and trustworthy politician. <b style="color:#7F007F">Ritchie333</b> <sup style="color:#7F007F">(talk) <sup style="color:#7F007F">(cont)  11:54, 10 January 2024 (UTC)
 * Do we see graphs working? Dynamic talk pages, aka Flow, were abandoned and deprecated. We can’t hope on the WMF to do this in the near future. Aaron Liu  (talk) 12:07, 10 January 2024 (UTC)
 * huge technical staff who are paid to solve such problems Nice theory. Doesn't work that way, but it's a nice thought. <span style="display:inline-block;position:relative;transform:rotate(-3deg);bottom:-.1em;">Paradoctor (talk) 15:28, 10 January 2024 (UTC)
 * The Discussion Tools extension was created by the WMF Editing team as part of MediaWiki and seems reasonably successful. That has been implemented across all the projects, as I understand it, and it's obviously sensible to make such functionality a common standard rather than having each project create its own kludges.  We just need to engage with people like  and  to explain the issue and see how they plan to address it. Andrew🐉(talk) 23:50, 10 January 2024 (UTC)
 * The technical solution here would be lazy loading of sections, which both is complex to implement and presents a worse user experience on pages that are not extremely long, as it interferes with Ctrl-F and makes jumping to sections more difficult. That's not to say it's impossible such a thing would be implemented in MediaWiki, but we should not expect it to happen. AntiCompositeNumber (talk) 22:53, 11 January 2024 (UTC)
 * It has already been done. This morning I was using my phone to browse Wikipedia in bed, as I often do before rising.  I tried EEng's talk page and it loaded almost immediately.  The display offered me a scrolling list of section headings which could be expanded as needed.  And there was a prominent button should I want to send him a message.  This is the standard mobile interface which is designed for such mobile devices and seems to work fine in this case.
 * The problem here seems to be that some editors are using non-standard interfaces such as Convenient Discussions. I'd never heard of this thing before and it turns out to be a kludge on Commons, not even hosted by the English Wikipedia.  We cannot be expected to cater for every conceivable piece of alien, external technology.  Users should stick to the standard interfaces provided and, if they don't, they should accept responsibility for any resulting difficulties.
 * Andrew🐉(talk) 10:25, 12 January 2024 (UTC)
 * No, that is not the problem. I just tried on a desktop incognito tab and it was over 10 seconds before I could click the new section button. (That said, this is a qualitative improvement over the last time I tried.) Many people have pointed out they have issues, at least honestly say it's not something important rather than inventing reasons on their behalf. CMD (talk) 11:09, 12 January 2024 (UTC)
 * I am not the only one who has had difficulties, with or without scripts. The mobile site and desktop site load in about the same time for me without userscripts. Just having collapsible section is not lazy loading; everything is already loaded. Aaron Liu  (talk) 12:06, 12 January 2024 (UTC)
 * Sure CD aggravates the symptoms, but the main points stand both with and without CD usage. —Th e DJ (talk • contribs) 12:14, 12 January 2024 (UTC)
 * Bear in mind that EEng has been archiving some discussions piece by piece since this came up so we are not dealing with the page as it actually was. —DIYeditor (talk) 14:06, 12 January 2024 (UTC)
 * Oppose - I briefly explored the possibility of automatically setting up auto-archiving on all content talk pages here. After consideration, I came to the view that the opposers were correct. Talk page text (including on user pages) can serve as a convenient source of information. Also, any size-based constraint is arbitrary if it doesn't take other media into account. Riposte97 (talk) 10:45, 10 January 2024 (UTC)
 * "Talk page text (including on user pages) can serve as a convenient source of information." ... unless your iPhone 5S (that is all you can afford) displays "This page cannot be loaded because a problem repeatedly occurred". <b style="color:#7F007F">Ritchie333</b> <sup style="color:#7F007F">(talk) <sup style="color:#7F007F">(cont)  13:01, 10 January 2024 (UTC)


 * a handful of devices will outright start overheating (my work pc in particular slows down to a crawl and blue screens in around 2 minutes) when exposed to unnecessarily heavy pages like eeng and tagishsimon's talk pages for too long. my phone just takes way too long to load and render them (and also overheats to the point where it hurts to hold ow ouchie), but i hear other people's phones haven't been able to fully load them without errors at all
 * that's just flat out not good for keeping hardware usable
 * keeping wikitext under an arbitrary amount seems easy enough, but a small handful of lines could potentially still have a whole bunch of other heavy shit load, so i don't think there's a way to do it with only bots
 * so i support keeping talk pages, as rendered by an average pc or phone at this current time (i'll assume windows 10, android 9, and ios 13) and the view point of an ip (so no wacky gadgets, no superior dark mode, but maybe test under both desktop and mobile modes), under a memory usage threshold like 200-300 mb or something, and cutting down whatever might be clogging it the hardest. that number might still be highballing it (this page is only currently using around 100 mb, for example), but the problem is already complicated enough as is, so i really don't know if anything here would be possible to quantify in guideline format
 * tldr: heavy pages (in terms of total things loaded, not total wikitext) make my phone and work pc cry, make them do less of that pwease  cogsan (nag me)  (stalk me) 12:41, 10 January 2024 (UTC)

The worst performing talk page I've seen yet is User talk:Wolfgang8741 which causes Safari on macOS Ventura running on a 2020 M1 Mac mini to lock up for a second or two. <b style="color:#7F007F">Ritchie333</b> <sup style="color:#7F007F">(talk) <sup style="color:#7F007F">(cont)  13:14, 10 January 2024 (UTC)
 * I just tried that talk page and it worked for me, albeit sluggishly. In that case, it seems that much of that page is weekly newsletters, especially Wikidata weekly summary.  I've signed up to a few such newsletters and it's a chore to clear away the old ones every time a new one arrives.  Their default behaviour ought to be to do this automatically - removing the previous newsletter when posting the latest one.  Such newsletters can link to a central archive, in case editors wish to read back issues, but there's no need to duplicate the content of every issue across many talk pages and archives.  I don't want these cluttering up my personal archives and so just delete the old ones. Andrew🐉(talk) 23:30, 10 January 2024 (UTC)
 * I think such newsletters should be unquestionably archived at sight automatically, see the top of my talk page for how to configure that. Aaron Liu  (talk) 23:41, 10 January 2024 (UTC)
 * Aaron Liu seems to have a bot configured so that every time a newsletter arrives on his talk page, it is then copied to another user page and deleted from the talk page. I don't want that behaviour.  What I'd like is for the original bot that posts the newsletter to remove the previous issue in the same edit -- a one in, one out policy.  Creating additional bots to clean up after the first bot is inefficient and over-complex. Andrew🐉(talk) 00:08, 11 January 2024 (UTC)
 * Ah. Well, on the technical side, that would require a bit more work on the part of message delivery. Such messages are not sent by a bot, but by an extension that simply adds more wikitext to a list of pages. That would introduce a ton of new maintenance in that suggestion and introduce new goals, so such a feature would be better left done by something external instead (at least from the perspective of me, a unix philosophy liker). Aaron Liu  (talk) 02:28, 11 January 2024 (UTC)


 * Oppose opting anyone in to any sort of bot list. If a talk page is technically disruptive due to size, just trim it (i.e. archive to history). — xaosflux  Talk 15:12, 10 January 2024 (UTC)
 * So you're not opposed to archiving other user's pages, just as long as it is done ?!? <span style="display:inline-block;position:relative;transform:rotate(-3deg);bottom:-.1em;">Paradoctor (talk) 15:30, 10 January 2024 (UTC)
 * @Paradoctor I think it should be handled on a case-by-case basis, when there is significant disruption - and suggest that it is just done by archiving to history instead of creating even more copies of the text. — xaosflux  Talk 16:11, 10 January 2024 (UTC)
 * Even worse. SMH <span style="display:inline-block;position:relative;transform:rotate(-3deg);bottom:-.1em;">Paradoctor (talk) 16:23, 10 January 2024 (UTC)
 * A golden rule of volunteers (and their bots) is that you should never rely that a future action will be made by someone else - if you think an edit is important to do, do it yourself. — xaosflux  Talk 16:51, 10 January 2024 (UTC)
 * Now it's spinning. <span style="display:inline-block;position:relative;transform:rotate(-3deg);bottom:-.1em;">Paradoctor (talk) 17:10, 10 January 2024 (UTC)
 * what is that supposed to mean Personally, archives are better than deletion as I can just search for something. Aaron Liu  (talk) 17:13, 10 January 2024 (UTC)


 * I've left that user a message at User_talk:Wolfgang8741 - perhaps they just don't know. — xaosflux  Talk 15:19, 10 January 2024 (UTC)


 * Has anyone talked to the editors who keep large talk pages (and choose not to archive) to ask them why they do so? Perhaps there is a reason why they don’t archive. Blueboar (talk) 15:29, 10 January 2024 (UTC)
 * Of course there is. Setting up archiving is a not completely insubstantial task for those comfortable with scripting / researching new tasks. For the vast majority of the rest, it's a major hurdle without (sufficient) support.
 * Make it a checkbox on userpages, and the problem goes away. Better yet, make it the default. Apart from a handful of adventurous non-conformists, I don't see anyone turning off archiving on purpose. <span style="display:inline-block;position:relative;transform:rotate(-3deg);bottom:-.1em;">Paradoctor (talk) 15:37, 10 January 2024 (UTC)
 * To set up Lowercase Sigmabot archiving, add  at the top of your talk page. I think it was harder to format this post than for a new user to set up archiving. <b style="color:#7F007F">Ritchie333</b> <sup style="color:#7F007F">(talk)  <sup style="color:#7F007F">(cont)  16:44, 10 January 2024 (UTC)
 * Sigmabot is the worse but faster one. For cluebot do  Aaron Liu  (talk) 17:02, 10 January 2024 (UTC)
 * Curse of knowledge. <span style="display:inline-block;position:relative;transform:rotate(-3deg);bottom:-.1em;">Paradoctor (talk) 17:08, 10 January 2024 (UTC)
 * It’s a repeat of the instructions at Help:Archiving (plain and simple). Aaron Liu  (talk) 17:14, 10 January 2024 (UTC)
 * SMH <span style="display:inline-block;position:relative;transform:rotate(-3deg);bottom:-.1em;">Paradoctor (talk) 17:26, 10 January 2024 (UTC)
 * I have been successfully confused. Aaron Liu  (talk) 17:49, 10 January 2024 (UTC)
 * Not my intention. But I still can't help you there. If what I've already said won't work, more of the same won't either, right? <span style="display:inline-block;position:relative;transform:rotate(-3deg);bottom:-.1em;">Paradoctor (talk) 18:07, 10 January 2024 (UTC)
 * I don’t get what you mean, I already have archiving set up. Aaron Liu  (talk) 18:23, 10 January 2024 (UTC)
 * Yes, I have seen this question asked of editors. The primary response I have seen is that the editors prefer to archive manually. Sometimes they are picking-and-choosing what to archive; sometimes they are using a specific structure for their archives and presumably prefer to control this manually. Some editors like to keep threads on their talk page as a prompt to review them (DGG I believe fell into this category). One editor didn't seem to like any discussion page being archived, as it made it harder for them to find older threads on them (as I recall they used more flamboyant language). isaacl (talk) 19:54, 10 January 2024 (UTC)
 * That's my position. When my talk page started to get large, I looked at archiving tools but they seemed confusing and klunky so I have been curating it manually.  The main thing I'd like is a way of editing such pages at section level, like the high-level view of an inbox in an email interface.  I could then manage the page at section level, selecting specific sections for actions such as deletion or moving.  I have the impression that there's OneClick tools that might do this but it's also my impression that such homebrew tools are unreliable and klunky.  I want a professionally supported and universal MediaWiki feature, please. Andrew🐉(talk) 10:40, 11 January 2024 (UTC)
 * No, userscripts are not clunky. They have been accumulating development since 2013, and I don’t trust that the feature request for moving will be implemented soon. Aaron Liu  (talk) 12:28, 11 January 2024 (UTC)
 * Thanks for finding and linking to the Phabricator ticket for that feature. I'm not understanding your reference to 2013 though.  Surely user scripts have been around for much longer as all early development was done by volunteers?  The page User scripts was created in 2005 and, now I look, I see there that there's a long list of them.
 * The list indicates the number of users of each script but doesn't seem to have any kind of quality rating. I'm quite wary of code that hasn't been through an approval and QA process as there's a lot of malware out there.  In my limited experience of such scripts, they usually warn that they can't be trusted and some of the scripts that I've found useful in the past are no longer supported and don't work any more.  Now that there's a professional support organisation for this system, we should use it.  "Why keep a dog and bark yourself?" Andrew🐉(talk) 20:17, 11 January 2024 (UTC)
 * User:Evad37/OneClickArchiver's history traces back to 2013.While I understand the concern about code quality, as the self-appointed editor of WP:Scripts++ for the last month, I can attest that there is no malware on US/L. Scripts that are productive enough usually get featured into an issue of S++. I feel like allowing any user to edit a script's rating at US/L would create chaos. Aaron Liu  (talk) 21:06, 11 January 2024 (UTC)
 * If any popular script had malware, you'd probably know about it because the account holder of the script would be globally locked by the WMF. As long as the script is open source, there are easily enough techies around to be able to review code reliably. See Linus's law. Ironically enough, I sort of agree with Andrew with respect, as I can't see the source code, and started coding an open-source replacement in case it ever went offline. <b style="color:#7F007F">Ritchie333</b> <sup style="color:#7F007F">(talk) <sup style="color:#7F007F">(cont)  11:45, 12 January 2024 (UTC)
 * I just looked at the OneClickArchiver page and it says  My experience with other scripts indicates that, if there's a problem, one can wait forever for a resolution.  These javascript hacks seem to be a big vulnerability so I prefer to wait for something that is safer and supported.  No-one should be forcing such scripts on other editors because of the issue of responsibility.  You can't be responsible for a script that you have been forced to use and don't understand. Andrew🐉(talk) 22:07, 12 January 2024 (UTC)
 * Every script has that. Maybe you're just extraordinarily patient, but I'm tired of waiting for the WMF to finish this giant list Aaron Liu  (talk) 21:07, 13 January 2024 (UTC)
 * Question (mostly rhetorical): how do you ask someone to shorten their talk page, without making the talk page even longer? I've been thinking about this discussion, and the more that I think about it, the more I'm becoming annoyed with those editors who are Oh So Upset at the thought of other editors with lengthy talk pages. (Find some content to improve. Or get a life.) This is a genuine issue only to the extent of when an editor wants to post something at another editor's talk page and cannot, because the talk page length causes a computer problem that makes the amount of effort needed impractical. It doesn't mean that the page loaded a little more slowly than some other pages (oh, the horror). I've been thinking about my own posting at EEng's talk page, and it's never been a matter of anything worse than being just a little bit slower than average for me, which makes me suspect that some editors have been exaggerating how difficult it was for them. Above, I posted a permalink to the talk page of the late DGG:, which I've repeated here for convenience. DGG was a long-time admin, and was a member of ArbCom. Throughout that time, his talk page was long, as in that link. That's easily in the same ballpark as EEng's talk page has been. But it was not a Big Awful Issue while DGG was elected by the community to positions of trust and respect. Why, editors who needed to communicate with him about administrative or ArbCom matters were even able to do that! We don't need to make any changes in policy over this stuff. --Tryptofish (talk) 19:39, 10 January 2024 (UTC)
 * "We don't need to make our entrance wheelchair accessible. We haven't had a single customer in a wheelchair come in here in the past ten years, so that would be a total waste of money." <span style="display:inline-block;position:relative;transform:rotate(-3deg);bottom:-.1em;">Paradoctor (talk) 19:58, 10 January 2024 (UTC)
 * You don't know me in real life, of course, but I'm actually someone who has some disabilities, and I actually won a lawsuit under the Americans with Disabilities Act. What we are discussing here is not about accessibility for people with disabilities. (Yes, someone who needs to use a screen reader might encounter issues with a long talk page, but they also encounter a lot worse with WMF software.) --Tryptofish (talk) 20:08, 10 January 2024 (UTC)
 * Then you should be aware that disability is often caused by the environment rather than by the impairment. And you're ignoring several comments stating they couldn't access these pages. <span style="display:inline-block;position:relative;transform:rotate(-3deg);bottom:-.1em;">Paradoctor (talk) 20:20, 10 January 2024 (UTC)
 * Wow, just wow. --Tryptofish (talk) 20:57, 10 January 2024 (UTC)
 * Respectfully, @Paradoctor, the analogy of poor hardware with disability seems to be in rather poor taste.
 * Taking your point, though, to what extent do we make allowances? Should we set guidelines such that a first-generation iPhone being operation halfway up Everest should be able to load every Wikipedia page within a second? I'm yet to see much in the way of concrete metrics here.
 * I am loathe to set yet another vague guideline which some overzealous admin will inevitably use as a cudgel. Riposte97 (talk) 10:20, 11 January 2024 (UTC)
 * Respectfully, look up "social model of disability". You can keep whatever lesson you learn from that. Just don't start a discussion with me here, that's OT. If you really need to, you can do so at my talk. <span style="display:inline-block;position:relative;transform:rotate(-3deg);bottom:-.1em;">Paradoctor (talk) 15:24, 11 January 2024 (UTC)
 * I interpreted the above comment as being in the theme of survivorship bias rather than specifically about accessibility for disabled people. As in, perhaps the lack of complaints about DGG's talk page on his talk page is due to those who would have a complaint not being able to leave a message at all. JoelleJay (talk) 04:45, 14 January 2024 (UTC)
 * Even if it was about what you call survivorship bias, that doesn't justify the reply to me. And as for your wild speculation about DGG, I'm not seeing that EEng's detractors had any difficulty finding places where they could complain about his talk page. --Tryptofish (talk) 21:56, 14 January 2024 (UTC)
 * The comment seemed like a pretty straightforward analogy to me. You were the one who brought up successful posts to DGG's large talk page as evidence that the size wasn't a problem for people. I'm simply (back)translating Paradoctor's analogy to that particular scenario. JoelleJay (talk) 02:37, 18 January 2024 (UTC)
 * After I had explained, in response to what you call an analogy, that in real life I am a person who lives with disabilities and that I had been discriminated against because of it, the proper reply would not have been that I am at fault for supposedly not being aware of what people with disabilities face. I don't want to drag this part of the discussion on for so long, but I also don't think that I should have to explain to people how offensive that was. --Tryptofish (talk) 19:27, 18 January 2024 (UTC)
 * I was responding to your misapprehension of the analogy (that it was implying the "long talk page" issues actually had anything to do with, or were being compared to, disability, when really it was simply invoking a perfectly apt example of non-response or coverage bias). I had hoped that clarifying the intent of that analogy would make you feel less personally targeted and alleviate some of the tension. JoelleJay (talk) 03:00, 19 January 2024 (UTC)
 * I didn't misapprehend anything. Those of us who oppose rigid rules about user talk pages are not doing so as non-response or coverage bias. --Tryptofish (talk) 21:06, 19 January 2024 (UTC)
 * Then why did your response to the analogy completely miss the point and go in an unrelated, personalized direction? And what you said about "no one having complaints about DGG's talk page" literally is non-response bias... JoelleJay (talk) 19:46, 20 January 2024 (UTC)
 * Here's a non-response for you. I'm not going to respond to this any more. --Tryptofish (talk) 20:19, 20 January 2024 (UTC)
 * I am not exaggerating when I say that it requires over 20 seconds to load EEng's talk page with the userscript Convenient Discussions. I should not have to suffer for WMF's snail pace at implementing features into DiscussionTools, and yes, it has been quite annoying to post on EEng's talk page, whether it's an edit conflict that freezes up everything, the fact that I have to wait for scripts to finish loading, or the 500+ MB of memory usage it brings. Janitors are good people, and they should not be seen as bad police. There's no reason to antagonize change to help people improve the encyclopedia. You can never measure something (analog) without changing it. Making the talk page longer is not a problem; people are already asking people to archive.  Aaron Liu  (talk) 21:04, 10 January 2024 (UTC)
 * Twenty seconds? That's what you're complaining about? Was there someplace you had to go in a hurry? --Tryptofish (talk) 21:08, 10 January 2024 (UTC)
 * Ok, thanks to you, I've actually went ahead and measured it. On my Ryzen 2700 with 16 gigs of RAM and an RX 580, it takes a minute and three seconds, expending 611 MB of RAM. Even twenty is a ton of an annoyance when you just want to post a message. And I have "improve performance of long pages" checked in CD settings. Aaron Liu  (talk) 21:12, 10 January 2024 (UTC)
 * Thank you for testing that. Yes, that's a disturbingly long time, I agree. It's also vastly longer than anything I've experienced there. This is why I've been saying that we need to base this on empirical data, and not on impressions. If you are interested in further testing, I have a suggestion. I'm completely sincere about this. Do the same test for Sissinghurst Castle Garden. I've picked that page because it's a Featured Article (one that I co-wrote), that fully complies with Wikipedia's norms, and which is rather long in text, and also has a significant amount of images. My guess is that it will be quicker than EEng's talk page, but non-zero for your system. I'm genuninely interested in how different it will be. --Tryptofish (talk) 21:55, 10 January 2024 (UTC)
 * Thanks. That article takes milliseconds to load on my iPad, but it’s not a talk page. Let’s say ANI instead. It takes two seconds to load on my iPad (both tests in V22). Aaron Liu  (talk) 22:01, 10 January 2024 (UTC)
 * That, you say, is on an iPad, but your data for EEng's talk is from a Ryzen 2700. We need to compare on a single device. --Tryptofish (talk) 22:05, 10 January 2024 (UTC)
 * My PC is faster than my iPad in this case. My PC also takes 2 seconds to load ANI and milliseconds to load the article, while my iPad takes 1 minute and 21 seconds to load EEng's talk page. Aaron Liu  (talk) 22:31, 10 January 2024 (UTC)
 * I'm trying to figure this out. My own PC, which is now a couple years old and I've been thinking about replacing it, loads the article and ANI in barely a second, and EEng's talk in maybe 4 seconds. My PC is running Windows 10 (and the current version of Firefox), with a 3.4 GHz cpu and 8 GB RAM, and I have a pretty fast broadband connection. I'm not sure how to account for how you and I get such different results for his talk page. As I've said from my first comment here, I actually do support the need for editors to be able to communicate with one another. I realize that this means that we have to allow for the fact that different people have different resources, and some people have slow systems that are not the state of the art, and that's OK. On the other hand, there comes a point, I think, where the burden does not rest entirely on the editor whose talk page it is, but also, to some extent, with the editor who has a slow system – the tricky part is how to be fair about that, from a policy perspective. --Tryptofish (talk) 22:47, 10 January 2024 (UTC)
 * I have said several times that I use a talk page–enhancing userscript. Anyways, lower-tier devices should also be considered, and some people have expressed that they encounter significant difficulties with EEng's talk page.Either way, 350 kb is definitely too much, even just to navigate. Aaron Liu  (talk) 23:08, 10 January 2024 (UTC)
 * Is the script the reason that it runs slower for you? If so, there may be a way to troubleshoot that script, which could be beneficial regardless of what goes on with talk page policies. About navigating long user talk pages, Template:Skip to top and bottom is very useful. --Tryptofish (talk) 23:16, 10 January 2024 (UTC)
 * The script does some UI transforming that threads everything. It's a design limitation. Going all the way through with archiving is better than scaffolding. Not to mention some users do experience much bigger problems on much lesser hardware, which aren't outdated enough to warrant not considering. Aaron Liu  (talk) 23:28, 10 January 2024 (UTC)
 * When you say that the script does that, is that in the edit window (as in threading edits automatically), or on the display of the page itself, while loading? If it's the latter, then that's almost certainly the reason for the slowness. --Tryptofish (talk) 23:42, 10 January 2024 (UTC)
 * The display, and I'm pretty sure this is the sixth time that I've said the script is a large contributor to the slowness, and that this doesn't void the argument much. Aaron Liu  (talk) 23:43, 10 January 2024 (UTC)
 * OK then, that's clearly the explanation. So for his talk page, it takes loading time from a couple of seconds to well over a minute. As I said just above, I think it's important that we pay close attention to making user talk pages usable for editors with a wide variety of systems, including keeping things accessible for those editors with systems at the slower end of the spectrum – but I also don't think that this should be an absolute, where the editor whose talk page it is, has all the responsibility, and the editor coming to the talk page has zero responsibility. I think the proprietor of the talk page should have the primary responsibility, and if editors want to make changes to policies or guidelines about this, then the issue to be examined thoughtfully is how to get that balance right. --Tryptofish (talk) 23:52, 10 January 2024 (UTC)
 * Yeah, I agree. 350kb seems like enough leeway to me, though, and there's no use keeping such a long talkpage anyway. Aaron Liu  (talk) 23:57, 10 January 2024 (UTC)
 * see my comment somewhere above this one for why something taking a lot of time and memory to load is not very #awesomesauce for a device's lifespan, and why heavy pages being slow and clunky is only the more immediately notable half of the problem  cogsan (nag me)  (stalk me) 21:46, 10 January 2024 (UTC)
 * Support a limit in some formulation, since WP:UOWN's provision that user pages are part of Wikipedia, and exist to make collaboration among editors easier applies equally well to user talk pages. That limit should be generous, though — certainly not lower than 200k. I've haven't read the discussion about implementation details above enough to have a view on it. &#123;{u&#124; Sdkb  }&#125;  talk 19:57, 10 January 2024 (UTC)
 *  Oppose More harm than good.   And we skipped past a simple notification and advice/request.   Or a place to ask for somebody to set your page up for archiving.    This would solve almost all of them. <b style="color: #0000cc;">North8000</b> (talk) 20:29, 10 January 2024 (UTC)
 * Query: How do y'all say we start over with Tamzin's wording? It seems that many are calling for things incorporated in that wording and assuming the original proposal's wording to be the only wording that'll be implemented. Aaron Liu  (talk) 21:04, 10 January 2024 (UTC)
 * Oppose. --Tryptofish (talk) 21:08, 10 January 2024 (UTC)
 * Based on your rapid fire responses and tone, I think you'd might want to calm down a bit. Aaron Liu  (talk) 21:12, 10 January 2024 (UTC)
 * I'm calm, really. You've made two separate replies so far, to my merely saying "oppose". Let me say to you, very seriously (and calmly), that what you proposed to start over with is unlikely to get consensus. But what I said does nothing to stop you from giving it a try. Instead of asking everyone else to come up with something from the start-over, you could actually formulate a proposal. --Tryptofish (talk) 21:19, 10 January 2024 (UTC)
 * The reply below about being an idea lab was conceived separately from your reply. I didn't see it when you were typing, else I would've consolidated my replies. I put in this query because I thought this was the proposal, not the workshop. I don't think there's much more to formulate besides simply starting it.My remark about calmness was not solely about your "Oppose" without a rationale. Besides that, you've jumped at the thought of people growing impatient because they have to wait twenty seconds to leave a message (and ignored my initial input on userscripts), threatened someone's reply with switching to a strong oppose, and ignored Paradoctor's telling you that you've been ignoring several comments that state that EEng's talk page is inaccessible. Aaron Liu  (talk) 21:35, 10 January 2024 (UTC)
 * I'm not the issue here. Please comment on the substance of the discussion, and not on the contributor. If you think I'm being disruptive, ANI is thataway. --Tryptofish (talk) 21:46, 10 January 2024 (UTC)
 * Hold up, the opening comment says that this was only an idea workshop. Aaron Liu  (talk) 21:08, 10 January 2024 (UTC)
 * Absolutely opposed to giving "any uninvolved editor" the right to play with another editor's talk page operation. This will just create disputes and become a method of harassment. Also, 100K is far too small for a guideline when we have articles at least 4 times more than 7 times that length. If a talk page is creating a problem, then leaving a friendly message should be the compulsory first step (as a standard template so that all such pages can be located easily), then if the problem isn't fixed an uninvolved administrator can take care of it. Zerotalk 01:06, 11 January 2024 (UTC)
 * But if it is too big to edit, then how is someone supposed to edit it to add the friendly message? As well as I know, we can have subpages of talk that aren't named archive. If someone really needs a big, but not archive page, they could make it a subpage, use it there, and put a link in the main talk page. The main page could then suggest adding new entries to the subpage, if possible. If someone can't, they can add to the main page. Gah4 (talk) 01:30, 11 January 2024 (UTC)
 * (1) Use a different browser, (2) write on your own talk page with a ping to the offending editor, (3) ask another editor to do it, (4) send email, (5) report it on a noticeboard. I.e., there are plenty of ways to get the attention of an editor apart from writing on their talk page. Also, I don't think there has ever been a talk page "too big to edit", unless some vandal made one. What there has been is a talk page that some limited number of people using particular software found too big to edit. Zerotalk 04:02, 11 January 2024 (UTC)
 * I can't access these talk pages on any of my devices using any browser. At this point, it's just restricting some editors to be able to use it. Chaotıċ Enby   (t · c) 20:53, 11 January 2024 (UTC)
 * Regardless of 100k, 350k should be enough, no? WP:TALKO is another guideline where editors can fix bad things from other users, and I don't see why this should be treated much differently.Note that this is a workshop, and so far I don't see much people opposed to Tamzin's amendment. Should we add a section break with this information? Aaron Liu  (talk) 02:44, 11 January 2024 (UTC)
 * No, 350K is not enough and seems to be an arbitrary hard limit chosen for no particular reason. I recall corporate email systems that enforced such hard limits and they were quite vexatious.  There was general relief when we moved to cloud-based systems that had no limit.  That's the general trend of technology – to provide ever increasing capacity.  We should make our technology more advanced, not less.  That's our policy. Andrew🐉(talk) 09:40, 11 January 2024 (UTC)
 * I don’t think the limits of single emails are much of a comparison. Aaron Liu  (talk) 12:30, 11 January 2024 (UTC)
 * When I started at one corporation, their email system restricted standard users to just 100 saved messages -- emails would bounce after that. But that was in the 20th century.  They've moved on since. Andrew🐉(talk) 12:01, 12 January 2024 (UTC)
 * Support in some formulation. Large talk pages have crashed/frozen the tab in my laptop's browser before. 100k seems like a reasonable maximum size (supports about 100 sections). Any editor being allowed to add or modify an archive bot config template to summon an archive bot at that size seems reasonable to me. – Novem Linguae (talk) 02:16, 11 January 2024 (UTC)
 * You have very short talk page sections. Mine average 2380 bytes and there is nothing unusual about them. Zerotalk 04:22, 11 January 2024 (UTC)
 * True. Maybe it'd be a good idea to start with a higher number of bytes. From this list of largest user talk pages, #1 is 2 million bytes, #50 is 1 million bytes, #100 is 850k, #500 is 517k. Maybe we start with a 500KB limit, fix those 550ish talk pages, then see if it's still a problem. – Novem Linguae (talk) 05:11, 11 January 2024 (UTC)
 * I think talk page pruning should be enforced but strongly oppose "any uninvolved editor". Egalitarianism and sharing the load are good but we know that any uninvolved editor would end up meaning that opponents and SPA gnomes would use the rule to needle good editors. It would be better to require a polite non-templated request with a link to a standard explanation of the issue. If a repeat after two weeks does not get a good result, post a message at WP:AN. An uninvolved admin should do the pruning after giving the TPO another opportunity. That makes it impersonal and just a matter of how things are done. Johnuniq (talk) 03:24, 11 January 2024 (UTC)
 * Anything can be used to harass and abuse people. Aaron Liu  (talk) 12:36, 11 January 2024 (UTC)
 * Incidentally, from Special:LongPages I find that we have 46 articles above 500K, 255 above 400K, 1213 above 300K, and 5766 above 200K. The list doesn't go down to 100K but a plausible extrapolation is 25,000–30,000 articles above 100K. We need a very good reason to restrict talk pages to a size that we tolerate in a large number of articles. I'm wondering if we have any example of a talk page less than 500K which anyone with modern hardware and software cannot edit due to its size. Zerotalk 04:46, 11 January 2024 (UTC)
 * Interestingly, the two largest articles (>700,000 bytes) load much faster for me (in seconds) than any of the talk page examples listed in this discussion. If this experience is consistent for others, then that seems a good reason to treat the article and talk spaces differently, although I'm not sure what the cause of the difference is. CMD (talk) 05:21, 11 January 2024 (UTC)
 * User scripts and gadgets seem like they could be a cause of that. A user highlighter script could be performance intensive only on talk pages, for example. – Novem Linguae (talk) 05:53, 11 January 2024 (UTC)
 * I spot-checked those articles, and all the ones that I did are tagged with "This article is too long". <b style="color:#7F007F">Ritchie333</b> <sup style="color:#7F007F">(talk) <sup style="color:#7F007F">(cont)  09:59, 11 January 2024 (UTC)
 * I have 0 respect for users like this. Archive the page and if they don't like it they can use a different website. People thinking they have special privileges in this world, come on. Users need to be considerate towards others and this is clearly behaviour that is not considerate towards others. Archive, and move on, this is not THEIR website, they can host their own website and do whatever they want there. If we can tell people not to host any of the things listed here: User_pages then we can easily do this —Th e DJ (talk • contribs) 10:21, 11 January 2024 (UTC)
 * Support something - either a size limit and/or age limit. Somebody with more technical knowledge will need to suggest a size limit, but I don't see why any old threads more than a maximum 6 months need to remain on talk pages. I manually archive my own at least once a week. GiantSnowman 13:00, 13 January 2024 (UTC)

(Not quite) arbitrary break re talk page size
I've posted a notice of this discussion to WP:VPT. There's been a lot of productive discussion here and many valuable perspectives have been offered, but my impression from reading this discussion is that most people participating here became aware of this discussion by reading the ongoing ANI thread. There's nothing inherently wrong with that, but I think the perspectives of technical editors who may not check ANI regularly would be useful. Here are some questions I have (speaking only for myself, of course): As a side note, I checked Novem Linguae's query and was alarmed to see that EEng's talk page is only the 69th-largest user talk page at the time of this comment. I know the ANI thread regarding him was the precipitating incident that led to this discussion, but I'll take this opportunity to reiterate that I really don't want this discussion to be about him and his talk page&mdash;it seems to be a widespread issue and I don't think there's much to be gained from further anecdotal discussions of specific cases here. — Callitropsis🌲&#91;talk · contribs&#93; 05:52, 11 January 2024 (UTC)
 * Do we have any data regarding of the types of devices and applications people use to access and Wikipedia and how often they are used? If so, is this data broken down by namespace or type of action (e. g., editing pages versus merely viewing them)?
 * If such data exists, do we have a good idea of the download limits (that probably isn't the correct technical term, but whatever) of the slowest device/application combination that is regularly used to access and edit Wikipedia? If so, how does this (roughly?) correlate to size as measured by wikitext? (As noted above by Rhododendrites wikitext may not be the most reliable indicator of how quickly a page loads, but it seems like the simplest and most easily measurable metric and I think any formal guideline regarding talk page size should probably use it as a yardstick.)
 * Are there any additional technical considerations that apply to editing pages but not to simply viewing them? Similarly, are there differences between any of the commonly used tools for editing talk pages (standard editing window, VisualEditor, 2017 wikitext editor, DiscussionTools, Convenient Discussions, Factorum, etc.) in terms of performance and tolerance of large page sizes?
 * Apparently the average page on the web as of 2022 was 2.2MB. If we are having trouble with pages a fraction of that size, it isn't due to the amount of wikitext. Zerotalk 07:14, 11 January 2024 (UTC)
 * Seems like this might be an apples to oranges comparison. The total size of the wikitext of my user talk right now according to the history tab is 46 KB. But if you measure that by the amount of HTML generated (view HTML source -> copy paste it to a text file -> look at how big it is in File Explorer), it jumps to 363 KB. If you measure it by the total size of all assets, including images, js files, etc. (measured by opening DevTools -> going to network tab -> looking at "resources" in the footer -> hard refreshing) then it jumps to 7800 KB (7.8 MB). The 2.2 MB number in your citation is using the same methodology as the 7.8 MB number. The latter number will also vary based on whether you're logged in and how many user scripts and gadgets you are using.
 * These same stats for https://en.wikipedia.org/w/index.php?title=User_talk:EEng&oldid=1194559025, which is a user talk page with 298 sections, is 942 KB wikitext, 6.4 MB HTML, 27.7 MB all assets. Also, on my well spec'd desktop computer, scrolling to the bottom of the page took 16 seconds until text was visible, and 23 seconds for my user scripts such as my UserHighlighter to kick in. Maybe if I get curious I will retry this experiment on my laptop and my smartphone, but I can't imagine these numbers will get any faster on those less powerful devices. More likely things will lag more and/or freeze. – Novem Linguae (talk) 07:47, 11 January 2024 (UTC)
 * This is a good point. Introducing a hard limit measured in K seems quite laughable nowadays.  I downloaded an update for the navigation database of my car recently and it was about 100 Gb.  I did this on this same browser and same laptop that I use for Wikipedia.  It took a while but so it goes.  My smartphone has a memory size of 250 Gb but I'm planning to get a new one soon as it's becoming obsolete.  And the capacities of personal devices are starting to be measured in Terabytes now ... Andrew🐉(talk) 10:19, 11 January 2024 (UTC)
 * NL makes a good point. Perhaps we should ask the techies to give us a tool for html+images, as a more useful measure of page size. Zerotalk 10:44, 11 January 2024 (UTC)
 * I’m not concerned about the size of files embedded on a page. MediaWiki serves thumbs anyway. I also don’t see why we should compare the length of HTML code instead of Wikitext. Aaron Liu  (talk) 12:38, 11 January 2024 (UTC)
 * "It took a while but so it goes." This reminds me of something that Vincent Flanders wrote on his seminal webpagesthatsuck.com website about 25 years ago ... "Unfortunately, people won't wait for images unless they're of naked or dead bodies". <b style="color:#7F007F">Ritchie333</b> <sup style="color:#7F007F">(talk) <sup style="color:#7F007F">(cont)  10:58, 11 January 2024 (UTC)
 * The download for my car took about an hour to download and unzip and then an hour to install to the car. That required some care and patience but I've worked with software that took days to run.  But people seem to be freaking out here if they have to wait for a few seconds.  If they want instant gratification then they should stick to sites such as Instagram, TikTok and Twitter, which are explicitly designed for short-form content.  Wikipedia is an encyclopedia and so a sedate and scholarly pace is fitting.  Festina lente... Andrew🐉(talk) 23:02, 11 January 2024 (UTC)
 * Communication between editors should not be comparable to the installation of software. Aaron Liu  (talk) 02:22, 12 January 2024 (UTC)
 * That software update was measured in Gb and took hours. EEng's talk page is measured in Kb and takes seconds.  This difference is several orders of magnitude.  See Make a mountain out of a molehill. Andrew🐉(talk) 09:51, 12 January 2024 (UTC)
 * You are asking good questions, but these are all overly detailed, technical aspects that in the grand scheme just don't matter here and will only serve to facilitate discussion and create details for people to disagree about. In the end this is very simple, lot's of wikitext becomes way way more HTML, which will eventually cause very slow page loads and crashing browsers, with an easy and widely accepted solution... ARCHIVE the contents. We don't need to have 20 000 hours of wasted discussion, because we already know it's happening, people reported such. —Th e DJ (talk • contribs) 11:09, 11 January 2024 (UTC)


 * Support some formulation but not the invitation for any editor to just go modifying someone's talk page. It should be a reason to take them to WP:ANI and possibly have their refusal to archive it or use a bot looked into as disruption. —DIYeditor (talk) 16:11, 11 January 2024 (UTC)
 * Oppose - Didn't we just have a problem with certain editors policing userspace through WP:MFD? And now we want to do the same thing with user page lengths? Heck no. Any such rule should be a guideline and not a cudgel that bad-faith users employ to police other people's talk pages. Duly signed, ⛵ <span style="color: white; font-family: Verdana; font-weight: bold; background: linear-gradient(white, blue, navy, black)">WaltClipper - (talk)  17:55, 11 January 2024 (UTC)
 * Convenient Discussions apparently makes it much harder to load these talk pages. Chaotıċ Enby   (t · c) 20:56, 11 January 2024 (UTC)
 * Unsurprisingly, since it is 762K of compressed javascript. I think that people who add lots of bells and whistles to their download should expect it to be slower, and I don't think they should expect other people to modify their archiving to help them out. Zerotalk 12:03, 12 January 2024 (UTC)
 * Just because you find something that makes it even more annoying, doesn't take away that is already plenty annoying on its own. It's like a Ford F-650 for grocery shopping. Super annoying and unnecessary, even though it might fit. Get out of the way of others, stop being selfish or find yourself being regulated by community. —Th e DJ (talk • contribs) 12:22, 12 January 2024 (UTC)
 * That is, if we were the only ones having troubles. There are a lot more, and we should cut the curb to help everyone out. Aaron Liu  (talk) 12:37, 12 January 2024 (UTC)
 * I don't know of a lot of people have problems, nor do I know of any serious attempt to determine why they are having problems or whether the amount of wikitext is a fair measure of the amount of problems. Zerotalk 12:48, 12 January 2024 (UTC)
 * i don't think the amount of wikitext is the problem, honestly
 * 1 mb of plain ol' copypastas might be a little annoying to load, but 200 kb of templates, images, videos, and an mp3 file of some guy screaming about among us... that may be a little worse
 * unfortunately, i don't think it's easy to quantify that in guideline format when pretty much everyone with an account has gadgets  cogsan (nag me)  (stalk me) 13:04, 12 January 2024 (UTC)
 * Regardless, you shouldn’t need a talk page with over 350kb of Wikitext, even if it’s all plain text. Aaron Liu  (talk) 14:11, 12 January 2024 (UTC)
 * They are having problems because the page is giant. This isn’t too hard to eliminate as they don’t have trouble with this page or other user talks. Aaron Liu  (talk) 14:10, 12 January 2024 (UTC)
 * Oppose any lower limit than the size of WP:ANI, measured as its max size over the last year, and currently approximately 718kb. We should clean up our own house first before moving on to individual users. —David Eppstein (talk) 21:30, 12 January 2024 (UTC)
 * What‽ That is true! That doesn't make sense! Why would 100kb make that much of a difference? Is there an overabundance of templates at EEng's talk page? Aaron Liu  (talk) 21:40, 12 January 2024 (UTC)
 * David was joking. And so am I, when I say that we should block ANI for being so... um, what was I talking about? --Tryptofish (talk) 21:45, 12 January 2024 (UTC)
 * I don't feel like they were joking and they have a good point for why the proposed limit isn't a very good one. Aaron Liu  (talk) 21:47, 12 January 2024 (UTC)
 * Indeed. And ANI is just one of many large pages out there.  I try to avoid that one but often load ITN archives to check an old nomination.  These are quite large and correspondingly slow.  For example, In the news/Candidates/January 2023 is 945 Kb. Andrew🐉(talk) 22:18, 12 January 2024 (UTC)
 * ANI is now up to nearly 765k . And no, I'm serious: we should not make stricter limitations on individual user talk pages than we place on our big public noticeboards. The only valid reason presented here for such a limitation is technical: some people's browsers cannot handle it. That issue is, if anything, much more salient for public noticeboards than for individual talk pages, because many more editors have good reason for needing to access the public noticeboards. —David Eppstein (talk) 19:15, 13 January 2024 (UTC)
 * The very weird thing about this is that ANI loads in ~4 seconds while EEng's talk page loads in ~1 minute. Even logged out, ANI loads in ~3 seconds while EEng's talk page loads in ~14 seconds. I'm counting load time by the time it takes to get to the bottom and have the page be responsive. Aaron Liu  (talk) 21:03, 13 January 2024 (UTC)
 * David, my apologies. --Tryptofish (talk) 22:14, 13 January 2024 (UTC)


 * The main issue would seem to be the media loading on a large talk page -- a relative small page in terms of wikitext/HTML could still entirely consist of image galleries that'd overwhelm a browser, while a page that's 300kB of wikitext could be entirely innocuous. This makes deciding whether a page is "too big" sort of challenging when trying to set limits.
 * There's a technical solution to this, which is adding lazy-loading attributes to images . There were some historical issues with doing that (thus why we haven't), largely around it not working well when you wanted to print an article page, but I gather that progress has since been made on that issue by browsers... DLynch (WMF) (talk) 17:30, 17 January 2024 (UTC)
 * WebKit (Safari) still has the bug. Aaron Liu  (talk) 17:41, 17 January 2024 (UTC)
 * Thanks, DLynch, that's important information. In particular, it means that editors who have been analyzing this on the basis of the number of kb of plain text have been barking up the wrong tree. --Tryptofish (talk) 21:53, 17 January 2024 (UTC)
 * That still doesn't explain the giant difference when loading with userscripts. Aaron Liu  (talk) 22:05, 17 January 2024 (UTC)
 * Well duh. Of course the kb is just a lever to modify the problem. If you only used one long series of a's instead of words on the entire page, it would be even more efficient than not using images. There is not a single uniquely triggering issue here. If you fill a bucket with water, then throw pebbles in it, you won't solve the problem of overflowing by saying "no more pebbles". You say, stop filling it to the brim, so that we have some room to spare if someone throws in a pebble. —Th e DJ (talk • contribs) 22:08, 17 January 2024 (UTC)
 * Using that analogy, the question is whether to stop adding more water, to stop adding more pebbles, or to consider whether there are different sized pebbles that are different in the amount of water they displace. Editors are real people, and hassling someone because a "lever" gave an incorrect result isn't doing anything to improve the project. And using kb in a simpleminded way to boss other people around, when we know that kb are the wrong measure, is suboptimal conduct, duh. --Tryptofish (talk) 22:20, 17 January 2024 (UTC)
 * We don't know the precise measure for when a talk page will cause issues, but we do know that most user talk pages have no reason to be over that measure and that a lower value of the measure loosely correlates to faster loading. Aaron Liu  (talk) 22:33, 17 January 2024 (UTC)
 * Given that we don't know the precise measure, we should pay close attention to whether editors have trouble communicating on a given talk page. If someone has trouble loading the talk page, or has trouble leaving a message, that matters. And I'm not disputing that. But if no one is having that trouble, and if we don't know how to measure it, then using a measure that we know doesn't work, to boss that editor around, is just bossing an editor around. --Tryptofish (talk) 22:40, 17 January 2024 (UTC)

I picked out the longest pages listed in Database reports/Long pages/User talk (no subpages) (a report that generated) and tried to set up automatic archiving on the top three results. (FWIW none of these users have recently edited so asking them to do it is unlikely to happen). I made a minor mistake and forgot to subst: the template, so went back and did it again. As you can see, it took ten minutes, several of my edit summaries were eaten, and the attempt on User talk:OswaldClara failed because it comes back with the error "ERROR: The text you have submitted is 2,048.071 kilobytes long, which is longer than the maximum of 2,048 kilobytes. It cannot be saved.". While I was trying to make the edits, one CPU was throttling on 100% usage; one of the few instances where I've seen an Apple Silicon CPU get hammered. <b style="color:#7F007F">Ritchie333</b> <sup style="color:#7F007F">(talk) <sup style="color:#7F007F">(cont)  14:03, 13 January 2024 (UTC)
 * Support some formulation. A pagesize limit won't catch all problematic pages, but it will resolve enough problems to be worthwhile. That some pages such as ANI sometimes necessarily exceed that limit won't make it any less worthwhile (and ANI is usually lighter on mark-up and images than the problematic user talk pages). Oppose opening the door for any and all uninvolved editors of whatever standing to capriciously interfere with user talk pages. NebY (talk) 14:45, 13 January 2024 (UTC)
 * Support, per WP:COMMONSENSE if anything else. Archived talk pages are just one click away, nothing gets lost, I don't get all the drama and the stonewalling that is getting raised here.   Cavarrone  18:47, 13 January 2024 (UTC)
 * Support in principle. I am not the most tech savvy editor but I will agree that in general there should be some commonsense limits on talk page size. And I will qualify by saying that as much latitude as possible should be accorded users in terms of how they handle their talk page, and for that matter their user page. But we already have rules in place that make it clear that nobody owns their pages and we do have a few restrictions already in place in terms of content and behavior. So while I am content to leave the more technical details to others to hash out, I do think that a user talk page that is so large that others have difficulty opening the page, navigating it, or being able to comment there, is ipso facto disruptive in that it defeats the intended purpose of the page. My preferred approach would be a four-step process.
 * 1. Politely notify the user of your concerns and ask them to prune or archive their page.
 * 2. Issue some form of formal caution possibly in template form.
 * 3. Request assistance from an uninvolved admin who assuming the two previous steps have been attempted w/o satisfactory results could review the matter and if necessary in their judgement, issue a point blank directive to the user to get their talk page under control within a specified time frame.
 * 4. If all of the above has failed, some form of compulsory archiving can be set up.
 * It would be understood that any user could appeal to WP:AN if they felt this was unreasonable. All of which said, this is thankfully not a common problem, and I would imagine having to actually go through all of the above steps would be exceeding rare. -Ad Orientem (talk) 20:05, 14 January 2024 (UTC)


 * I would support a maximum user talk page size policy only provided that any discussion with activity in the last 2 weeks is allowed to remain regardless of page size. Otherwise we may have users with one or two humongous threads on their page either try and prematurely close/archive those threads or complain that new threads are disappearing before they can see them. This exception will probably be rare (the maximum length should be chosen such that it is), but it should explicitly be permitted. David Eppstein, this should deal with your ANI issue, as ANI gets auto-archived every 24 hours while only keeping threads with activity in the previous 60, making it only 25% of the stated age maximum. Animal lover &#124;666&#124; 21:30, 14 January 2024 (UTC)
 * No, this does not deal with my issue. My issue is that taking over and forcibly archiving someone else's talk page is an extreme measure, something that should only be done with very good reason. The only reason being promoted here is that somehow (maybe because of something hidden in how they are rendered to html) very long talk pages cause browsers to choke. If the length of the page is what is causing browsers to choke, then we urgently need to address that on the most important talk pages that editors see, our noticeboards. Pushing new rules on user talk without addressing the noticeboards is grandstanding. Making exceptions that allow our noticeboards to be huge because we really need them to stay exactly as they are in order to retain current discussions is sweeping the problem under the rug rather than doing something useful about it. If, on the other hand, it is not a length problem (maybe it is really #images not text size, or maybe some user talk pages have some weird coding that we do not see in the noticeboards) then length is not the problem we need to solve and we are succumbing to the "we must do something! this is something! therefore we must do it!" syndrome. —David Eppstein (talk) 21:37, 14 January 2024 (UTC)
 * Unfortunately, Wikipedia is in the real world, where not everything fits into perfect models. Yes, we want all pages to be reasonably short. However, we also want the ensure proper communication can take place at the correct venue. Yes, we should see if we can find a way to reduce the size of ANI; however, we can't hold other policies hostage over that. I came up with my issue before seeing your ANI comment, but the same concern I expressed is the issue with ANI. Animal lover &#124;666&#124; 21:50, 14 January 2024 (UTC)
 * This "unfortunately we're in the real world and we must do this thing even though this thing totally fails to address the actual problem" is rhetoric, not a valid argument. —David Eppstein (talk) 22:51, 14 January 2024 (UTC)
 * Frankly, I agree, although in the case of ANI it's not quite as straightforward (it is getting archived on a regular basis, it's just so damn high-volume that even a 24h auto-archive doesn't help). The most obvious thing after that would be to split its functions out among several different pages, but as far as I can tell, most efforts to spin up additional noticeboards the last few years have failed for want of adoption. <b style="font-family: monospace; color:#E35BD8"><b style="color:#029D74">jp</b>×<b style="color: #029D74">g</b>🗯️</b> 22:49, 14 January 2024 (UTC)
 * The problem is clear. Pages overloading devices. When crashing, this is generally a memory allocation issue of either CPU or GPU by the OS to the browser application. Larger pages with more content and more images, more scripts or other forms of complexity, expand into bigger pages, that need more memory to run and more memory to layout and render. Consider that cheap phones have just 2GB of shared RAM for CPU and GPU, while a Chrome tab on the desktop will easily run in excess of 100MB and you can see how relatively quickly a large webpage becomes problematic on such a device. Next to the main problem, there is the issue of slowness. The time that it takes the server to render a very large page from wikitext to html (20+ seconds) and the transfer time of a very large page (25MB+ is still a lot of data to download for a lot of people using Wikipedia). Now the times at which any of this becomes a problem differs of course for each user, each device, each amount of open browser tabs, each additional script/modification running (CD, or dark mode, and perhaps a inefficient browser extension) and a dozen other factors that none of us can really control. This is why generally, you try to keep webpages small. MediaWiki gives users lots of freedom however to NOT keep pages small. In general for content pages that is less of a problem because a lot will be cached and because people are there to consume the content and willing to wait. There are also things like google snippets and the lead (which generally renders early in the process) that takes away much of the discomfort. On (very active) talk pages however, due to the nature of interactions (lots of edits often quickly succeeding eachother, at the bottom of the page) the cache cannot be used as efficiently and people need to wait for the entire page to render to html, download completely and finish rendering on their screen completely, after which all modifications need to be made in order to interact with the page. You essentially happen to miss every single possible optimization and use every system to their max capacity that way. Notice boards (while often problematic), are less of a problem here as they DO archive, and they DO split out content when a discussion becomes to massive. The most common approach to solving this problem is lazy loading of content/sections with Javascript. But Wikimedians hate lazy loading and they probably hate Wikimedia/MediaWiki developers who would implement this lazy loading even more. The quick and reliable solution is a social one. Show restraint and be considerate towards other users by setting up archiving. —Th e DJ (talk • contribs) 22:45, 17 January 2024 (UTC)
 * Dynamically loading a large page reduces the effect of limited network bandwidth/computing resources, but browsing through the large page is still a problem. The common approach is to load from the top of the page downward, but with English Wikipedia's tradition of adding new sections at the bottom of the page, this would mean a lengthy, manual scrolling process to see the latest threads. This is arguably worse than just loading the whole page at once, since it requires constant user interaction. The community could invert this tradition, but the need for manual interaction in order to browse would still be present, just in reverse chronological order. This also makes searching the page more difficult. isaacl (talk) 03:17, 18 January 2024 (UTC)
 * "but browsing through the large page is still a problem" yeah, if you decide to load every section, you still have a problem. But this is not impossible to solve with lazy loading. Remember that every app with a chat interface works with a bottom first approach. You'd just have to scroll up inside a subcontainer. And searching within a chat isn't uncommon either. Or you can have a forum index, with pagination as a concept (but fora are top first) etc etc. But our current conventions do not match any of the common UI and programming interfaces that generally are used to solve problems like this. —Th e DJ (talk • contribs) 12:44, 18 January 2024 (UTC)
 * That was Flow, basically. Apparently people hated it enough for WMF to abandon it when they realized the changes needed for IP accounts. Mayyybe someday we’d get similar enhancements to DiscussionTools.  Aaron Liu  (talk) 14:17, 18 January 2024 (UTC)
 * It's pretty technically possible, and in fact is more or less how the mobile-apps talk pages are done -- we made an API that exposes DiscussionTools' parsed data, and the apps display that rather than the raw talk page HTML. Similarly you can see a Special page that does a reformatting of a talk page as a visualization of that same parsed data, which would be pretty functional as a "modern" talk page view if we turned on reply-buttons in it (and, you know, worked out all the edge cases)... DLynch (WMF) (talk) 16:25, 18 January 2024 (UTC)
 * Yes, I didn't want to get into details in discussing potential solutions; I just wanted to note that there are problems related to English Wikipedia's current ways of working (and some of them were discussed during the Flow deployment). New search tools or indices would help with searching, but browsing is a common activity for users to get a sense of the topics that have been discussed over time, and seeing the threads in context helps with identifying related clusters. Linking to threads is also common; supporting this would require dynamically loading the appropriate section, thus replacing a basic cross-referencing feature with one that requires the reader's browser to support Javascript (although I personally feel that this is increasingly becoming a necessary default assumption across the web, I understand why minimizing English Wikipedia's dependency on Javascript is a significant concern for some users). Regarding a bottom-first approach: whether the scrolling direction is up or down, that's what I was referring to by reverse chronological order. isaacl (talk) 18:02, 18 January 2024 (UTC)

Some perspective (the actual hundred largest user talks)
Lest we restrict ourselves unjustly to shitting solely on EEng for having a talk page that's insanely long and breaks browsers, keep in mind that his is not the longest, nor is he even in the top 10... or top 20... or top 50. Here is the actual table of the top 100 from the database report I set up last night:

I opened a thread on WP:AN about this, and I added archive templates to a couple of the pages where the users hadn't edited in over a decade to see how the archive bots handled such a thing. I think that 800 kilobytes is probably a good point to draw a line and say this talk page is too damn long. <b style="font-family: monospace; color:#E35BD8"><b style="color:#029D74">jp</b>×<b style="color: #029D74">g</b>🗯️</b> 23:53, 13 January 2024 (UTC)
 * I think inactive editors should also get not around, which opts them out of message delivery. Huh, Tryptofish is also on that list. COI? Aaron Liu  (talk) 00:58, 14 January 2024 (UTC)
 * I'm not sure what that table is intended to demonstrate. If an editor is not around, then presumably no one will need to contact them at their talk page. That means it doesn't matter how big it is. Riposte97 (talk) 01:36, 14 January 2024 (UTC)
 * Good point, though I guess it wastes server resources through MassMessaging. Still, there are quite a bit of active editors on there. Aaron Liu  (talk) 01:44, 14 January 2024 (UTC)
 * It's meant to demonstrate the thing that I said in my post: there are a bunch of user talk pages that are too long to be reasonably viewed or edited -- some of them larger than the MediaWiki software even permits a page to be -- and I think they should have archiving set up on them. I made a thread at WP:AN about this last night. Of course it would be possible to go through these and exempt the pages from inactive users, but it will make the list extremely difficult to work through (not to mention that whatever reasons we have for wanting active users to have loadable talk pages don't stop applying if the user is inactive). Since this only has to be done, what, once every fifteen years?, I think it should just be gotten over with. <b style="font-family: monospace; color:#E35BD8"><b style="color:#029D74">jp</b>×<b style="color: #029D74">g</b>🗯️</b> 04:07, 14 January 2024 (UTC)
 * Be that as it may, it's pretty clear from the above that this proposal is not going to get consensus.
 * I also note that the experiments you conducted on User talk:Hair e. pot err and User talk:JAB5 do not seem to have been entirely successful - the bots have archived everything to one archive page. Those pages are now enormous. Riposte97 (talk) 09:31, 14 January 2024 (UTC)
 * Yeah, I note with dismay et cetera. I think the way it works is that the bot archives to one page per run, which is normally fine but becomes problematic if it's run on 14 years of shit at the same time. Oh well. If this is done I suppose it will have to be done with a different bot, or with one-click archiver or sth. <b style="font-family: monospace; color:#E35BD8"><b style="color:#029D74">jp</b>×<b style="color: #029D74">g</b>🗯️</b> 10:05, 14 January 2024 (UTC)
 * I find it really strange that you thought that this was something to report at WP:AN, and I'm apparently not the only one, because the AN thread was closed pretty quickly. Is anyone seriously thinking that 100 editors should come under administrator scrutiny because of this? Why is this a "Dirty Hundred", as opposed to simply a hundred? (Which I am going to change in this edit.)
 * In any case, I am in favor of "some perspective". For all the shouting that EEng was the worst of the worst, over the past few days of drama, it turns out here that there are 82 talk pages that, at the time of this analysis, were longer than his. --Tryptofish (talk) 22:06, 14 January 2024 (UTC)
 * It was apparently an important enough to have been brought up at the admin noticeboard and discussed at length for the one individual person, so I had the creeping suspicion that people might have actually cared about the accessibility issue of many users' talk pages being so long they were literally impossible to render or comment on with many computers. I hope I can be forgiven for this conjecture. <b style="font-family: monospace; color:#E35BD8"><b style="color:#029D74">jp</b>×<b style="color: #029D74">g</b>🗯️</b> 22:45, 14 January 2024 (UTC)
 * If you think that what I and others have said to you here means that people don't care about accessibility, then you are missing the point. The way to address the accessibility issue is to relate the list you made to whether or not each entry on that list is actually difficult to access. That's useful to discuss. You began your post here by proposing 800 kb as a cutoff. Does the data actually support that? But when you call 100 editors the "Dirty Hundred", some of us are going to push back. --Tryptofish (talk) 22:53, 14 January 2024 (UTC)
 * I agree. User talk pages that consist mainly of newsletters don't cause bothersome delays for me. Aaron Liu  (talk) 23:06, 14 January 2024 (UTC)
 * EEng's talk page, at the time of his block, was 950k+ bytes long, if I recall correctly. Most of these talk pages are inactive. Aaron Liu  (talk) 23:02, 14 January 2024 (UTC)
 * OK, then, if I take your number of approx. 950 kb, that would put him in the vicinity of 65th on the list, give or take. --Tryptofish (talk) 23:11, 14 January 2024 (UTC)
 * Yeah, and there are only 6 with a longer talk page who have edited in 2024, assuming nobody else on the list archived their talk pages. Aaron Liu  (talk) 00:25, 15 January 2024 (UTC)
 * We're only two weeks into 2024, so there could be other editors who are still reasonably active. I think you and I agree that talk pages of people who have really been inactive for a long time are not that big a problem, since there will not be much reason for anyone else to communicate with them. --Tryptofish (talk) 00:54, 15 January 2024 (UTC)
 * Worth noting also that compared to all 6 with a longer talk page, EEng has the highest number of edits, both overall and per annum (given that he has been editing since 2008). This means that he has the largest relative footprint, so users are going to be more likely to cross paths with him as opposed to editors who might not be as prolific. This is likely why the concerns about talk page length are so acute when it comes to him in particular. Duly signed, ⛵ <span style="color: white; font-family: Verdana; font-weight: bold; background: linear-gradient(white, blue, navy, black)">WaltClipper - (talk)  14:49, 15 January 2024 (UTC)

A proposal for handling of long threads on talk pages and noticeboards
One recurring problem is that certain pages (ANI is probably the most frequent offender here, but there are others) tend to get big discussions, making it difficult to use them. I propose the following solution: Animal lover &#124;666&#124; 14:22, 19 January 2024 (UTC)
 * 1) Create a bot to move any big threads from the page to suboages. The bot will leave behind the thread header with a notice "this thread was moved" along with a link, and some template to prevent the archive bots from archiving this.
 * 2) When a discussion subpage no nlonger has any activity, this bot will archive the section on the main page. Consider some official closure on the subpage itself.
 * 3) Worth considering: make this bot an admin bot, and copy over any protection from the main discussion page to the subpage. Perhaps also put move protection on any subpage, regardless of main discussion page protection.
 * People (including me) have little problem with accessing ANI. Aaron Liu  (talk) 14:34, 19 January 2024 (UTC)
 * Animal lover says the problem is "use," not "access." I'm not exactly sure what they mean. But count me among those who see long threads and go into tl;dnr mode. I'm not sure that Animal lover's proposal would solve that problem. - Butwhatdoiknow (talk) 15:23, 19 January 2024 (UTC)
 * I feel like they simply mean replying and reading, which I also meant to include in “access”. Aaron Liu  (talk) 16:17, 19 January 2024 (UTC)
 * I'm really not sure what the proposal is and how it will fix things. Duly signed, ⛵ <span style="color: white; font-family: Verdana; font-weight: bold; background: linear-gradient(white, blue, navy, black)">WaltClipper - (talk)  18:22, 24 January 2024 (UTC)
 * This seems to propose a bot to move large threads to their own subpages of ANI. I don’t think the problem exists either. Aaron Liu  (talk) 18:42, 24 January 2024 (UTC)
 * Why would we need a bot to do this?
 * The only example I can think of of discussions having their own pages is WP:RFCTP. (See for a recent example of someone moving an existing discussion to its own talk page due to length). The manual system works just fine for RfCs.
 * I'm not convinced there's a need to move ANI threads automatically (or at all), but I think the first step would be to gain consensus for the process of creating new subpages and then, and only then, file a bot request for approval. Sincerely, Novo TapeMy Talk Page 18:58, 24 January 2024 (UTC)

How about responding to my proposal, as opposed to complaining about my wording? Animal lover &#124;666&#124; 21:50, 22 January 2024 (UTC)
 * I don't see the point of this and I haven't seen much people having trouble with using ANI. Aaron Liu  (talk) 23:16, 22 January 2024 (UTC)

Request for input regarding talk page use
There is a discussion and dispute regarding addressing a talk page post by an ip that may or may not be trolling or a legitimate request. Your input at User talk:Thinker78 is requested; cordial, objective input is welcome, to provide additional insights. Regards, Thinker78  (talk) 00:27, 10 February 2024 (UTC)
 * I looked, and you have three admins telling you to drop it. --Tryptofish (talk) 00:42, 10 February 2024 (UTC)
 * Two of them commented before I replied with my detailed rationale and one of them was already involved in the revert dispute. The other is an involved administrator who I questioned their block of someone else. But certainly, I will be mindful of that. Uninvolved community input would be nice and more clarifying of the issue though. Regards, Thinker78  (talk) 01:12, 10 February 2024 (UTC)
 * None of the admins are WP:INVOLVED since they are all merely performing adminstrative actions. Bon courage (talk) 02:45, 10 February 2024 (UTC)