Re: Custardy
She certainly wasn't to be trifled with.
Well, somebody had to.
32780 publicly visible posts • joined 16 Jun 2014
"Always enjoyed the fact that the US "#" (pounds, or octothorpe if you're a purist)) key translated to the UK "Sterling" key on some keyboard or other.
Would make more sense if it replaced the "$" key, but something else was there."
It's still the $ key. As the # is still needed it means the UK keyboard needs an extra key.
On the subject of # and £ keys has anyone sorted out how to get the £ working properly on Devuan on the RPi? It results in displaying a # and (apparently) a CR on bash. Ksh displays £ and then on the next line a complaint about ?B?#: not found and in vi it inserts \xc2\xa3.
Both its parents,f Raspbian and Devuan on Intel have no problems with this. And, yes, I've tried various combinations of locale and keyboard map without finding one that works. Fortunately it only affects CLI usage (including ssh sessions).
One of my first jobs was preparing dissections - mostly rats for schools (they went into perspex boxes filled with formalin; the filling holes sealed with the littl plastic plugs from the ends of ballpoint pens). The formaldehyde tanned my hands. I'm sure that resulted in the dermatitis I suffered down the years.
My approach to dating pollen samples was to brew up a large sample with NaOH to dissolve the humic acid matrix and sieve it, just like the first stages of a normal preparation for microscopy. The resulting brown liquid was then run through a continuous flow centrifuge at 10,000 RPM to get the fine particulate content back. That was checked with a microscope to ensure it was mostly pollen. It didn't need any other treatment except to char it (uncharred samples would gum up the dating system with tar). What I suspect was happening was that someone else was doing much the opposite - precipitating the humic acid with HCl and dating that. He was supposed to be doing a PhD on pretreatment methods; it did tell us something about the relative ages of various components but not in time for what I needed.
"The fumes at melted away a lot of the contacts on the motherboard!"
We had a pretreatment for carbon-dating samples that involved a final wash with dilute HCl (I can't think why!) followed by drying in a large drying cabinet. The cabinet got progressively less effective. We eventually found the fan blades had been eaten away. The cabinet was just sitting in the open lab, no fume cupboard.
We had another, small drying cabinet in a different lab. This was used to dry off benzene which was the final wash for pollen samples for microscopy so the amounts were small. One day SWMBO decides to make some meringues using ANalar sucrose (because it was available) and used the little cabinet as an oven.
The things you could get away with before elfin safety.
I'm not sure we're looking at the same graph. The UK line shows an initial peak followed by what looks like a bit of a change of mind followed by a fairly steady state, maybe falling a little from 2014 up to and including Q1 2018 after which is shows sustained falls for each of the following quarters. The fall from 2014 mirrors what's happening in Germany and the Netherlands, both of which have had much higher registrations in the UK except for the early exuberance when the UK had more then the Netherlands.
Yes, for users the issue is not so much on the protocol as on getting the information it contains right. Of course if the "established e-Tailer" is "Nominet was able to match the registrant's name and address against a 3rd party data source" then you can consider it fair warning. If the registrant is a business, tell us because it isn't PII. If it's an individual then comply with GDPR or equivalent legislation elsewhere. Sole traders need to be considered; off hand I'm not sure what GDPR has to say about those as data subjects.
"The problem is you'll just get the desktop and no useful software to run from there."
Really? What desktop Linux versions did you try? I'm not sure about some of the lightweight versions - of which there are a fair few in the list Jake pointed to - and there are some special purpose versions, such as pen-testing, etc. But all the mainstream versions come bundled with a set of applications that fulfil most everyday needs such as browser, email, graphics, multimedia and office.
Perhaps by "no useful software" you mean "no useful software you can buy". That may be because there's not much need.
"Patents shouldn't be transferable...."
Let's do a thought experiment.
You invent something.
You patent it.
You find you really don't have the money to build and sell it.
Do you
(a) Hock your house, children & right arm (assuming that allows you enough credit) to borrow money from the bank to set up a factory and marketing organisation, not of which you have experience of or
(b) Go to a VC who requires the above and 95% of the profits to set up the factory & marketing organisation or
(c) Sell the patent to someone who already has the business in place to develop it and cash out not?
Suddenly we see there's a good reason to be able to transfer patents.
Waaaaay back I worked for a short while for a schools supplier, this time biology and chemicals, who also went bust. They also had just made a capital intensive new-build addition. What's worse in their case it was mostly to produce microscopes just at the time the Japanese were coming into the market.
You'd think by now that hotel chains would have learned that (a) they really need to do a thorough annual audit of their own security and (b) do the same in spades for any business they're thinking of buying.
Obviously they haven't. It's going to take a few more big fines and lawsuits, big enough for the board and investors to notice. Even then it seems doubtful that they'll manage to learn from the misfortunes of others.
"Must be bloody expensive printer paper."
For what I hope are obvious reasons the base stock is a security print. That means not only specialist printing techniques but also rigorous control, secure disposition of waste etc. Pads are, or were (it's a long time since I've seen one), personalised to the prescriber which also introduced a good deal of maintenance of prescriber data etc. It all adds to costs.
Nevertheless my previous GP used to use the tractor-fed paper face-down in their office printer, not only wasting money but making a nonsense of the whole security issue.
I wonder how a totally electronic system would work for consultations outside the GP's surgery or hospital. I assume there will be a well secured means of sending the prescription from a phone (you may detect a slight snark here) but what if the patient also needs the bar-code token? Does this mean the doctor has to carry a portable bar-code printer or will there be pads of pre-printed tokens to be carried?
"at Mach 5, they travel 86 meters in 1/20th of a second"
Quite. There's something not making sense here. Is the engine 86 metres long? Is there a convoluted path? Is the air slowed to much less than Mach 5? Or does this mean there's some way to go before it can be cooled quickly enough to work in an engine of practical size?
The fact remains, however, that the package for the direct employee is different. It includes holidays, sick pay etc. as tax-free benefits in kind. In order to maintain "fairness" - which was much trumpeted by the likes of Red Dawn - surely those should be taxable. And while we're looking at such things why not assess the value of a permanent contract of employment. It would be a little more difficult to value because some "permanent" posts are more permanent than others but then HMRC have never been hesitant about valuing things if it brings in taxes. How would they value their own posts?
The thing to do in such circumstances is to ask oneself what BOFH would do.
In this case, gradually limit the bandwidth available over period of a couple of months. When the complaint eventually arrived the usual BOFH/PFY good cop/bad cop/worse cop routine would explain that it must be because our internet connection is getting very congested these days and we really need a much bigger pipe and suggesting a contract with a new comms supplier they've just heard of.
The issue is do you mitigate the worst risks, which seems to be the solution they're looking at, or do you eliminate them?
OK, here come the no-Linux-here naysayers but all they can claim is one sort of risk vs another. The GDPR-related risks are ultimately legal and on-going whilst the FOSS-related risks are practical ones involving training and the like and relate to change-over.
if the Timeline is disabled and telemetry set to the lowest level, there are "no high data protection risks resulting from the diagnostic data collection in Windows 10". My emphasis.
Hmmm. Does this mean "We know there are still some risks" or "There could still be risks but we haven't found them if there are"?
"If they start being completely honest and open about what they pay staff, how much they raise and what they spend that money on then I will be happy to believe what they are doing is genuine."
You mean they should do something like publish accounts? With some oversight body like the Charity Commission?
Sometimes figure need a little interpretation. A while ago it was reported that the Charities Commission was concerned with Samaritans because almost the whole income was eaten up by office expenses. What do Samaritans do? They seat counsellors in offices to answer phones. Offices and phones were classed as office expenses.
One junction in Huddersfield used to have a turn right filter operated by a detection loop in the road. The detection loop was forward from the stop line. Out-of-town drivers would stop at the stop line on red. The main lights changed to green and they'd just stay there waiting for the filter not knowing that they needed to roll forward a car length or so to trigger the filter.