Re: ASA told the Home Office not to run the advert again
"So the Home Office need to coordinate with the DWP and HMRC."
Those three! Shudder.
40558 publicly visible posts • joined 16 Jun 2014
OTOH the opposite sort of comments are also flung around fairly freely when these sort of rows are going on. I can't see any of either persuading anyone that this is a good field to enter as a career unless, of course, they are the sort of profession umbrage taker who prospers in said rows.
There are, of course, purists who insist that "contact" is only a noun and el Reg should have said "attempted to make contact with".
JR-M probably has it on his banned list because his 2nd deputy nanny told him not to use that because her primary school teacher told her not to because her English teacher told her not to because Dr Johnson didn't define it as a noun. (Actually my old Pocket Oxford doesn't either but I'd guess a newer edition would.)
"My only gripe with Debian Linux being that infuriating Libre Office software that won't let me install Apache Open Office."
1. I've never come across that one. Really? I've had LO & OO on the same box in the past with no problems.
2. You do know you can remove S/W you don't want, don't you? Although I run LO myself it's the version from the LO site, not the distro version which I removed.
3. OO is still a thing?
I haven't tried anything with a 2.0 kernel lately but what I have found is that I could install new versions of Linux on very ancient H/W. Subsequently used than ancient H/W & Linux combo talk to and set up a brand new printer that the user's W10 infested laptop kept trying to set onto a sub-net that the laptop itself wasn't on. So new gadget worked better with Linux & old S/W rather better than with new W10.
Most banks don't seem to care that any time their users use this thing they're in breach of the contract with their bank (the "do not give your details to anyone ever not even the police" bit).
This is something the "nothing to hide" crowd fail to grasp. There are perfectly legitimate things which you're obliged to hide.
"IT is a service"
Quite right. It's a service within a business and it's the business that's the unit. Working in IT I always found it was most useful to the business if I got to know something about how my users worked. It didn't even do any harm if some of the users got to know something about IT. And the most effective way for that was face-to-face communication so not only did I not take offence at them coming and talking to me, I went to talk to them. In fact, at times, the seating arrangements were a little ad hoc and I found myself seated next to them.
Apart from anything else the "keep users at arm's length" approach is an invitation for users to keep IT at arm's length. Perhaps an arm long enough to reach to India.
"Before that, I lived in the Peoples Republic of Islington,"
A very long time ago, when David Blunkett was in his pomp, I went to a couple of talks by a pathologist from Sheffield. His standard opening (maybe not the best term in relation to a pathologist) was "Greetings from the People's Republic of South Yorkshire".
when my wife referred to the doll as "African-American" the woman became rather upset about the politically-correct terminology. "It's black, honey!"
To be fair the correct PC terminology could have just been changed to "black" and she'd missed it. It's harder to find umbrage to take if you can't keep wrong-footing the public.
My standard reply was that I'd already made clear to my bank that I wasn't doing that so the one thing I knew for certain was that they weren't my bank and I wasn't even prepared to confirm they'd guessed write. It was inevitably followed up a few days later by a plaintive letter from HSBC to the effect that I wouldn't give them a chance to try to sell me services I didn't want.
Once I closed the company my personal account was closed as well. I did offer to meet them to discuss it but only in my preferred branch, the one they'd just closed.
My preference is for requiring the telcos to automate the process but at much lower fees, say a couple of quid or a fiver for a TPS registered number. Get a call, dial a code when you put the phone down, the fee gets credited to your account and the caller charged with the fee plus the telco's fee. The call came from a different telco? No problem, the charge gets passed to them, they add their own fee and pass it on to the caller. Multiple telcos? It goes on accumulating more handling fees. A telco doesn't know where the call comes from? Tough, they pay the bill and realise they need to keep better records.
Downsides?
There'd be a need to prevent fraud - someone trying to collect a fee on every call whoever it came from so there'd need to be some statistical work to verify problem callers and maybe charge the would-be fraudsters for their trouble.
There'd also be an upfront cost for the telcos putting the mechanism together. In theory their fee covers it, in practice as it would close down the problem PDQ and they'd lose out on their investment. You know what would happen? They'd suddenly find ways to cut down on the problem rather that do that. Not being faced with a mandatory investment they couldn't recover is also good for the bottom line.
In general I wouldn't make a practice of it, although some people obviously do.
However there are situations where there's time to do work and neither office nor home are close at hand. In my case it's been occasions when I've taken the grand-kids to their tennis lesson & have to hang about waiting to take them home again. If I have something to write I'll take a laptop and sit the club's coffee bar although it's likely that it will be the little MSI job and not something more substantial. For others it might be waiting for a train, a gap between appointments or lectures etc.
The email system is dependent on co-operation. WHat a pity Microsoft haven't worked out what that means. A rational response would be for MSPs to organise a back channel for sorting out problems. If MS have a problem with another MSP then use that channel to raise it and let that MSP sort it out. Blocking the entire SP should only be the last resort. Of course it may well be that such an arrangement is in place and has failed to resolve the matter so an additional action should be to announce that this mechanism in use. In that way innocent users of both services (yes, Microsoft, it's your customers who are rendered unable to receive mail) at least know what's happening and can take avoiding action.
Do you know who contributes most to Linux? It's the big companies who get something back - largely Intel because so many devices use their processors.
What they get back is a widely used OS that costs them less to develop co-operatively than if they went all-out to each develop their own private OS. H/W vendors used to roll their own. Then they saw how a 3rd party OS such as CP/M allowed a whole lot of start-ups to start making their own products. The MS followed up with MSDOS. The day of the OS developed from scratch was largely over. Common sense, really.