An implementation of updatedb could make use of this, allowing to search files by their identified type.

There are probably ethical issues in getting people with Alzheimers to participate with solid state of mind in a trial that may be lethalâ"not to mention it might be more stressful for the researches as well..

Additionally I presume that when you have induced Alzheimer on the mice, you know that they have comparatively same "quality" of the disease in them; this is then a scientific experiment even others could replicate. You can't really get the same level of statistical certainty by using it on individuals, you need a lot of people. This iteration of the drug wasn't probably their first drug either.

It's part of flatpak: https://github.com/flatpak/fla...

It seems the main functionality is to allow reading a particular directory tree, and that for all write activity it asks a daemon if this is OK. Then presumably the daemon checks some rules or even might ask the user if it is acceptable to proceed.

Would you describe your refutal as being based on logic and facts, or rather an appeal to emotion?

This toy must be way better than parking a kid with a mobile phone, right?

And I imagine this toy can actually train your spatial thinking (based the parts of the video I viewed from the site), in some ways perhaps better than a Rubic's cube (and certainly more captivating), even if it has fewer movable parts.

So overall, seems like potentially a very good toy. Btw, it is not quite as fresh product as I thought, although I had not heard of it before, as the Youtube video linked from the page is three years old.

It could happen rather easily: e.g. the government could compel a datacenter to provide access to a rack server of its customer. Or a datacenter worker could be bribed to do it. Power outage can be explained by a power distribution malfunction.

E.g. Signal uses Azure and SGX is a component of their security, for dealing with things like contact discovery. But surely nobody would be interested in compromising Signal..

You're probably need to be quite a high-value target be attacked this way.

Pebble was able to kill itself, well before Google acquired Fitbit, and well before Fitbit acquired Pebble.

I think this timeline doesn't hold.

Pebble killed itself by severe mismanagement (they had a huge number of people in the company; obviously large plans for the future but they didn't pan out, while cash was burning) and the remains of the company (basically IPR) were then acquired by Fitbit at 2016, which kept the servers running for some years. Then Google acquired Fitbit at 2021 and after some time released the Pebble OS.

And now it appears Core Devices was able to acquire the Pebble trademark from Google, so they can sell these as genuine Pebble devices.

Why must they do worse?

To me it would seem for generating proofs LLMs would be much better at guessing than simply blindly breadth-first-search would be, with any manually-written heuristic.

Indeed I expect large parts of proofs would be applying existing patterns and LLMs would be good for applying structures they've been trained on. In particular generating the required tons of training material should be pretty straight-forward.

Such a model could then be a proof strategy in Rocq (previously known as Coq).

Good thing verifying formal proofs is basically mechanical work and the tools to do it automatically exist already.

Just in case you were lamenting that it's not written in Rust, fret no more, you can find one at https://github.com/souk4711/ha...

I wasn't able to make hakoniwas file-based restrictions to work, though. Complains about "fully incompatible access-rights". And its cli tool documentation is worse. Overall it seems the tool linked here is better.

It would have been so much nicer to mess up with the results to subvert the operation.

Perhaps it would have been too big of a business risk, though. Maybe they could've brought CIA along, or just blamed them anyway.

If you've followed the story, they person opposing this was not *forced* to integrate anything, as the code was not going inside his subtree.

Nevertheless, he was opposing in principle the existence of shared Rust DMA interfacing code. Instead, each Rust driver should use their own interfacing.

The maintainers can quit for whichever reason (or no reason at all), but if they do, in this case it's not probably a good reason.

IRC iss closed federation: you need to agree with the network admins to get your server linked. In addition, the servers are manually configured to conform to a tree structure network, not free-form one.

I believe nowadays the term federation by default means open federation.

Well, let's just agree to disagree.

Whether you like it or not, it seems quite certain to me that most code is written in ten years is going to be written with the help of of an AI assistant, LLM or some new approach.

It's just that useful.