Wikipedia talk:Talk page guidelines

Images on talk pages

With this edit, Cambalachero added, "Non-free content can not be used at talk pages. If they are being discussed, they must be linked with a colon, as described, and If they are included for decorative purposes, they must be removed. "

But Wikipedia:Non-free content criteria states, "Non-free content is allowed only in articles (not disambiguation pages), and only in article namespace, subject to exemptions."

Thoughts? Flyer22 Reborn (talk) 06:17, 9 June 2017 (UTC)

I think you have found an error dating back to 2005 . The language you quoted is obviously flawed because all articles are in article name space . This redundancy appeared In this edit. Prior to that time the text said Non- free images may only be used in article namespace, period. That text gave the green light to article talk pages. the extra text saying " only in articles " was probably intended to preclude disambiguation pages, since an explanatory parenthetical comes right after the quoted " only in articles". Seems like the only way to really resolve this for purposes of these guidelines as to attempt to fix this problem on the guideline for non-free use . But that does seem worth doing since the confusion here appears to be the result of a clerical mistake in the diff I provided. It should probably read " only an article name space , excluding disambiguation pages . NewsAndEventsGuy (talk) 07:15, 9 June 2017 (UTC)

Articles need not be in article space. They might be in User: space, or in Draft: space. Also, that text did not give the green light to article talk pages: article talk pages are in Talk: space - they are the talk pages for pages that are in article space, but they are not in article space themselves. --Redrose64 🌹 (talk) 09:42, 9 June 2017 (UTC)

oops, thanks for pointing out that an article talk page is not in article namespace.... WP:Namespaces. I hate not noticing when I am assuming! NewsAndEventsGuy (talk) 11:28, 9 June 2017 (UTC)

Would someone please spell out the problem? Flyer22's OP includes two quotes:

1. "Non-free content can not be used at talk pages ..."
2. "Non-free content is allowed only in articles ... only in article namespace ..."

