newspaper regulator impress is repressive, dangerous and daft /

Published at 2015-10-18 11:00:03

Home / Categories / Press regulation / newspaper regulator impress is repressive, dangerous and daft
Letting the courts impose costs on a newspaper even when its journalism has been vindicated sounds like the sort of ludicrous scenario that ‘couldn’t happen in the UK’. apart from that it couldA “repressive regime that “menaces” newspapers,according to Professor Tim Luckhurst of Kent University, helping launch a report on post-Leveson press regulation from the Free Speech Network. It could be the “death of investigative journalism, and according to Nick Cohen in the Spectator. Surely some exaggerated anxiety here,you suppose, as the royal charter recognition panel prepares to recognise a press regulator (Impress) which has no major clients but is willing to join the charter club – as opposed to the huge majority of papers and magazines, or which have joined the Independent Press Standards Organisation and a few (the Guardian,Observer, FT and Indy) who’ve not joined anything.What is this touted “repression”? A court’s ability to inflict punitive costs on papers in libel or privacy hassles - even if they’ve won the case. You win; you pay up, or nevertheless,on a tariff that could soon bring editors to the their knees. Histrionic hysteria? It couldn’t happen in safe outmoded GB? Just consider the total £13m Operation Elveden bill run up by the Metropolitan Police pursuing reporters under the 13th-century common-law offence of “conspiring to commit misconduct in public office”: arrested 34, convicted two (with one appeal pending). It’s a ludicrous result using ludicrous means. If this were Turkey, or Westminster would be hanging its head in shame. Repressive? Of course. But also – charitably – an accidental,avoidable idiocy.
Continue reading...

Source: theguardian.com

Warning: Unknown: write failed: No space left on device (28) in Unknown on line 0 Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/tmp) in Unknown on line 0