This will be like trying to explain rocket science to a Labrador.

If it was my land, I'd be more worried about it setting fire to huge swathes of dry grass than hitting a building. Isn't space debris pretty hot by the time it's battered its way through the atmosphere?

Back in the day, "bricked" meant permanently and irrevocably useless - rendered somewhat like a brick, in fact - rather than something that would fix itself if you left it to update.

I'm fairly sure that Mountaineering Scotland aren't covertly funded by Apple.

Well yeah, but the problem is it also puts the lives of the mountain rescuers at risk, which is more of a problem. Mountain rescue doesn't work on the basis of determining fault and allocating resources accordingly.

To non-UK readers, the development was overseen by the Head of Track and Trace, Dido Harding, failed boss of ISP TalkTalk who presided over data loss relating to around 4m customers. She is coincidentally married to John Penrose MP, who (I'm not making this up) is the UK Anti-Corruption Champion. The cost of the Track and Trace system so far has been £37,000,000,000 (around $50bn), give or take, in a country with a population of around 67m.

I'm more interested in how it "slowly regained buoyancy," given it never lost buoyancy in the first place. If anything you could argue it would be more buoyant as it was in a denser medium (mud).

Is there a legal or other reason Apple didn't sign the guy up to a long-duration non-competitive contract?

3, 2, 8, 6, 1, 9, 7, 4, 5?

Too late, David Cameron (allegedly) beat him to it. https://en.wikipedia.org/wiki/...

This will work great for dead racist, psychopathic relatives, based on previous MS chatbots.

"...the last furlough?" I didn't know horse racing was measured in periods of idleness.

Well, no they didn't, otherwise they'd be lousy yes-men.

They didn't so much have the capability to build a prototype that looked like theirs, as the money to pay somebody to come and build a nice body for them.

I'm very far from an expert on this, but I thought the idea was that the client hashed the password and the server compared the hashes, so that the password was never sent to the server. This isn't the case then?