LinXitoW

There's this documentary about how badly that can go. Called Horizon Zero Dawn.

On the other hand, that way we'll finally get to "reconnect" with nature...forcefully.

That's how it's supposed to work. That's not necessarily how it does work, especially considering how hush hush and scammy all the AI companies are when it comes to posting real numbers.

They might also be in a Uber style subscription strategy. Make something super duper cheap, at great cost to yourself, so that you can grow a massive user base. Use that user base to get investments to keep burning money. Once you've got enough competitors out-priced long enough, jack up prices and enshittify like CRAZY to recoup the cost.

Competition is the only reason you can pay 100$ a month for like 4000$ worth of API credits.

How does "the world" get ready, when these limits are so hard core that Opus regularly stops working when I'm just trying to find and fix security exploits in my apps?

Currently available, unhindered models can already find a bunch of exploits, not because they're smart, but because they're cheap and smart enough to just keep going for hours or days until it finds something.

The defenders, especially in the FOSS space, only have one big advantage: Unified scale. If defender A finds a vuln, then defender B doesn't need to find it again. Attackers generally act alone, so they need to do all the work themselves.

If we remove a bunch of defenders, the attackers are back at it again.

Ironically, the gameplay is what meant I only managed to get through DAO and DA2 with a bunch of cheats. Realtime with pause is a horrible monstrosity. It combines the worst parts of action and turn based.

Veilguard was my favority gameplay wise, but the writing... well you know.

The important part is HOW they want to pace the frontier. Not by actuall slowing down themselves, but by having the government create expensive regulations, like having independent verifiers "verify" the models before release.

Now, something tells me that those verifiers would verify anything an american company in good standing with the Trump admin releases, and likely nothing else.

And obviously, since verification is so incredibly important, we can't allow models, open or not, from other non-verified companies.

Think of the profits...I mean, the kids, or something.

Every single issue they brought up in their blog post starts with even just 1% AI code. If they actually believed the absolutely absurd stuff they spew, banning it all would be the only logical solution.

The current solution solves none of the issues, AND pisses off most sane people (mostly because their arguments are fabrications). They dropped the cake and shit on it too.

Bad examples. Use meat consumption. It will blow any other kind of "non-essential" resource use out of the water, on ALL fronts.

It's really hard to believe that people care about the personal impact of their decisions, when it's only ever other peoples decisions that get talked about.

Considering that especially leftists have spent literal decades hating on vegans for telling them about their individual footprint, there is no real fallacy here.

AI haters have somehow discovered personal responsibility. Awesome. They've never ever applied that to anything else they PERSONALLY do, though. It's only things others do. For any personal choices, suddenly it's all the governments fault or the corporations fault. No personal responsibility to be seen.

My 5-ish years of veganism have easily made up for a life time of prompting. Yet, I still would never generate video or images in part because of their impact.

How many of you non-vegan AI haters are going to be vegan now?

The freaking point is that basically anything worth running will have that amount of access, even Flatpaks. And you don't freaking know what's malicious before hand.

For a single user, opinionated, modern, developer focussed OS, this is completely and utterly on par. Using docker as a developer without this is just plain annoying.

On average, you can either have a discoverable GUI for noobs, or a configurable, keyboard driven system that's a giant pain to learn and configure.

Omarchy aims to find a middle ground between those two.

It does warn you. It's an opinionated Linux for a modern developer/user. This modification absolutely makes sense in that context.

There's no universe in which just buying a second or a larger subscription isn't a billion times better and cheaper than any kind of comparable local workflow.

Privacy, experimenting with ML and "unorthodox" needs are currently the only acceptable reasons to do local.