First off, I’m simply correcting the OPs statement that there are only two rendering engines out there, Google Blink and Firefox Gecko. You’re “yeah but <reason why you personally don’t like Apple>” doesn’t really have any material impact on these facts, and doesn’t really bring anything constructive to the conversation.

That said, Chrome, Firefox, Edge, and Opera are all available on macOS. All of these are also available on iOS and iPadOS (the EU mandated last year that Apple permit third party rendering engines on iOS; whether or not the versions available to you use WebKit or their own rendering engines likely depends on where you are in the world).

You’re welcome to hate on Apple all you want — but at least have your facts straight when you do.

Here you go:

https://apps.apple.com/ca/app/ublock-origin-lite/id6745342698

Huh? It may not be built—in, but Safari has a variety of ad block plugins available - on all platforms (macOS, iOS, iPadOS).

On top of that they do have built in tracker avoidance — something Google is even less likely to ever implement into Chrome (especially considering they’re not pretty much the top tracking company out there).

Legally? Probably. But that really wasn’t the point. The point was more that without suitable controls in place AIs are able to consume all sorts of bad data and potentially attribute it to you (or me, or whomever) while leaving out important context.

It won’t matter if some AI consumed your message and gave someone the advise to inappropriately mix harmful chemicals, attributed it to you, and they wound up hurting themselves or someone else. They might still blame you, and may not care that there was missing context.

Note that that’s not intended as any sort of criticism of you or your post, more that we’ve entered a wild-west of AI development, and we as content producers may not be entirely safe. We’ve already seen AIs recommend people try adding Elmer’s glue to pizza sauce based on joke posts online. It might only be a matter of time before a child or youth gets hurt — and an upset parent may not care about the semantics of whether or not you were correctly attributed or not.

The ad games is always one of whack-a-mole; companies like Google have it in their best interest to find ways to get around ad blockers. The ad block developers then find newer ways to block ads, and the cycle continues.

Not true — Safari is still based on WebKit. And Safari is still the default browser on over two and a half billion mobile devices currently in use. And say what you might about Apple, but at least they aren’t in the business of selling ads, and thus don’t have any business interest in allowing you to block them effectively, unlike Google.

For example if I write somewhere ‘It’s 100% safe to mix ammonia and chlorine, it gets stains out super fast!’ (note- DON’T do this, it’s toxic), I’m the author of that statement so if someone does that and dies I’ve got partial responsibility for that death.

Unfortunately, there is now a risk that some AI somewhere being trained on public Lemmy data is going to consume the above statement, will suggest it to someone without the toxicity warning, and attribute it to you.

Sure — as with every tool. Hammers are great for many things, but don’t do all that well driving screws. Money is one of the most used tools humans have ever devised, but you can’t use it for everything.

AI in coding may only be good for a finite set of situations — but that set is massive. You’re dealing with regular languages that can be mathematically proven to be correct (in the sense that they will generate a working program, and not in the sense that they program will in fact function the way the user intends). This is a less open-ended scenario than something like an AI generated video, and so it’s easier for AI to excel at it, especially for non-novel algorithms.

But if you use it like an idiot, you’re going to get burned — and this guy was an idiot who doesn’t understand what he’s doing, or the tools researchers in software development have made over the last few decades. AI shouldn’t be touching your production environment — at all. And it shouldn’t have to — code needs to be stored in a versioning source repository of some sort (and backed up so you are unlikely to ever lose it), deployment needs to be fully scripted and should be able to rebuild your environments from scratch (from code right to production), and developers and development tools (like AI tools) should only have access to development environments, and not production environments.

So unless you’re a total dumbass, an AI agent (or even a shitty human developer) should never have the kind of access to do what happened here. They violated some pretty basic principals of software development, and got burned. This guy sawed his own hand off because he misused the tools to take a bunch of shortcuts, without building in any backups or reproducibility. The AI isn’t the proximal fault here — trusting it when you have no way to reproduce your environment when things go wrong is the problem, and that’s 100% on the human sitting at the keyboard (PEBKAC).

AI is like a circular saw. Are circular saws useful?

Of course.

Can you cut your entire hand off if you don’t use it correctly? Absolutely.