I had a similar thing happen to me when an elevator I was in started to fall (it had emergency brakes but I didn't know that). I wouldn't describe it as shock, but almost as indifference. I thought "huh, so this is how it happens".
They said 123m in the interview, at least in the translation. But the point of the released interview was not to refute that they worked for the GRU. It was obvious to everybody. The point of that interview was to spite the West, by making it even more obvious that they were not tourists. Russia does this a lot, they don't even pretend that the stuff they put out is true. It's basically adding insult to injury.
It's interesting that they're targeting chain emails first. I would say comments on the Czech news sites are a bigger problem. Usually the Russian trolls are easy to spot (they use words and terms that people just don't normally use, like "demoblok" to denote the political parties which are critical to Russia), but sometimes it can be quite subtle. Then again maybe the news sites themselves should regulate this.
Some good basic info, but at the same time there are some inaccuracies. WAV is not a lossless format, it's a container, it can contain any compressed audio format, even mp3. You can have PCM inside WAV, which is indeed lossless, but you're not going to see that in the wild too often. Going with 16k is also questionable, since most readily available pre-existing datasets, were recorded in 8k (which is what telephony codecs mostly use).
WAV is almost always lossless with PCM data. I'm not sure where you got the impression that "you don't see that in the wild too often". Depending on what kind of analysis you need to having your audio at 8k is going to deem any results useless. I would have it minimum 16k and aim for 44.1k in order to preserve the top end which is where a large quantity of useful information is. The reason most sets are recorded in 8khz is that they are running MFCC's which are quite stubborn and insensitive to the high end anyway with most enough information for machine learning existing in the bottom end. If you're doing music, or environmental sounds you really need to preserve the other frequency bands.
Contractor in London here. I've seen this for Python / dev-ops as well, well more the aftermath since the contractors were usually already gone. But the level of incompetence was jarring for someone on 500 pounds per day (this was before Brexit).
As far as I know, the only way to have something close to Wireshark for CPUs is to do a simulation. Then you can measure network latencies, cache hits and so on, but the simulation will be extremely slow. There's GEM5 (http://www.gem5.org) - a simulator with couple of DSLs designed to do just that, but I'd bet that Intel has their own thing. I did my thesis on simulating MESIF in GEM5, here's a link: https://dip.felk.cvut.cz/browse/pdfcache/kadlej16_2013dipl.p... , that could get people started if they are interested (it also might be a good introduction into the subject of cache coherency protocols). I have the code laying around somewhere, I've been wanting to make it public, but it needs cleanup first.
