Be advised: this thread is not for serious in-depth discussion of weighty topics (we have a link for that), this thread is not for anything Culture War related. This thread is for Fun. You got jokes? Share 'em. You got silly questions? Ask 'em.
What is this place?
This website is a place for people who want to move past shady thinking and test their ideas in a
court of people who don't all share the same biases. Our goal is to
optimize for light, not heat; this is a group effort, and all commentators are asked to do their part.
The weekly Culture War threads host the most
controversial topics and are the most visible aspect of The Motte. However, many other topics are
appropriate here. We encourage people to post anything related to science, politics, or philosophy;
if in doubt, post!
Check out The Vault for an archive of old quality posts.
You are encouraged to crosspost these elsewhere.
Why are you called The Motte?
A motte is a stone keep on a raised earthwork common in early medieval fortifications. More pertinently,
it's an element in a rhetorical move called a "Motte-and-Bailey",
originally identified by
philosopher Nicholas Shackel. It describes the tendency in discourse for people to move from a controversial
but high value claim to a defensible but less exciting one upon any resistance to the former. He likens
this to the medieval fortification, where a desirable land (the bailey) is abandoned when in danger for
the more easily defended motte. In Shackel's words, "The Motte represents the defensible but undesired
propositions to which one retreats when hard pressed."
On The Motte, always attempt to remain inside your defensible territory, even if you are not being pressed.
New post guidelines
If you're posting something that isn't related to the culture war, we encourage you to post a thread for it.
A submission statement is highly appreciated, but isn't necessary for text posts or links to largely-text posts
such as blogs or news articles; if we're unsure of the value of your post, we might remove it until you add a
submission statement. A submission statement is required for non-text sources (videos, podcasts, images).
Culture war posts go in the culture war thread; all links must either include a submission statement or
significant commentary. Bare links without those will be removed.
If in doubt, please post it!
Rules
- Courtesy
- Content
- Engagement
- When disagreeing with someone, state your objections explicitly.
- Proactively provide evidence in proportion to how partisan and inflammatory your claim might be.
- Accept temporary bans as a time-out, and don't attempt to rejoin the conversation until it's lifted.
- Don't attempt to build consensus or enforce ideological conformity.
- Write like everyone is reading and you want them to be included in the discussion.
- The Wildcard Rule
- The Metarule

Jump in the discussion.
No email address required.
Notes -
Item 1 of 3
Are there any traffic-sign designs that annoy you? (For reference, the US uses the MUTCD (Manual on Uniform Traffic-Control Devices), while several dozen other countries use ECE/TRANS/196 (the Vienna Convention on Road Signs and Signals) plus local standards (such as UKGBNI's Traffic Signs Manual).)
MUTCD sign R10-12, "left turn yield on green 🟢": This is redundant! It should be "left turn yield on green circle" or "left turn yield on green ⬤" instead of "left turn yield on green [green circle]".
MUTCD sign W4-2L/R, "left/right lane ends": On most US traffic signs (see, e. g., sign W4-3L/R, "added lane on left/right"), thin lines (around 1.5 or 2 inches on a 36-inch sign) represent both lane lines and road edges, while thick lines with arrowheads (around 4 or 5 inches) represent traffic movements. For many years, I have been utterly baffled by the decision to denote road edges with thick lines (without arrowheads) on this sign only. IMO, the unusual thickness of these lines, especially in conjunction with the thin line representing a lane line on the same sign, invites the motorist to misinterpret them as traffic movements rather than as road edges. (Compare UKGBNI diagram 871.2, "reduction in number of traffic lanes ahead", which on a 1260-mm (50-inch) sign uses thin lines (30 or 45 mm, 1.1 or 1.8 inches) for both lane lines and road edges and thick lines (80 mm, 3.1 inches) with arrowheads for traffic movements. See also the code chart's semi-official rendition of Unicode character â›™, "white left lane merge", which uses thin lines for lane lines and thick lines for road edges.)
Item 2 of 3
Front-page news on Reddit: Microsoft Publisher, a program for laying out printed (or at least page-based) works, is being discontinued. Competitors include Adobe InDesign (1 2 3), QuarkXPress (1 2 3), and Scribus. (Microsoft recommends Word and PowerPoint as replacements.)
At present, HTML+CSS is focused on the layout of a single webpage that can be as tall as it needs to be (1 2), and is unable to deal with such items as page numbers and section titles in page headers, footnotes in page footers, and page-number references for intra-document links. CSS Generated Content, CSS Paged Media, and CSS Generated Content for Paged Media technically exist, but only in draft form, not ready for implementation. It's my understanding that these drafts are based largely on the work of companies that have developed their own nonstandard solutions for problems that standard CSS fails to address—e. g., Prince XML, Antenna House Formatter, and BFO Publisher—just as other CSS standards have been based on the nonstandard work of major browsers. In particular, the acknowledgements section for CSS GCPM specifically states: "This work would not be possible without the immense contributions of Håkon Wium Lie." Lie, the creator of CSS, has been the chairman of Prince XML's board since year 2004 (1 2).
Item 3 of 3
Front-page news in Nowheresville, USA: A lawyer is removed from a county courtroom after rejecting the judge's instruction that he wear a tie.
A few days later, the lawyer makes the front page again—he sues McDonald for allegedly defaming him in a Facebook post responding to the news.
At least around here, it seems these are (slowly) getting replaced with a flashing yellow arrow, with an equivalent sign. A bit confusing at first, but I think it makes sense that it would use a typical "proceed with caution" indicator, not a "go".
The use of a flashing yellow arrow to indicate a permissive left turn was approved by the feds on an experimental basis in 2006 (Interim Approval 10) and on a permanent basis in 2009 (in the previous edition of the MUTCD). But adding an extra yellow arrow to a signal is a lot of money to spend, just to remind motorists of the default rule that they should be following anyway (on a green circle when neither a green arrow nor a "no left turn" sign is present).
This is a sensible signal but the implementation around me has been terrible. The left turn signal is a 3-stack of arrows, green, yellow, and red. The first part of the turn is a protected left, so it's a green arrow during this segment. Near the end of the protected left segment, it switches to solid yellow for 3 seconds. Now, my expectation would be that if the next period is unprotected turning, it would flash yellow, and it does, but not before turning solid red for 1 second. Every time I start proceeding on the yellow, expecting it to turn flashing, the solid red causes me to stomp the brakes in case I've made a mistake and the direction is changing. It's infuriating, and I wonder if anybody else has this terrible implementation in their area.
(My preference would be for it to transition immediately from green to flashing yellow - why do we need a warning that we're about to proceed with caution?)
Under MUTCD § 4F.01 ¶ 03:
This is the default under item F.6.
This is permitted (not recommended or required) under item F.6.b.
If you feel like making a long shot, you can try asking your jurisdiction about this signal, citing these specific passages of the MUTCD in your complaint.
More options
Context Copy link
More options
Context Copy link
More options
Context Copy link
More options
Context Copy link
More options
Context Copy link