Exactly right.
And the issue is further confounded/compounded by the medium that
the alleged new "source" was reported in. Even if Demi Moore is
perfectly reliable on the truth surrounding her birth name,
common sense tells you that a 140-character tweet (or two) is not
the sort of place where you can make nuanced distinctions between
"I was born Demi, which is to say, that's what everyone always
called me, even though it says 'Demetria' on my birth certificate"
versus "I was born Demi, and it even says that on my birth
certificate, but my parents always said it was short for
'Demetria', and I always believed that, and told the story in a
People Magazine interview, too, and I only just recently learned
the truth."
(Common sense should also tell you that revisionist history is
rampant when it comes to these sorts of aspects of the personal
lives of celebrities.)
The Cunctator wrote:
Ummm... common sense says that if someone says what
their birth name is,
about 50 years after they were born, when decades of documentation --
including interviews -- says something different, that someone is making
up the new info.
Either Demi Moore was incorrect in 1996, or she is incorrect now.
Either People Magazine, Encyclopedia Britannica, the New York Times, and
the World Almanac are incorrect, or Demi Moore now is incorrect.
Both common sense and Wikipedia policy should give weight to reliable
sources, especially when Demi Moore has conflicting statements.
On Mon, Dec 5, 2011 at 10:44 AM, Ken Arromdee <arromdee(a)rahul.net> wrote:
> On Sat, 3 Dec 2011, Steve Summit wrote:
> >> Summary: Demi Moore, in a tweet but verified as being her, says that
> her own
> >> birth name is Demi. Wikipedians do not want to use this statement
> because
> >> the "reliable sources" say otherwise.
> > And, per that talk page, they've got some pretty darn good arguments.
>
> Except for common sense.
>
> Common sense says that if someone tells you what their birth name is, you
> believe them, not something that's probably misinformation but which has
> been multiply repeated.
>
> Someone on BLPN is actually arguing that WP:IAR *doesn't allow you to
> ignore
> sourcing policy*. Of course it does.