Re: Waylanding
"Wayland is mostly usable now"
Damning with faint praise.
I agree that is, now, the case with KDE on Debian/Devuan. It wasn't a few months ago.
33111 publicly visible posts • joined 16 Jun 2014
Given that a lot of money had been spent in development writing it off against one or two prototypes gets very expensive. Even more so when you write it off and then buy imports. And most of all when you do so to tell the world the exact depth of your commitment to "the white heat of technology".
Nevertheless, if they want to look like scammers they're going to be treated as such.
Maybe initially nobody will notice. Nobody, that is, except the scammers. When the customer gets used to this way of renewals they'll get scammed. Next time round after that the renewals are going to fall off.
No problem, the vendor manager will have had a couple of years' bonuses paid and it'll be time to move on and explain how he boosted the renewal rate at his last job.
When I send an email Mythic Beasts send it for me from my domain because they're the MSP for that domain but it originates from my machine sent by me.
Somebody sending an email not via Mythic Beasts and purporting to be from my domain should be instantly treated as a scammer.
they themselves signed on the altar of “taking back control”
I fear the attitude of the current govt. is that that's something somebody else signed log ago. It looks as if getting them to abide by something they signed themselves is hard enough, probably on the basis of an elaboration of "We didn't read it properly".
"With each passing day the opportunities are missed," said European Scrutiny Committee chairman Sir Bill Cash. "British institutions are left high and dry while science marches on without them and the returns on our financial contribution edge lower."
I suppose he'll argue it's nothing to do with him, hoping we'll forget his contributions to the car crash.
"does the end-user really need a third-party holding (and snooping on) their business?"
The snooping should have been dealt with long ago. The existing system should have incorporated a PKI years ago so that encryption could be built into the clients.
The equivalent of a torrent would be that you send out the email to lots of other people and the when the intended recipient goes online they pick it up from whoever is online at the same time.
I've always been in the habit of storing emails locally. It's very convenient. It means I've gone through several service providers, migrated from ISP addresses to own domain and switched the MSP for the domain. It still does work on a basis of a server - fairly unavoidable, I'd have thought, with the store and forward nature of email unless I were to run my own server. It means that I have a local archive of more or less anything I need going back years (and a lot of stuff I no longer need but don't have to waste time reviewing to discard).
My sister-in-law, however, has difficulty grasping the notion that the icon for her email on the desktop is just a link to her MSP, opened by the same application as her Google icon with saved credentials and that by going back to the login screen and entering her husband's ID they could use it to access his email instead of using his mobile. People like that would have problems making the switch.
Shifting habitual thought is a bit like turning a supertanker. A pandemic and the consequences - problems it's raised with supply chains and discovering that having everyone in the office isn't essential - is probably starting to do that.
It's going to take time to work out that cities as presently used aren't sustainable but there's a lot of money invested in them, together with more than half a century's planning dogma, at least in the UK. Things might have to bite very hard to change that but bite they will.
"which means ensuring that OS, drivers and software will run on older kit"
The OS, drivers and software that ran on the older kit will continue to do so. If you want something he older kit didn't support then you will need something newer although the older products might need continuing security releases.
The real clash comes when the old kit has some very expensive, much longer life machinery attached, such as a PC running W7 controlling some expensive machine tool or medical diagnostic equipment. That case could be dealt with by requiring the source code to be placed in escrow and released if the software is declared EoL before the equipment it was controlling.* If the S/W vendor doesn't want that then they have to look on provision for continuing support as part of the original cost of doing sales.
"Escrow and release would also be the solution for security releases in general.
Interests can be steered.
In many countries a lot of equipment has to meet safety requirements to be placed on sale. Looked at in the broader sense repairability can be seen as a public safety issue.
If the choice is a longer life-cycle and selling of reasonably priced spares versus being not being allowed to sell products at all I'm fairly sure most companies would be able to decide pretty quickly to do the right thing.
Security of employment, e.g. being employed as a Civil Servant by HMRC, is also a substantial untaxed benefit in kind. An MP with security from only one election to the next would have much less security and a minister, at the whim of the PM even less again and possibly even less than a contractor.
Lower overall tax rates paid for by taxing these benefits should be able to get buy in from Parliament and ministers as they would gain accordingly. I'm surprised HMRC haven't suggested it as it would, at a stroke, get rid of the disparities and ensure everyone pays the right amount of tax.
"Woman haven't been required to wear hair coverings in the UK for as long as we have recorded history, which encompasses at least two and a half millennia."
Accepting "the UK" as shorthand for either the island of Britain, the whole archipelago including Ireland or anything in between: we have two and a half millennia of recorded history?
Even stretching "recorded history" to include the occasional reference as seen from the far end of the Mediterranean: we have recorded history sufficiently detailed to record requirements for hair covering?
The Robin Hood Airport case was a particularly difficult one. Whether one takes a bomb threat seriously is heavily conditioned by factors such as whether you have public safety responsibilities or whether you have experience of an environment where bombing were sufficiently frequent to make one inclined to take them seriously.
I've mentioned before something that highlighted to me the contrast between someone with NI experience (me) and someone with just English experience (facilities management). One of the other tenants in a glass-walled business received occasional bomb threats. They were taken sufficiently serious that the building would be evacuated but not, inmy view, seriously enough.
FM's idea was that people would walk round the end of the building, following a path very close to it, to the assembly area on the opposite side of the building to our exit.. Mine was that I'd exit the building and proceed in as straight a line as possible as perpendicular as possible to the facade until I'd reached a safe distance and if you want to walk past a glass wall with, potentially, a bomb inside it you're welcome. I'd seen what a bomb detonated a few tens of metres from my place of work had done and heard accounts from those who'd been there at the time.
"Death and rape threats are also illegal."
As is "threatening behaviour" in general, it often appears on the charge sheet. The courts are well experienced in dealing with it. Putting the decision in the hands of a regulator who isn't might be problematic.
We've been through the loop of trying to apply the existing law to threats made online in the past - e.g. the bomb threat against Robin Hood Airport. That didn't work out well. Have we learned anything since then? Do such threats, made in the heat of of the moment but not really meant, have cumulative effects on others who hear them and incline them to violence? If not, can we distinguish those which do or which are meant? If we can make a better judgement of what's serious and what isn't can we just apply existing law through existing means?
"The Minister rated the chances of such a kill switch being built as low."
Unlike ministers elsewhere who are convinced that saying they want it is all that's needed to bring it into existence.
Perhaps he had to put somebody's wish list into the speech to keep them happy whilst personally being realistic.
"If you give somebody your phone number and they store it in their phone, you don't each agree to a set of legal T+C's about what that person may or may not do with your number."
If I give someone my phone number it's for their use to contact me. There's an implied limitation there. I'd hope that if someone else asked them for my number they'd check with me first as that's what I'd do in the reciprocal situation.
As to your straw man argument - that would very likely be an offence under some aspect of common law.