an initial coin offering that "never really existed, on a blockchain that never really existed, born from mining farms that never really existed."
One of the better ones, then?
42396 publicly visible posts • joined 16 Jun 2014
"the whole truth"
Or as much of it as he can remember.
This element of the oath always worried me. As a witness one can only respond to the questions asked. If neither asks for a relevant fact then the fact might not get into the evidence and if a witness were attempt to volunteer it the counsel who the fact doesn't favour might object.
The US and Liberia are the only common law jurisdictions to use it. The rest of us have replaced the closed door system with an open court with a judicial figure of some nature in charge (AFAICR it was magistrates in NI). Depending on the case reporting restrictions might be in place but members of the public can see what's happening and defendants not only know about the proceedings but can be represented.
It's a very interesting comparison between the two legal systems, especially as regards the operation of the grand jury. On this side of the pond we got rid of them some time ago in favour of preliminary hearings, usually, as far as I can remember, in front of a magistrate and in open court. I wonder what impression the US system is making on the judge.
"Seems you don't really understand the difference between security and privacy"
One thing I'd want security for is to protect privacy. If a vendor (any of them) goes straight for taking away privacy any security they may put in place against third party threats is somewhat devalued.
Regulation on providers of services exists to protect customers. Genuine businesses comply with that. Compliance is a cost of doing business. Undercutting by non-compliance puts everyone at risk by driving out genuine businesses who try to offer legitimate low-cost provision.
"Probably because there's no way they can really know. In this example"
The whole problem with their business model is that they're taking money for something for which they should take responsibility which they find difficult to do. Their response to the Irish incident suggests they expected to get away with doing nothing.
It's their problem and we should hold them responsible for solving it. If they can't or won't then their entire business deserves to go down the tubes for being built on an unsustainable model.
The same thing exists here. It gets ignored. From time to time, as reported here, ICO go after offenders and presumably their fines are increased if listed numbers are being called. Unfortunately the calling companies fold to avoid paying but they're now starting to get directors banned and at some point in the future I'm sure there'll be criminal convictions. I still favour a charge back onto the caller's bill with added charges if the celled number is on such a list. At the very least the problem would be contained by the telcos' credit departments.
Switch to a system where it doesn't matter where the provider is.
Assign a short code. In the UK we have 1470 to mask one's own CLI and 1471 to give the number of the last incoming call. AFAIK the remaining 147n range is unused. Assign a number to one of them*. Dial that after a call and it's registered as probably problematic**. If the telecoms company recognises the source as problematic (and don't forget they do know where the call came from because they use it to bill the caller) then they credit the callee with a fee for receiving the call and add the fee and a handling charge to the bill. If the call originated with another telecoms company, even an overseas one, they bill that company. That company can pass the bill on with another handling charge added. Double (or more) the fee if the number called is on a do not call list.
In theory the victims get paid with credits against their phone bill and it's cost neutral at worst for the telecoms companies because their handling charge at least covers the costs unless the callers default. Defaults would be the equivalent of folding to avoid the fines. The telecoms companies have credit controllers so defaults will be limited. A telecoms company which doesn't keep proper track of the calls gets handed the bill and will change its ways PDQ or go out of business.
In practice, of course, this would kill the whole thing stone dead as the costs to the robocallers would go through the roof. The telecoms companies will realise this and know that if they're obliged to prepare for it they'll never get enough handling charges to cover their up-front costs. So proposing to enforce this will incentivise them to clamp down on the problem before the proposal gets taken any further. Once they're incentivised I'm quite sure they'd be very effective. On the principle that there should only be once chance to self-regulate any subsequent slackening off and the whole thing goes ahead.
* Vary for whatever numbering system works in your area.
** There's a risk of fraud if some toerag were to try responding to legitimate calls so the telecoms companies would need to gather a few reports from different people before actioning them.
"The one paying to have the phone call made are ignoring the fact that is has a contrary effect on the way their products are percieved and the company selling the phone call will certainly not reveal that fact."
You have just described the entire advertising industry and the marketing departments that pay them.
"if...Microsoft provides (or offers to provide on demand) the full sources for the kernel version in question, including any customizations they may have made."
That's a bit of a question. The article says We're told people will eventually be given instructions and code on GitHub to roll their own WSL 2 kernels, if the supplied 4.19 one doesn't float your boat. but what does 'eventually' mean? Does it mean when they ship it (and the article says they're shipping it on the Insider programme already) or at some indeterminate time in the future?
"IT bureaucracies that seek to have someone else to blame when things go bad"
Having someone to blame isn't the same as having someone to fix it. Either the bureaucracy does that itself or, given that it would be too much like hard work, outsources it. They're unlikely to outsource it to Microsoft but to a third party. The stupid thing is, of course, that the Windows supporting third party can't really go beyond what their latest MS certification course taught them whilst the FOSS-supporting third party can actually look at the source code. It ways more about the stupidity of large bureaucracies with more interest in off-loading blame than in supporting their employers.
"There is also constant pressure to make the software available on Windows... perhaps because it would allow the software to be used in university teaching labs"
What an indictment of University teaching labs.
"everyone here who has relatives running Linux keeps a good eye on them and is ready to sort out issues."
People here who have relatives running Linux have them doing so because it's a damn sight easier keeping an eye on them doing that than when they were running Windows.
Please get that into your head: the Linux option is easier.
I could visualise a switch where the legacy windows applications run under a real Windows Subsystem for Linux, i.e. a Linux kernel with a Windows compatibility layer and, of course, a proprietary UI. But although there would be a legacy support its real purpose would be as a client to all the Microsoft services. Not making people ponder whether they still need Azure etc but making sure they do need it all.
"The reason I and people like me use Linux is not about money, it's about control"
In my case it's because it runs a Unix-like user land. I really don't see the need to carry a Windows overburden to do that.
I do remember that in the old days Microsoft actually had their own Unix port, Xenix, and at the time it was fine. There was no indication of Microsoft wanting to apply EEE. Possibly it was a matter of them wanting their own server OS at a time when Netware dominated the X86 server world. When it no longer suited them they turned it over to their major distributor, SCO. Inititally the SCO product was also fine. There was even a specialist market in PC boards to facilitate various aspects of running SCO such as multiple serial port boards for character terminals. It was much later when that went to pot.
Often the case with big corporations is that the corporation itself isn't necessarily bad, it's the fact that they can change top management and be taken in totally different directions.
I can't help feeling that there's always going to be an advantage in being someone who knows several areas in detail rather than overspecialising. On the one hand you have value in being possibly the only one able to connect several of those silos to work together when they they need to and on the other you're not stranded when one of the areas goes out of fashion. OTOH you do have the advantage over someone who has sketchy knowledge of everything.
"HR also regularly sends out announcements by sharing a link to Google Docs."
HR and marketing - the weakest points in any organisation*. They'll only send out this crap indistinguishable from phishing if they don't know what's wrong with them and if they don't know what's wrong with them they'll have know inhibitions in falling for incoming.
* Apart from senior management, of course.
"XTAL's attempt to file for bankruptcy before the trial court could end. If the company succeeded, it could sell off its intellectual property – even if it featured chunks of ASML's code."
I can't imagine much success if the property was largely at risk of being invalidated by the ongoing court case.
"Write your destructive code so that it includes testing the condition that it is running where you intended it to run, before performing the destruction"
Which is another reason for doing it in a script. First write a SELECT* using the WHERE and HAVING clauses and run that. Only once your sure it returned what you expected do you edit that to the UPDATE or DELETE you intended. With a BEGIN at the front, of course.
*Just getting a count might be sufficient.
"Of course a script would be a more permanent solution, but sometimes you just have to run SQL on the production server."
In which case you do it in a script. It doesn't have to be a permanently saved. Your script starts with BEGIN TRANSACTION. You run the script then - and only then - your type your COMMIT.
It's a production database, belt and braces are not amiss.
*It never fails to boggle my mind the number of posts online about "I've found a cheaper O2 sensor that seems to work" or "I use a different kind of CO2 scrubber that isn't actually rated to go in rebreathers and none of the major manufacturers have ever tested on but it's cheaper so I'll use it".
Nobody ever posts "I tried it and it didn't work"? They must all work.
In the meantime, remember the saying "either go to sea with one compass or three."
"Senior company leadership was not involved in the review and first became aware of this issue in the aftermath of the Lion Air accident,"
For some minute value of 'leadership'.
This seems to be a management insistent on getting what it likes to hear instead of what it needs to hear. One thing it needs to hear is "when you're in a hole, stop digging.".
"In Rightpondia, manufacturers they can write whatever they want in the T&Cs but within the bounds of legality,"
The legality can depend on whether the transaction falls within consumer protection. I'd imagine a sale of a tractor to a farmer wouldn't. However in Rightpondia the tractor market is competitive so such shenanigans might amount to shutting up shop. If it wasn't they'd result in an anti-trust investigation.
There's an alternative line of attack. If the manufacturer doesn't want buyers to repair kit they bought, they, the manufacturers, repair it themselves (through agents if they prefer) at their own cost for the life of the item, life being as long as the kit physically exists. IOW a permanent warranty. Suddenly allowing right to repair might sound like a good idea.