according to their stated security model, untrusted applications must not be allowed to communicate with the secret service.
That won’t be a popular stance to take when someone eventually steals a bunch of cached, unlocked credentials off of D-BUS because of an oversight somewhere in the npm/aur/pip/cargo/whatever ecosystem.
More rabbit hole:
What kind of car?
They used to be. Go back far enough in time and you could climb up under the hood into the engine bay to work on it. All that went by the wayside to get smaller packaging, lighter weight, and better fuel efficiency.
Now you need special tools or special code readers to solve/diagnose all vehicle problems. The large scale farmers are dealing with this now with the large combines and harvesters needing a tech with special equipment to read all the codes where the older tractors from the 70s and 80s can be repaired.
Well, nothing to do but start at the first one and work our way down…
Dramatically reduce the legal ability to shoot anything other than a hog.
Chronic wasting disease in deer is bad enough as it is. We did in their natural predators.
market it as doing your patriotic duty to take out a hog instead of buck, or something.
Already been done: https://www.youtube.com/watch?v=jsn9BrNsVPo It’s a scale problem.
https://wildlife.onlinelibrary.wiley.com/doi/10.1002/wsb.787 tl;dr: there were more, healthier hogs when a bounty was paid out for them.
Hm. Had been thinking of it in terms of controlling the local file system.
Thanks.
people then concluded that FROST is harder to exploit in real-world scenarios than in the lab
What happens if there’s an extra 4GB of stuff laying around?
A jeep renegade I rented did ok
You must’ve gotten a good one.
Try the c++23 standard. There’s been a lot of cross pollination. Contrived example follows:
#include <format>
#include <numbers>
#include <print>
#include <string>
int main(int argc, char *argv[]) {
double pi = std::numbers::pi;
std::string fstr = std::format("{}, {:>.2}, {:>.5}, {:>.10}", pi, pi, pi, pi);
std::string h = "Hello";
std::string w = "World";
std::println("{}, {}!", h, w);
std::print("This won't have a {},", "newline");
std::println(" but this will add it."); // Add a newline.
// Can't put a non-constant string as the first argument to
// print or println so they can be checked at compile time.
std::println("{}", fstr);
return EXIT_SUCCESS;
}
Choosing here to reply because I agree with you about the fine motor control, and I also agree with @9tr6gyp3 about being able to read historical documents (roll credits).
One argument I’d bring up in the whole cursive/shorthand debate is whether there are any other languages that have glyph sets that have already been described with Unicode that would be just as fast as shorthand? I’d also want to consider the ease of doing OCR on the documents for digitization. I don’t see how shorthand would be good at either of those things.
¯\(ツ)/¯
If GNOME wrote it then they probably trust it. If you’re using GNOME, then you’ve accepted their security model on some level.
At least you know to go look for it. Attackers will only get more sophisticated:
https://ioctl.fail/preliminary-analysis-of-aur-malware/