These statements seem to agree. The first is spelling out a consequence of the second, and the second has more detail (it's not just article talk pages where non-free content is prohibited). I regard "only in article namespace" as a redundant device to hose down wikilawyers who may argue they can copy an article to a user subpage and retain non-free content because it is no different from the "article". Indeed, Redrose64 gives that reasonable interpretation, although I would regard a copy of an article as different from the actual article. For example, article categories should be removed from copies of articles. Johnuniq (talk) 10:17, 9 June 2017 (UTC)

Let's put for example the lead image of The Avengers (2012 film). Writing [[File:TheAvengers2012Poster.jpg]], without colon, displays the image. That's what can only be done in article namespace. Writing [[:File:TheAvengers2012Poster.jpg]], with a colon, generates a mere link to the image, File:TheAvengers2012Poster.jpg. That's just a link, and may be used anywhere. It is not the image itself, but just a software element to make reference to the filename used to store the file. Cambalachero (talk) 12:06, 9 June 2017 (UTC)

IP user talk page

I'd welcome other opinions on this edit.

It seems to me that it's not what the guideline intends at all. But in that, as far as I can tell, IP user talk pages are in namespace 3, the same as the talk pages of registered users, perhaps this needs clarification.

See Wikipedia:Administrators' noticeboard/Incidents#User:185.59.158.22 for some of the background to this. Andrewa (talk) 05:11, 26 June 2017 (UTC)

@Andrewa: It's explicitly prohibited by WP:REMOVED, fourth bullet. --Redrose64 🌹 (talk) 08:05, 26 June 2017 (UTC)

So it is! Thank you. Andrewa (talk) 08:24, 26 June 2017 (UTC)

DTTR

I believe we should codify in these guidelines that WP:DTTR is not sufficient grounds to justify removal of a post on a talk page other than your own. Though DTTR is often treated as a policy or guideline, it isn't one, there's an antithetical one called Wikipedia:Do template the regulars, and user warnings are specifically written to not be personal attacks. Thoughts? pbp 14:03, 11 August 2017 (UTC)

WP:DTTR is just an essay, which can be boiled down to "templates often treat the editor as brand new, and provide helpful links - regular editors (should) already know about all the links and what's expected of them, so treating them otherwise isn't the best idea". Regardless of if someone agrees or disagrees with DTTR, it does not give grounds to remove a post from a talk page other than your own -- There'sNoTime ^{(to explain)} 14:15, 11 August 2017 (UTC)

• Oppose See WP:CREEP. While I agree this is a correct reading of existing rules, observe that 3 of us read the existing rules as already frowning on third party talk page reverts of this sort. NewsAndEventsGuy (talk) 17:16, 11 August 2017 (UTC)

Very old talk pages

On old talk pages, I find some weird layouts.

---

text
reply

---

text
reply

reply

---

etc

What was that? — Preceding unsigned comment added by Nixinova (talk • contribs) 20:42, 13 August 2017 (UTC)

Guidance against interleaving replies

Proposed text for introduction in "Editing others' comments" section:

"Generally you should not break up another editor's comment to reply to individual points. Interleaving comments like this confuses the layout of the page and obscures the original editor's intent, as well as potentially leaving text unsigned."

Version 2 of proposal (19:49, 14 August 2017 (UTC)):

"Generally you should not break up another editor's comment to reply to individual points. Mixing comments like this confuses the layout of the page and obscures the original editor's intent, as well as potentially leaving text unsigned. Instead, place your reply entirely below the original comment. You may wish to use the {{Talk quotation}} template to quote a portion of the material in question."

I have encountered a few times situations where to respond to seemingly itemized multiple points an editor interleaves their reply within the post they are replying to, for example as Andrewa did here (I'm inviting them to continue the discussion here out of courtesy). It may be particularly prone to happen when a post has bulleted points which I have seen a couple times and which made a real mess of the talk page. The biggest issue is that it leaves the original post's text broken up and without signatures. If signatures were added after the fact that would, to me, definitely constitute editing another's post and changing what they intended to convey and how they wanted it to look, without improving the clarity of formatting. I think instead the proper convention should be to say something like Regarding X, "Regarding X," whether X is a description or a numbered point in cases where there is one, or Quoted material: with the tq template, and to do this entirely below the post you are replying to. I am proposing that some guidance be added in this regard. —DIYeditor (talk) 00:26, 14 August 2017 (UTC) Edited to correct use of tq template. 19:08, 14 August 2017 (UTC) Updated with Version 2 of proposal. 19:49, 14 August 2017 (UTC) Underlined version 2. 02:06, 15 August 2017 (UTC)

The convention as I have followed it is not to break up existing paragraphs. It is in my experience easily learned and followed, and common elsewhere on the Internet. The indenting makes the authorship plain, and the interleaving makes the logic plain. Respecting others' paragraphs leaves their comments intact.

The proposed addition doesn't really make it clear that this is discouraged, and I'm not convinced it should be.

The convention I have followed is however easily messed up, either accidentally or deliberately, and when this happens it can get very messy.

I'd like a stronger statement on the mixing of colon and asterisk indenting. This is the most common way that the convention gets messed up, in my experience. Andrewa (talk) 01:02, 14 August 2017 (UTC)

No, please do not do that. Consider what might happen if someone wanted to reply to you, and then there was some back-and-forth. That leaves a dreadful mess. Talk pages are not just for the benefit of those currently participating who might know what is going on. In a year, people might want to work out why a particular decision was taken or not taken. Johnuniq (talk) 03:10, 14 August 2017 (UTC)

Exactly. But the mixing of asterix and colon indenting is depressingly common, and as you say often leaves a dreadful mess... I'll dig up some examples. Sometimes I suspect it is even deliberate rantstyle (I might not give examples of that as it raises behavioural issues) but other times it is, disappointingly, experienced and respected users, to the point I sometimes suspect I'm just being grumpy to criticise it. But if we could avoid it, it would greatly increase the value of the archives, as you say, as well as making it easier IMO to arrive at and assess consensus in the first place. Andrewa (talk) 06:34, 14 August 2017 (UTC)

This edit is a case in point - I fixed three problems there:

1. blank lines, contrary to WP:INDENTGAP (and which incidentally I have also fixed in this edit);
2. signature divorced from post by interspersed comments;
3. markup symbols inconsistent bwtween a post and its reply which caused the enumerated list to restart at 1 instead of continuing with 3.

Mixing the three styles (asterisk, colon and hash) is not a problem per se, the problem is when people mix them incorrectly. The general principle should be that if you reply to somebody, copy the markup from the start of their post, whatever combination of symbols that might be; and add one symbol (of any type) to the right hand end. --Redrose64 🌹 (talk) 09:01, 14 August 2017 (UTC)

Agree that the protocol proposed in the above post copy the markup from the start of their post, whatever combination of symbols that might be; and add one symbol (of any type) to the right hand end would work extremely well if followed consistently. But we need to deal with bold edits by inexperienced editors as well as considered edits by old hands, and as even the old hands often depart from the relatively simple current rule of Generally colons and asterisks should not be mixed for no obvious reason, there's reason to be very afraid of a new and more complex rule. I think on balance it would be worth a try. Andrewa (talk) 13:16, 14 August 2017 (UTC)

You know, Wikipedia possesses specific tools which allows one to reply to a specific section or paragraph of an other contributor's post. For instance, the template {{Talkquote}} allows one to quote the specific part of the post one wishes to reply to, complete with signature and linked timestamp, within one's own post below which one can then post one's own reply.Tvx1 17:21, 14 August 2017 (UTC)

Certainly... at the expense only of brevity. But that can also raise objections, in my experience. Andrewa (talk) 22:39, 14 August 2017 (UTC)

• Support Although long posts can be troubling in themselves, interrupting their flow to reply to a specific point takes any shortcoming with the fact its a long post and multiplies that by 10. So don't do that please. In the discussion I noticed two related and somewhat side issues to which I reply as follows -

Re A) on messy format.... see WP:SOFIXIT. These guidelines already encourage stand-alone edits that only clean up formatting problems. I usually do not do that with regulars unless I get their permission first. But for newbies, don't hesitate, just do it, and give them a friendly how-to-do-better-formatting note.

Re B) on replying point-by-point.... hopefully my comment here shows how I do this. If the long post does not include numbers or letters so you can reply that way, just give the point you want to reply to a letter or number and say what you wish after the longwinded editor's signature.

