Warnock's dilemma

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

Warnock's dilemma, named for its originator Bryan Warnock, is the problem of interpreting a lack of response to an online posting.[1] The term originally referred to Usenet posts, but has been applied to mailing lists, blogs, Web forums, and web content in general.[2] The dilemma arises because a lack of response does not necessarily imply that no one is interested in the topic, but could also mean for example that readers find the content to be exceptionally good (leaving nothing for commenters to add).[2]

On many internet forums, only around 1% of users create new posts, while 9% reply and 90% are lurkers that don't contribute to the discussion. When no users reply, the original poster has no way of knowing what lurkers think of their contribution.

Warnock's dilemma leads to web publishers adopting more confrontational writing strategies in order to ensure that they will get a response.[3][4] However, this can also lead publishers to avoid producing the kind of content that might fail to generate comments due to its high quality.[5] This problem arises particularly with sites that focus on viral content, such as Buzzfeed and Huffington Post.[5]

Original description

<templatestyles src="Template:Blockquote/styles.css" />

The problem with no response is that there are five possible interpretations:

  1. The post is correct, well-written information that needs no follow-up commentary. There's nothing more to say except "Yeah, what he said."
  2. The post is complete and utter nonsense, and no one wants to waste the energy or bandwidth to even point this out.
  3. No one read the post, for whatever reason.
  4. No one understood the post, but won't ask for clarification, for whatever reason.
  5. No one cares about the post, for whatever reason.
    — Bryan C. Warnock, [6]

Since Warnock's original description of the dilemma in August 2000, the expression has become used in the Perl world.[7]

See also

Works cited

  • Lua error in package.lua at line 80: module 'strict' not found.

Notes and references

  1. Holiday 2012, pp. 101-103.
  2. 2.0 2.1 Holiday 2012, p. 101.
  3. Holiday 2012, p. 102.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. 5.0 5.1 Holiday 2012, pp. 102-103.
  6. Re: RFCs: two proposals for change -- Original description of the dilemma
  7. Re: Warnocked? -- Post to the Perl 6 language list explaining history and uptake of term

External links