@glyph OK, I thought of something. Over the last few months I kept seeing #jq mentioned in passing all over the place. I finally realised it was installed by default on all my machines and looked up the manual. I've now used it to poke around in unfamiliar datasets, extract data from huge JSON files into user-friendly CSVs, and alongside #jc I've been able to convert YAML files to JSON, and pull out just the interesting parts of my Apache log files. Sure I could do all this in Python but I'm old enough to have used sed, awk, and plain old grep, so I love a versatile tool that can manipulate standard input. I don't know why I overlooked jq for so long.

[cont’d] The #JC's embarrassing failure is not significantly different from that of the #NYT and #WSJ, which used Israelis as "investigative reporters" despite their links to the #IDF/Israel, and allowed them to publish their pro-Israel biased pieces at critical stages, thereby giving Israel a pretext to escalate its already brutal and genocidal attack on #Gaza. In fact it seems endemic.

[…] Despite being provided with a series of questions, Wallis Simons and the JC have so far declined to describe# how Perry – an individual with no discernible journalistic track record, let alone as an investigative reporter – came to be writing for the paper or what due diligence had been exercised over an increasingly fantastic series of claims.

https://www.theguardian.com/world/2024/sep/14/crisis-at-jewish-chronicle-as-stories-are-withdrawn

@israel
@palestine