In closing, I think the suggestion to not insert comments in the middle is a good one, but I don't care for the word "interweave". My brain stopped cold, I had to think, it was an obstacle. Better to just use simple third grade language, something only a bit more refined than "Don't butt in line". NewsAndEventsGuy (talk) 14:06, 14 August 2017 (UTC)

Perhaps "Mixing comments" rather than "Interleaving comments"? And how about some additional guidance like: "Instead, place your reply entirely below the original comment." and perhaps "You may wish to use the Talk quotation template to quote a portion of the material in question." I agree that keeping it simple would be good but maybe some clear advice on what to do in addition to what not to do would help. —DIYeditor (talk) 19:19, 14 August 2017 (UTC)

Positive guidance, rather than negative, is greatly to be preferred. It is both far more likely to be effective and adheres to the spirit of wp:AGF. Andrewa (talk) 19:45, 14 August 2017 (UTC)

I don't think those are side issues at all...

A) I would welcome strengthening the relevant guidelines to make that a bit clearer. In particular, In general... is vague. If the proposed more elaborate guideline (which is growing on me) is adopted, I hope the phrasing will be more to the point than that.

B) Yes, that works in cases like this. Another technique which I have employed is to start a new subsection on a particularly important point that is raised. I've received some criticism in the past for doing this, but generally from those who did not wish to hear what was said (at the risk of violating wp:AGF... sometimes the assumption wears a bit thin). Andrewa (talk) 19:45, 14 August 2017 (UTC)

