jj4211

joined 3 years ago
[–] jj4211@lemmy.world 1 points 23 minutes ago* (last edited 22 minutes ago)

It's not the creators intent, is the closed captioner. The director does not play a role in what goes into the closed captions generally.

[–] jj4211@lemmy.world 3 points 6 hours ago

Yes, but those LLMs are not the official LLM of X directly tweeting on the platform publicly for all to see, attribute directly to the LLM instead of to whatever user induced the behavior.

[–] jj4211@lemmy.world 1 points 11 hours ago

Well a light refactor of deduplicating code would be a refinement that is generally easy to review and likely comfortably in the capability of the codegen.

Versus creating, which generally is harder to review and requires the submitter to explain the rationale behind the change.

Volume of code and nature of change.

[–] jj4211@lemmy.world 3 points 11 hours ago (1 children)

Of that comes to pass, they can change it.

The codegen is a particularly big problem for famous open source projects. All of a sudden you have a flood of people trying to get their name on your project and flooding you with low quality stuff. Codegen enables folks without good ideas to generate submissions that demand a lot of review. Being about to shoot down obviously AI content without deeper review is pretty critical to keep the project viable. There may be good things tossed out with the bathwater, but it is a ton of bathwater. Besides, if there's something real behind it, a good human is likely to emerge to take it forward more credibly.

Closed source or personal projects can enjoy a bit more judgement. You can evaluate the people independent of the submissions and may be able to have an even more nuanced take.

[–] jj4211@lemmy.world 5 points 11 hours ago

It's not like it is a legally binding agreement that needs a high level of quality in adjucation. If things seem off then it can be cited and you don't have to prove it. Conversely, if something passes human review despite being codegen, well then I guess the codegen isn't that bad

I've seen a pull request that was ultimately nonsensical but plausible and short, and purported to be needed in a configuration none of the maintainers had access to. It was a pretty harmless change either way so they were inclined to accept it. But they sought a little clarification and the clearly LLM response in comment got it shut down. No human stepped up to actually explain an understanding and the LLM sounded like a TV show writer writing tech, sentences that sounded credible but to anyone with understanding was nonsensical bullshit.

LLM code can sometimes be hard to tell in a short code change, but the prose when things are anything vaguely needing explanation is just so very very obvious.

[–] jj4211@lemmy.world 2 points 11 hours ago

They can't count on a jury that hates insurance companies. You would be surprised how many folks might be neutral on it, and jury selection can spend as much time as they want trying to find those people. Last time I might have served the lawyers dismiaaed essentially the entire jury twice over before accepting and that was over some anonymous little civil suit.

With respect to the family man angle, well there's not much to be done on that front by the defense. "He was a dick who had it coming" isn't a legal defense and even if attempted, people would probably think it is a bad look to try to smear the reputation of a dead man.

On the Internet circle jerks, a folk hero getting off seems really neat and with enough celebration seems even probable. Reality is not so.

Just wish it cut both ways, that health care executives be more accountable for lives lost due to their misbehaviors.

[–] jj4211@lemmy.world 2 points 1 day ago

Yeah, but you'll have to submit to every known provider and hope the user used one of the ones that provide this checking service, and didn't do something like ask a local model to just randomize synonyms in a text.

[–] jj4211@lemmy.world 1 points 1 day ago (1 children)

You still have choices.

Variable names are pretty free form.

A switch statement or if/else might be a choice that achieves the same thing. Waffling between them would be highly suspect, since a person isn't going to be so wishy washy. So you could use structural choices too.

AI code tends to look more obviously AI than prose anyway.

[–] jj4211@lemmy.world 6 points 1 day ago (1 children)

Well, they got the 1 off-site bit...

[–] jj4211@lemmy.world 1 points 2 days ago

You don't have a car. Do you receive packages? If you called for medical help, how would it get to you? Most folks if they don't have a car at least want option for a bus, which requires roads. We can't build rail to reach every household (you said freeway next to your home, so that doesn't sound like it's a very downtown situation).

Perhaps there shouldn't be as many cars on it as you deal with, but the roads themselves..

[–] jj4211@lemmy.world 4 points 2 days ago (2 children)

On the Flock cameras, pretty much agreed.

Data centers are a bit more interesting. Sure the land itself is "find a willing landowner or handful in a sea of any land that would be equally ok", but then you have supporting infrastructure. Perhaps not as large of a route to secure, and more flexibility to make pretty sharp turns and such, but still lots of room for people to get in the way of a critical dependency. So surely the datacenters are having issues getting power to their facilities in the face of so many people around their property not wanting to give up their land right? No solution for that.

Oh yeah, if they won't sell their property to facilitate it, the government will just take it over: https://www.washingtonpost.com/ripple/2026/07/16/when-can-a-power-company-take-your-land-for-a-data-center/

So yes, in both datacenter and train, people can make it very hard to get things done. Somehow they find a way for the datacenters...

[–] jj4211@lemmy.world 30 points 3 days ago (1 children)

Dude lamenting women not being attracted to intelligence checks out as he use a picture that clearly focuses on a woman's intelligence.

view more: next ›