Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a21cebcc1e070abb

Jump to content

Talk:Snickometer

Page contents not supported in other languages.
Add topic
From Wikipedia, the free encyclopedia
Latest comment: 1 year ago by 84.68.179.51 in topic Why "Snickometer"?

Removed unsourced and dubious material

[edit]

I removed this unsourced and dubious sounding material by an anonymous editor:

A backyard version of the Snicko was first tested and introduced by Luke Lukess in 1992. Using a small microphone drilled into a cricket stump and a tape recorder recording backyard games, the device was used to adjudicate caught behind decisions.

Similar material had been removed previously in the edit of 20:31, 14 January 2016‎. -- dmmaus (talk) 04:35, 18 January 2017 (UTC)Reply

Why "Snickometer"?

[edit]

It may be obvious to cricket fans why this technology is called a Snickometer, but curious non-fans drawn to this article for clarification will come up empty. I'm guessing that barely hitting the edge of the ball with a bat might be called a "snick," but the text of the article is not very helpful in that regards. 2600:1700:5B2C:A090:18AC:BBA3:1F1:D88B (talk) 18:25, 14 June 2024 (UTC)Reply

The term was coined by Mark Sharman, Commissioning Editor for sport in 1999 at Channel 4,who introduced the product in that year. Mark incorrectly thought the term snick was used by Cricketers to refer to a fine contact of bat on moving ball. In fact, the actual term used, then and now, is Nick. ‘Nickometer’ is what it should have been. Doesn’t sound right. 84.68.179.51 (talk) 15:20, 31 May 2025 (UTC)Reply