Andrewa, as far as your A) on this this proposal maybe it should simply be "You should not" rather than "Generally". I wasn't sure if consensus would be behind a strong statement but it seems to be heading that direction. —DIYeditor (talk) 23:58, 14 August 2017 (UTC)

Modifying comments already replied to

This edit rather surprised me... wouldn't it be better to raise it as a new post, with a heads-up? Andrewa (talk) 01:11, 15 August 2017 (UTC)

It's got a time stamp. Perhaps should have been underlined if it is not clear by the time stamp that it was a change. —DIYeditor (talk) 02:03, 15 August 2017 (UTC)

Yes, it complies perfectly with the guideline on modifying your own comments (WP:REDACT) as far as I can see. But it seems to me far more confusing than my edit [1] which inspired this whole section. I think the indenting there makes the signatory of the original post quite transparent, but I concede there are other views on this. But I can't see how this edit can fail to tangle the logic of the discussion. The text to which I was replying is no longer there to see, you need to go into the page history to find it. How can that possibly be helpful? And yet it seemingly conforms to guidelines. Should it? Andrewa (talk) 04:10, 15 August 2017 (UTC)

Well, without software to manage talk page comments all we have are manually implemented guidelines. If users are to be able to edit their posts I think strike and insert work well enough, as well as the instruction to add a new timestamp when you've done it. On some forums where users can edit their posts the custom is to do something like "Edit: I did so and so" at the end of the edited post which I think is less clear than our strike/underscore method, but we also include a suggestion to offer an explanation if necessary in brackets. Or are you proposing that users not be able to edit posts once they are replied to? This is always an issue in forums; what it appears someone responded to may actually have been edited. Without strongly discouraging or prohibiting edits I don't see a way around it. My thinking was that it would be useful in that particular situation if the proposal were updated at the top which I believe I've seen done in other surveys. Maybe it would be useful to have clear guidance on that specific circumstance - what if you want to add another option to a survey. To me at the top makes sense as long as it is clearly marked as an edit with a time stamp. It also makes sense to include a "Survey" and "Threaded discussion" section which I wish I'd done to keep the two separate. Then any updates to the survey or !votes on it can be kept in the same area. —DIYeditor (talk) 06:22, 15 August 2017 (UTC)

Strike does not have appropriate semantics, see HTML5 documentation: The s element is not appropriate when indicating document edits; to mark a span of text as having been removed from a document, use the del element.; and underscore does not have any associated semantics. For accessibility reasons, we should be using <del>...</del> and <ins>...</ins> respectively, see HTML5 documentation. --Redrose64 🌹 (talk) 14:38, 15 August 2017 (UTC)

Version 2

Proposal:

"Generally you should not break up another editor's comment to reply to individual points. Mixing comments like this confuses the layout of the page and obscures the original editor's intent, as well as potentially leaving text unsigned. Instead, place your reply entirely below the original comment. You may wish to use the {{Talk quotation}} template to quote a portion of the material in question."

1) Replaces "interleaving" with "mixing" per NewsAndEventsGuy's concern. 2) Adds a brief description of what to do in addition to what not to do. 3) A question from Andrewa is whether this should start with "Generally you should not" or stronger wording like "You should not". I thought the stronger wording may not cover every possible situation which is why I started with "Generally". 4) I felt that only a brief mention of the quote template that is most often used would be best and we should avoid putting a detailed style guide for replying in the "Editing others' comments section", but conceivably we could start a new section about quoting/replying. It could for example cover numbering or lettering points (if that's not obvious) and {{Talkquote}} (a different template from {{Talk quotation}}). That is more than I wanted to get into originally and even if that were added I think a statement in the "Editing others' comments section" against splitting another editor's post would still be appropriate. —DIYeditor (talk) 03:09, 15 August 2017 (UTC)

