Their reasoning for not having 2 keyholder is that 2 people are more likley to colude to change the results (in this case announce false results) than 3. Of course 3 people could still colude to do so, so it's a matter of reducing not eliminating the risk.
My understanding is that in 2 out of 3, the third can also decrypt/view the results, so (assuming number 3 doesn't lose their key) then 2 can't colude to cheat (unless they also colude to somehow "deprive" number 3 of their key (e.g. with a heavy wrench)). If number 3 does lose their key, then the risk of colusion is higher than "requires all 3", but conversly the risk of "accidental or deliberate failed election" is lower.
It's (always) about a balance of risks.
Parse_url isn't standards compliant, often fails with relative url's and most importantly only parses urls, not uris (with the exception of file://). I also find it's syntax clunkier than the new uri(), but that's just personal preference.
The pipe operator is indeed just syntactical sugar (and the article links to another article specifically about it which does cover the case of temporary variables), but with the coming partial function application feature it (in my opinion) will make easier to read/reason chains of code than temporary variables or nested function calls.
> The hallucination issue can be worked around by providing that demonstrates the agent's working (i.e. what tools they called with what parameters).
And this is (in my opinion) an intractable problem - You can get the AI to list the tools/parameters it used, but then you can't be sure that it hasn't just hallucinated parts of that list as well, unless you both understand that they were the right tools and right parameters to use, and run them yourself to verify the output. And at that point you might as well just have done it yourself in the first place.
I.e. if you can't trust the AI, you can't trust the AI to tell you why you should trust the AI.
(Source : I work in vaccine research, including challenge studies, in the UK, but only in IT/Digital, I'm not clinical).
In the UK at least (and as I understand it in most countries that subscribe to the principles of the Declaration of Helsinki), all of our studies have to have insurance to cover such eventualities (which are exceedingly rare these days). In addition, we provide clinical contacts for the participants throughout the trial and follow-up, and ensure that participant NHS medical records (and central NHS databases such as for the COVID vaccines) are updated with the necessary details for any future related care.
Money/Payment is always a careful balance. You don't want people taking part in the trials purely for the money (i.e. doing something they wouldn't otherwise be comfortable doing), but you need to ensure they aren't disadvantaged by taking part in the trial.
Technically, that's not true either! That's the current format, previous formats (still legal and transferable/usable) have included XN, XNNXXX, XXXNX, and others!
Yes, but they're only allowed to use the data for the (legitimate) purpose it was retained. If you ask them not to retain/use it for marketing purposes, they can still retain it for statutory purposes but they can then only use it for that (not for sending you advertising emails etc.)
Looks like I may be in the minority, but I've had nothing but good experience in the month or so I've had a 5G phone (Samsung S22, Three network, mostly in and around Oxford, UK).
There is a 5G mast visible in the distance, and I consistently get 500-800Mbs down and 20-50Mbs up at home. Similar story when out and about if there is a 5G signal (occasionally download goes down to ~5Mbs). It's better than the ~400Mbs my Virginmedia home line maxes out at.
Indeed, but even centralised coal fired electric generation produces less carbon per mile travelled than petrol/diesel engines.
We're not there yet, but proper grid management and diverse renewable sources mean that an increasing number of countries are heading towards large parts of base load being renewable.
In all scenarios (apart from not travelling at all) electric cars are a carbon win, and it looks like it will only increase.
I think you've proved your second point by getting your first wrong. The benchmarks posted are for a stack including PHP, not PHP itself (and not the fastest stack with e.g. pgsql).
Also, I don't think thosd benchmarks use php 8, which is the first version with the jit that the post above referred to.
For exactly this reason. "Girls - these are your toys, you play with them. Boys, you seem to prefer these, you will play with these". Continual use of unnecessarily gendered language is a major factor in perpetuating these differences.