Revision as of 07:35, 25 February 2015 editFlyer22 Frozen (talk | contribs)365,630 edits →Distinction between acceptable and unacceptable forks← Previous edit | Latest revision as of 09:07, 30 September 2024 edit undoSdkb (talk | contribs)Administrators81,284 edits →Answer to the question: Are "Introduction to" articles exempt from this policy?: ReplyTags: Mobile edit Mobile web edit Advanced mobile edit Reply | ||
(147 intermediate revisions by 47 users not shown) | |||
Line 3: | Line 3: | ||
|counter = 2 | |counter = 2 | ||
|algo = old(30d) | |algo = old(30d) | ||
|archive = Misplaced Pages talk:Content |
|archive = Misplaced Pages talk:Content forks/Archive %(counter)d | ||
}} | }} | ||
{{archives}} | {{archives}} | ||
{{centralized talk|Misplaced Pages talk:Content forking/Internal}} | |||
== |
== WP:SPINOFF 2nd case == | ||
In ], the 2nd case (meta-articles) seems to be actually a ''consequence'' of spin-off rather than a ''cause'' for spin-off. So, I'm inclined to rewrite it as follows: | |||
Some examples, could be hypothetical, of improper content forking would be useful. I'm still not sure when an article could be considered a legitimate spin-off piece and when this is to be avoided. <font face="Rage Italic" size="4" color="#800080">]</font> <sup><font face="Times New Roman" color="#006400">] ]</font></sup> 15:36, 21 September 2013 (UTC) | |||
<blockquote>The main situation where spinoff articles frequently becomes necessary is when the expanding volume of an individual section creates an undue weight problem, for example: (...) The resulting article often becomes a summary style overview meta-articles composed of many summary sections, e.g.: (...) Summary sections are used in the broader article to briefly describe the content of the much more detailed subarticle(s).</blockquote> | |||
] (]) 19:15, 22 July 2023 (UTC) | |||
: |
:Done. ] (]) 04:42, 1 August 2023 (UTC) | ||
== Obligatory thread - making POVFORK less anti-AGF == | |||
== Proposal: Rename to "Content forks" == | |||
This is an apparently obligatory thread by {{User|Flyer22}}. Does anyone object/agree with my edit, and if so, please explain why. --]<small><sup>\ ] /</sup></small> 10:15, 18 February 2014 (UTC) | |||
{{archive top}} | |||
This proposal is to rename the guideline to "Content forks". | |||
The guideline now predominantly describes content forks rather than the editing activity of creating content forks, i.e., "content forking". | |||
:Like I stated I would, ] to this matter. ] (]) 17:09, 18 February 2014 (UTC) | |||
⚫ | |||
When applying the guideline, editors are primarily concerned with identifying the actual content that may need fixing, rather than the behavior that resulted in it. It is simpler to say "this is a content fork", rather than "this is an example of content forking". | |||
Most of the subsections describe a type of content rather than a type of content editing. | |||
::hmm... *scratches head* ...the MOS people? Does it have application to them somehow? I mean, I could be missing something, but it would of course help if I knew why you, personally, objected to the edit and felt the need to revert it (apart from it just being an edit to a guideline). Do you feel it doesn't clearly reflect consensus or something? --]<small><sup>\ ] /</sup></small> 17:50, 18 February 2014 (UTC) | |||
The lead section was changed to "Content fork" years ago. | |||
:::Forking is related to WP:Manual of Style, and I couldn't think of a better and more appropriate place to get various comments on this matter. But, alas, none of them have weighed in here on this matter yet. As for your edit, I personally dislike when one editor significantly changes a longstanding guideline or policy without discussion, especially if the change is spurred on by some recent Misplaced Pages experience the editor had and he or she is looking to make the guideline or policy conform to his or her personal view. Such changes are usually reverted, as it is in this case. What benefit is there to your change? ] (]) 19:15, 19 February 2014 (UTC) | |||
Maybe it's time for the title to be changed to "Content forks" to match the focus of the guideline. | |||
::::], but ] is probably the better venue for canvassing this. I'd have thought to post something there had I felt that this changed the guideline in a controversial or truly significant way (I would still like to know why you feel it does, though). ''What benefit is there?'' Apart from eliminating the redundant, confusing sorta-sentence starting with, "Instead, apply Misplaced Pages's policy that requires a," simply read the edit and its summary again. The change encourages ] so that a fork that someone believes violates the ] can be ] without it becoming a referendum on the motivations of the forker(s) and a ], thereby also ], as it encourages commenting on the content instead of the contributor. On a related note, I find it's a good rule of thumb to assume good faith and comment on the content—not the contributor's possible motives or bias—when a credible editor makes a change to a guideline, too. --]<small><sup>\ ] /</sup></small> 04:54, 22 February 2014 (UTC) | |||
* '''Support''' - as proposer. <span class="nowrap"> — '']'' </span> 02:57, 8 October 2023 (UTC) | |||
:::::Significantly changing a longstanding Misplaced Pages policy or guideline without discussion is not something I believe in, especially when it concerns a policy (though I know that Misplaced Pages:Content forking is a guideline), as is obvious by my above commentary. Misplaced Pages's policies and guidelines should be based on ], as even the "Changes to guidelines don't inherently require a discussion beforehand" link you showcased reflects, and that there is no objection to an edit does not always equate to "WP:Consensus"; sometimes such changes are accidentally overlooked. I suggest directing people at WP:VPP to weigh in on this matter. As for a "good rule of thumb to assume good faith and comment on the content—not the contributor's possible motives or bias," I've seen enough cases where an editor is in a content dispute and then comes to a policy or guideline and changes it to suit their argument in that content dispute; so, yes, their motives and bias are relevant in those cases. I'm not stating that something like that is what brought on your desired change to this guideline; I'm only stating why motives and bias very much matter to me when it comes to changing policies and guidelines. ] (]) 20:45, 26 February 2014 (UTC) | |||
: (pinging users from the discussions above) {{ping|WhatamIdoing|Quercus solaris|Pbsouthwood|Chris troutman|SmokeyJoe|Valjean|Anythingyouwant|fgnievinski}} <span class="nowrap"> — '']'' </span> 12:24, 10 October 2023 (UTC) | |||
== Notability standards for ] == | |||
:Consistency with the lead section is generally desirable. On that count I weakly support at this point, having seen no counterarguments. Other than that, a redirect would be valid and useful whether the move is done or not. Ping me if there is any serious debate. Cheers, · · · ] ]: 13:02, 10 October 2023 (UTC) | |||
I have started a discussion about notability standards for ]s at ].--] <small>(] / ] / ] / ] / ])</small> 05:40, 4 June 2014 (UTC) | |||
* '''No objection''' to the results (forks) of the unintentionally deficient activity (forking) being the focus of the chosen phrasing, as long as the fact of how forks are typically produced — by forking — is not perversely obscured. I'm not saying that anyone intends that, I'm just stating the condition of my "no objection". In other words, forks are typically produced by a failure to think of checking for existing content; to think of linking a term (such as a synonym, antonym, coordinate term, or related term) and finding out whether the link is blue or red and then following a bluelink to learn what's behind it before one writes any "wall of dupe"; to not forget to (at least) ''try'' to avoid duplicating existing content; and so on. As long as that fact (how forks happen and thus how to prevent them) remains clear in the text's explanations, I'm fine with focusing on results ("fork" and "forks") as the predominant nouns in the chosen phrasing (with gerund "forking" being less commonly mentioned albeit not "banned from utterance"). ] (]) 13:51, 10 October 2023 (UTC) | |||
jghcjchggf <span style="font-size: smaller;" class="autosigned">— Preceding ] comment added by ] (]) 08:41, 24 June 2014 (UTC)</span><!-- Template:Unsigned IP --> <!--Autosigned by SineBot--> | |||
: (pinging users from the discussions above) {{ping|WhatamIdoing|Chris troutman|SmokeyJoe|Valjean|Anythingyouwant|fgnievinski}} <span class="nowrap"> — '']'' </span> 08:03, 14 October 2023 (UTC) | |||
== Template POV fork == | |||
: {{done}} <span class="nowrap"> — '']'' </span> 04:34, 27 October 2023 (UTC) | |||
], any feedback there would be appreciated since TFD is usually a pretty inactive place.] (]) 17:24, 23 July 2014 (UTC) | |||
{{archive bottom}} | |||
== Tried to clarify the concept == | |||
== Several large POV forks were recently created. Should we merge them? == | |||
The content of these sections is largely identical, with some minor variation: | |||
*] | |||
*] | |||
*] | |||
: (pinging users from the discussions above) {{ping|WhatamIdoing|Quercus solaris|Pbsouthwood|Chris troutman|SmokeyJoe|Valjean|Anythingyouwant|fgnievinski}} | |||
Also, there are several duplicated paragraphs in these sections: | |||
*] | |||
*]. ] (]) 22:39, 20 January 2015 (UTC) | |||
I've edited the lead and a couple sections to help clarify what types of content forks are or are not acceptable, and what is or is not a content fork. For example, transcluded templates aren't content forks, as the copy can't diverge from the original, even when the original is modified. The guideline didn't mention pages of different types that cover the same subject, even though they fall under the definition of content forks (pieces of content about the same subject), so I've added that in. | |||
Multiple paragraphs about hydroelectricity have also been duplicated: | |||
*] | |||
Please look it over, and revert, remove, or revise as you see fit. Sincerely, <span class="nowrap"> — '']'' </span> 07:43, 19 October 2023 (UTC) | |||
*] | |||
:It may not be perfect, but is probably good enough. · · · ] ]: 14:06, 19 October 2023 (UTC) | |||
{{unsigned|Jarble}} | |||
::It's a lot longer, which is going to discourage people from reading it. Maybe try to split some of the new content into a ==Section==? ] (]) 16:50, 19 October 2023 (UTC) | |||
⚫ | |||
:::I haven't had a chance to look over the edits in detail, but I concur with @]. Conciseness for guidance pages ]. The impulse to respond to people not understanding the guidance by adding additional clarifying detail is ], and will make the problem worse by causing people not to read it. Examples never belong in guidance leads unless the topic is impossible to understand without them. Dumping the new material into a new section would at least get it out of the lead, but it'd still make the body longer, contributing to CREEP. I was inclined to revert when I came across these edits on watchlist but didn't because I didn't have time to sift through them to figure out what was just copyediting vs. expansion. <span style="color:#AAA"><small>{{u|</small><span style="border-radius:9em;padding:0 5px;background:#088">]</span><small>}}</small></span> <sup>]</sup> 17:09, 19 October 2023 (UTC) | |||
: Hello ], thank you for posting this here. I would support you with this effort, and it should be sooner than later, it is hard to merge articles, once each copy had a life of its own. — ] 07:08, 25 February 2015 (UTC) | |||
: Thank you for the feedback. So far, I've made the following changes in response to the above comments: | |||
:: {{done}} – Move examples to sections, to reduce lead size | |||
:: {{done}} – Add section links to lead, for ease of reference | |||
:: {{done}} – Move etymology out of lead to its own section, to reduce lead size | |||
:: {{done}} – Copy edit lead to reduce wordiness | |||
: Also, thank you @], your edits are definitely an improvement. <span class="nowrap"> — '']'' </span> 20:58, 20 October 2023 (UTC) | |||
== Are "Introductions to" articles exempt from this policy? == | |||
Please see related discussion at ] <sub style="border:1px solid #228B22;padding:1px;">]|]</sub> 03:30, 8 November 2023 (UTC) | |||
: Note: That discussion was closed, with no new consensus reached. <span class="nowrap"> — '']'' </span> 23:26, 26 September 2024 (UTC) | |||
::That discussion looks like it has a lot of argument, but if it was never promoted at the Village Pump or somewhere else that'd give it visibility, it's unsurprising it never had enough participation to make a consensus clear. <span style="border:3px outset;border-radius:8pt 0;padding:1px 5px;background:linear-gradient(6rad,#86c,#2b9)">]</span> <sup>]</sup> 14:41, 27 September 2024 (UTC) | |||
:::@] Do you think it would be a good idea to do a VP or RfC? <sub style="border:1px solid #228B22;padding:1px;">]|]</sub> 05:31, 29 September 2024 (UTC) | |||
::::I'd have to look into it further to say for sure, but my inclination is that it could be, yes. <span style="border:3px outset;border-radius:8pt 0;padding:1px 5px;background:linear-gradient(6rad,#86c,#2b9)">]</span> <sup>]</sup> 06:22, 29 September 2024 (UTC) | |||
:::::@] Take your time. A second opinion would be helpful to avoid the appearances of forum shopping. (I forgot about this issue anyway, but if folks find it interesting, I'd certainly support continuing the discussion to reach a consensus). <sub style="border:1px solid #228B22;padding:1px;">]|]</sub> 03:33, 30 September 2024 (UTC) | |||
::::: {{ping|Piotrus}} A VP or RFC on this would likely be a waste of participants' time. This is a contentious issue, with very strong arguments for and against, which will very likely wind up "no consensus", but not before a lot of bluster and frustration. It wouldn't resolve anything and would create unnecessary stress for those who feel strongly one way or the other, and anyone caught in the middle. Therefore, I'd advise against it. Just my 2 cents' worth. <span class="nowrap"> — '']'' </span> 08:48, 30 September 2024 (UTC) | |||
=== Answer to the question: Are "Introduction to" articles exempt from this policy? === | |||
::] and ] (Sebastian), articles sharing one or more paragraphs is normal and accepted on Misplaced Pages; Jarble, you know this, and the Related articles section of the WP:Content fork guideline is clear about this. Duplicate paragraphs do not make content fork violations unless there are articles that are pretty much the same thing and have duplicated paragraphs. ] (]) 07:17, 25 February 2015 (UTC) | |||
::: Thanks, ], I admit that I did not check the facts and compare the articles; I just assumed they were just wholesale forked. This was rash, and I'm sorry for that. — ] 07:22, 25 February 2015 (UTC) | |||
{{ping|Sdkb|Piotrus}} All content forks in the encyclopedia are subject to this guideline, which defines which types of content forks are acceptable (should be kept) and which types of content forks are unacceptable (should be deleted). So, no, "Introduction to" articles are not exempt. That leaves the question "What type of content fork is an "Introduction to" article? The answer is that it is a ], a type of ]. <span class="nowrap"> — '']'' </span> 08:20, 30 September 2024 (UTC) | |||
== Distinction between acceptable and unacceptable forks == | |||
]<!-- Just making sure you see this. --> | |||
The article seems to make the distinction between acceptable and unacceptable forks as follows: | |||
{| class="wikitable" | |||
|- | |||
! Size of smaller text !! Copied text !! Condensed text | |||
|- | |||
| Whole article || unacceptable || (not possible) | |||
|- | |||
| Section || NOT COVERED || acceptable | |||
|} | |||
What about the NOT COVERED quadrant? I feel an uncondensed copy of text introduces the same problems, whether it is copied to an article of its own or to a section within another article. Can we clarify that in this guideline? — ] 07:08, 25 February 2015 (UTC) | |||
:The question at hand is more what it ought to say than what it currently says. <span style="border:3px outset;border-radius:8pt 0;padding:1px 5px;background:linear-gradient(6rad,#86c,#2b9)">]</span> <sup>]</sup> 09:07, 30 September 2024 (UTC) | |||
:I addressed this in the ] section above. Sections are not yet explicitly covered in the WP:Content fork guideline because it is perfectly acceptable for articles to share one or more paragraphs, especially if ] is followed. By what the WP:Copying within Misplaced Pages and ] guidelines state, Misplaced Pages accepts and/or encourages such copying. The Related articles section of the WP:Content fork guideline addresses the fact that "distinct but related topics may well contain a significant amount of information in common with one another." | |||
== Where was the WikiProject process fork move review and RfC? == | |||
:Since this page does not get a lot of traffic/does not have a lot of ], I will alert ] to this discussion. ] (]) 07:29, 25 February 2015 (UTC) | |||
{{slink|Misplaced Pages:Content_forks/Internal|Process forks}} has {{tpq|one project trying this caused a tremendous amount of disruption over several years until a move review and an RfC reversed them}} from {{diff||848260232}}. Which? I am looking for a wikilinked footnote, especially to verify the potentially exaggerated wording {{tpq|a tremendous amount of disruption over several years}}. ] (]) 15:18, 18 August 2024 (UTC) | |||
:. ] (]) 07:35, 25 February 2015 (UTC) |
Latest revision as of 09:07, 30 September 2024
Archives | ||
|
||
This page has archives. Sections older than 30 days may be automatically archived by Lowercase sigmabot III. |
To help centralize discussions and keep related topics together, Misplaced Pages talk:Content forking/Internal redirects here. |
WP:SPINOFF 2nd case
In WP:SPINOFF, the 2nd case (meta-articles) seems to be actually a consequence of spin-off rather than a cause for spin-off. So, I'm inclined to rewrite it as follows:
The main situation where spinoff articles frequently becomes necessary is when the expanding volume of an individual section creates an undue weight problem, for example: (...) The resulting article often becomes a summary style overview meta-articles composed of many summary sections, e.g.: (...) Summary sections are used in the broader article to briefly describe the content of the much more detailed subarticle(s).
fgnievinski (talk) 19:15, 22 July 2023 (UTC)
Proposal: Rename to "Content forks"
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
This proposal is to rename the guideline to "Content forks".
The guideline now predominantly describes content forks rather than the editing activity of creating content forks, i.e., "content forking".
When applying the guideline, editors are primarily concerned with identifying the actual content that may need fixing, rather than the behavior that resulted in it. It is simpler to say "this is a content fork", rather than "this is an example of content forking".
Most of the subsections describe a type of content rather than a type of content editing.
The lead section was changed to "Content fork" years ago.
Maybe it's time for the title to be changed to "Content forks" to match the focus of the guideline.
- Support - as proposer. — The Transhumanist 02:57, 8 October 2023 (UTC)
- (pinging users from the discussions above) @WhatamIdoing, Quercus solaris, Pbsouthwood, Chris troutman, SmokeyJoe, Valjean, Anythingyouwant, and Fgnievinski: — The Transhumanist 12:24, 10 October 2023 (UTC)
- Consistency with the lead section is generally desirable. On that count I weakly support at this point, having seen no counterarguments. Other than that, a redirect would be valid and useful whether the move is done or not. Ping me if there is any serious debate. Cheers, · · · Peter Southwood : 13:02, 10 October 2023 (UTC)
- No objection to the results (forks) of the unintentionally deficient activity (forking) being the focus of the chosen phrasing, as long as the fact of how forks are typically produced — by forking — is not perversely obscured. I'm not saying that anyone intends that, I'm just stating the condition of my "no objection". In other words, forks are typically produced by a failure to think of checking for existing content; to think of linking a term (such as a synonym, antonym, coordinate term, or related term) and finding out whether the link is blue or red and then following a bluelink to learn what's behind it before one writes any "wall of dupe"; to not forget to (at least) try to avoid duplicating existing content; and so on. As long as that fact (how forks happen and thus how to prevent them) remains clear in the text's explanations, I'm fine with focusing on results ("fork" and "forks") as the predominant nouns in the chosen phrasing (with gerund "forking" being less commonly mentioned albeit not "banned from utterance"). Quercus solaris (talk) 13:51, 10 October 2023 (UTC)
- (pinging users from the discussions above) @WhatamIdoing, Chris troutman, SmokeyJoe, Valjean, Anythingyouwant, and Fgnievinski: — The Transhumanist 08:03, 14 October 2023 (UTC)
Tried to clarify the concept
- (pinging users from the discussions above) @WhatamIdoing, Quercus solaris, Pbsouthwood, Chris troutman, SmokeyJoe, Valjean, Anythingyouwant, and Fgnievinski:
I've edited the lead and a couple sections to help clarify what types of content forks are or are not acceptable, and what is or is not a content fork. For example, transcluded templates aren't content forks, as the copy can't diverge from the original, even when the original is modified. The guideline didn't mention pages of different types that cover the same subject, even though they fall under the definition of content forks (pieces of content about the same subject), so I've added that in.
Please look it over, and revert, remove, or revise as you see fit. Sincerely, — The Transhumanist 07:43, 19 October 2023 (UTC)
- It may not be perfect, but is probably good enough. · · · Peter Southwood : 14:06, 19 October 2023 (UTC)
- It's a lot longer, which is going to discourage people from reading it. Maybe try to split some of the new content into a ==Section==? WhatamIdoing (talk) 16:50, 19 October 2023 (UTC)
- I haven't had a chance to look over the edits in detail, but I concur with @WhatamIdoing. Conciseness for guidance pages is absolutely essential. The impulse to respond to people not understanding the guidance by adding additional clarifying detail is understandable but exactly the wrong approach, and will make the problem worse by causing people not to read it. Examples never belong in guidance leads unless the topic is impossible to understand without them. Dumping the new material into a new section would at least get it out of the lead, but it'd still make the body longer, contributing to CREEP. I was inclined to revert when I came across these edits on watchlist but didn't because I didn't have time to sift through them to figure out what was just copyediting vs. expansion. {{u|Sdkb}} 17:09, 19 October 2023 (UTC)
- It's a lot longer, which is going to discourage people from reading it. Maybe try to split some of the new content into a ==Section==? WhatamIdoing (talk) 16:50, 19 October 2023 (UTC)
- Thank you for the feedback. So far, I've made the following changes in response to the above comments:
- Done – Move examples to sections, to reduce lead size
- Done – Add section links to lead, for ease of reference
- Done – Move etymology out of lead to its own section, to reduce lead size
- Done – Copy edit lead to reduce wordiness
- Also, thank you @WhatamIdoing, your edits are definitely an improvement. — The Transhumanist 20:58, 20 October 2023 (UTC)
Are "Introductions to" articles exempt from this policy?
Please see related discussion at Wikipedia_talk:Make_technical_articles_understandable#Should_the_seciton_on_"Introductiont_to"_articles_be_depreciated_(removed)? Piotr Konieczny aka Prokonsul Piotrus| reply here 03:30, 8 November 2023 (UTC)
- Note: That discussion was closed, with no new consensus reached. — The Transhumanist 23:26, 26 September 2024 (UTC)
- That discussion looks like it has a lot of argument, but if it was never promoted at the Village Pump or somewhere else that'd give it visibility, it's unsurprising it never had enough participation to make a consensus clear. Sdkb 14:41, 27 September 2024 (UTC)
- @Sdkb Do you think it would be a good idea to do a VP or RfC? Piotr Konieczny aka Prokonsul Piotrus| reply here 05:31, 29 September 2024 (UTC)
- I'd have to look into it further to say for sure, but my inclination is that it could be, yes. Sdkb 06:22, 29 September 2024 (UTC)
- @Sdkb Take your time. A second opinion would be helpful to avoid the appearances of forum shopping. (I forgot about this issue anyway, but if folks find it interesting, I'd certainly support continuing the discussion to reach a consensus). Piotr Konieczny aka Prokonsul Piotrus| reply here 03:33, 30 September 2024 (UTC)
- @Piotrus: A VP or RFC on this would likely be a waste of participants' time. This is a contentious issue, with very strong arguments for and against, which will very likely wind up "no consensus", but not before a lot of bluster and frustration. It wouldn't resolve anything and would create unnecessary stress for those who feel strongly one way or the other, and anyone caught in the middle. Therefore, I'd advise against it. Just my 2 cents' worth. — The Transhumanist 08:48, 30 September 2024 (UTC)
- I'd have to look into it further to say for sure, but my inclination is that it could be, yes. Sdkb 06:22, 29 September 2024 (UTC)
- @Sdkb Do you think it would be a good idea to do a VP or RfC? Piotr Konieczny aka Prokonsul Piotrus| reply here 05:31, 29 September 2024 (UTC)
- That discussion looks like it has a lot of argument, but if it was never promoted at the Village Pump or somewhere else that'd give it visibility, it's unsurprising it never had enough participation to make a consensus clear. Sdkb 14:41, 27 September 2024 (UTC)
Answer to the question: Are "Introduction to" articles exempt from this policy?
@Sdkb and Piotrus: All content forks in the encyclopedia are subject to this guideline, which defines which types of content forks are acceptable (should be kept) and which types of content forks are unacceptable (should be deleted). So, no, "Introduction to" articles are not exempt. That leaves the question "What type of content fork is an "Introduction to" article? The answer is that it is a WP:DIFFFORK, a type of WP:GOODFORK. — The Transhumanist 08:20, 30 September 2024 (UTC)
- The question at hand is more what it ought to say than what it currently says. Sdkb 09:07, 30 September 2024 (UTC)
Where was the WikiProject process fork move review and RfC?
Misplaced Pages:Content forks/Internal § Process forks has one project trying this caused a tremendous amount of disruption over several years until a move review and an RfC reversed them
from . Which? I am looking for a wikilinked footnote, especially to verify the potentially exaggerated wording a tremendous amount of disruption over several years
. 142.113.140.146 (talk) 15:18, 18 August 2024 (UTC)