

If a physics simulation doesn’t agree exactly with experimental data, it is often difficult to figure out why and tweak the model until they agree. With AI, incorporating a few experimental examples into the training process is a lot more straightforward, and it’s not necessary to understand where exactly the model went wrong.
That’s not too bad if it’s only ever used as a rough guide in the early stages of design, with proper testing done later. But do we trust corporations not to get lazy and pressure their engineers to skip the accurate tests altogether, especially when they can then brag to their investors that AI is replacing expensive engineer time? What would Boeing’s management want to do with this tech?
There is a port to C++ underway, which still seems to be active:


Unfortunately it’s also critical for MRIs.


No, thanks for the tip. I’ll try that.
Edit: It worked! Disabling exploit protections got my bank’s app working. Thanks again.


The “advanced flow” with a one-day wait is just Google realizing they need to boil this frog a little more slowly to prevent a backlash. They still want a fully boiled frog in the end.


Mine refuse to run in GrapheneOS. Everything runs except my banks’ apps and eBay. It’s a slight inconvenience but the tradeoff has been worth it.
Edit: Thanks to NewOldGuard@lemmy.ml I got my bank’s app working under GrapheneOS.


I’ve been using NewPipe without problems. Is it supposed to have gone away?


We need development of Linux OSs for phones to ramp up. And we need Linux distributors and backers to fight back against “age verification” laws that are actually ID verification laws. There’s a global attack underway on multiple fronts against free software, private computing, and user ownership and control of devices.
In the meantime, for a stopgap, there’s GrapheneOS, but that doesn’t fix the problem of developers having to choose between Google’s way or unpaid obscurity.


I’d rather weed out the assholes.


From the article:
Google says it’s removing XSLT to address security vulnerabilities. The underlying library that processes XSLT in Chrome (libxslt) is an aging C/C++ codebase with known memory safety issues. Chrome’s team argues that because only about 0.02% of page loads use XSLT, it’s not worth the maintenance burden.
It’s debatable whether Google, with all its resources, really needs to do this, especially given that 0.02% of all page loads is still quite a lot. But there are certainly times when it’s better to just delete seldom-used old code from your project to lower the maintenance burden and reduce the surface area for attacks.


Previously they would have had to encounter a person who wanted to manipulate them. Now there’s a widely marketed technology that will reliably chew these vulnerable people up.


Worked fine for me, but I block ads and trackers on my home network so that probably helped.


The link sent Rademacher to a page on WebinarTV.us which featured a full recording of the Zoom recording, an AI-generated video summary of the meeting, “chapters” that sent the viewers to different parts of the meeting, and an AI-generated episode of the “Phil & Amy Show,” in which two AI-generated personalities discuss the content of the call, including quips and rapport between Phil and Amy.
So their business model is to steal other people’s meetings and add an overlay of shit? I hope it fails miserably for them.


VPNs? I don’t understand your question.


If you’re building your own router I’d recommend OPNsense. I hear PFsense is also good.


How about the bit where they say home routers have to be approved by the DHS or the “Department of War”? This is not normal.


So the application process is “drop us an email and we’ll tell you where to deposit the money.”


If you search for “install OPNsense” or “install PFsense” you’ll find quite a few guides. It’s not difficult to get going with these, but you should expect a bit of a learning curve if you’re coming from preconfigured home routers. It’s worth it though: these are far more powerful systems than regular home router software and give you much more control and advanced features like VLANs and intrusion detection.


That deals with the need for a WiFi access point, but not the main router functionality. Another approach would be a low-power PC running OPNsense or PFsense with a WiFi card repurposed as an access point. Or, if the new policy concerns only routers and not access points, a PC for the router plus a dedicated WiFi access point (some device that is not capable of being a router).
It’s exactly what we can expect from tech companies these days.