It's rearranging deckchairs. The more we look at the guideline the worse it gets, see #Modifying comments already replied to. Total rewrite required, incorporating the "add one of anything to the right" suggestion for more sophisticated users, and a far simpler protocol for beginners, example-based. And I still think that a brief interspersed comment is helpful on occasions, but I will of course go with the consensus on this. Andrewa (talk) 04:19, 15 August 2017 (UTC)

There may be some issues with this page as far as providing enough detail but I think the main places to address that are Help:Using talk pages and Wikipedia:Indentation (and any other topic specific locations). Providing examples and detailed style guides here would totally change the nature of the page. It is supposed to be dos and don'ts more than detailed instructions. We can make sure the reader is pointed in the right direction for more information. —DIYeditor (talk) 06:00, 15 August 2017 (UTC)

This proposal is a very welcome clarification. But I'm concerned that it is sufficiently severe in its impact as to require wider discussion. As it stands it seeks to ban or at least discourage what is a very common and IMO clear and helpful convention, one that is long in use far beyond Wikipedia. But this is a convention that I acknowledge is poorly documented on Wikipedia and often ignored here, leading to some very messy talk pages. Andrewa (talk) 17:30, 16 August 2017 (UTC)

Anchors (Version 3?)

@Andrewa, DIYeditor, NewsAndEventsGuy, Tvx1, Redrose64, and Johnuniq: In replying to or commenting on points in preceding comments, I have occasionally inserted anchors in those comments and linked to them. This way there is no need to quote in full the point I am responding to. More than that, when the discussion is already long and complex, with many replies-to-replies-to-replies-..., a reader can find the point being replied to without a potentially long and distracting search: for example, aXXXX this reference to Andrewa's comment about the "dreadful mess" that can result from mixing asterisk and colon listing. And unlike interleaving, anchors do not affect the display at all, but are visible only in edit mode.

I guess I'm making a proposal for a better (imho) way of replying to specific comments without interleaving or necessarily quoting, so I'm adding "Version 3" to my section header. I'm not ready to turn this into a guideline proposal, so I invite you all to please have a go at it (thus the question mark).

Please {{Ping}} me to discuss. --Thnidu (talk) 18:23, 27 August 2017 (UTC)

References

Template:Reflist-talk

I was going to boldly add a paragraph to the page, but because of the warning at the top—

You are editing a page that documents an English Wikipedia guideline. While you may be bold in making minor changes to this page, consider discussing any substantive changes first on the page's talk page.

— I'm posting it here first for discussion:

References on talk pages

If your comment includes references that will create footnotes, use Template:Reflist-talk at the end of your comment section. This will force your references to appear in a box at the end of the section, rather than at the foot of the page as they would in an article. Like this:

References

Comments, please! {{Ping}} me.--Thnidu (talk) 18:57, 27 August 2017 (UTC)

• Honestly, this page is complicated enough as it is. Refs on talk pages are fairly rare, and it's not the end of the world if they get rendered at the end of the page. Some other more experienced editor might come along and add {talkref}, or not, and either way it's not a big deal. I'd skip it, and let it be something people learn by example. EEng 19:09, 27 August 2017 (UTC)
• @Thnidu: I agree with the proposal. I see this about once a month and while not necessary, I'd like to see the practice formalized. Chris Troutman (talk) 21:26, 27 August 2017 (UTC)
• EEng (Ye gods, I just wasted at least half an hour in your "museums". Fun but dangerous!) Um... As I was saying... Yes, I still think it's a good idea. It can save a lot of scrolling (→ time → spoons), and make it a lot easier to compare the references with the text. I'mma put it in. --Thnidu (talk) 21:53, 27 August 2017 (UTC)