Easily hour+ long headache on your first time.
Whenever I read this kind of thing (and people seem to say it pretty often), it seems really weird to me. Same goes for complaining about distro installers. An hour of possible headache/irritation and then you use the machine for years. Obviously it would be better if stuff was easy, but an hour just seems insignificant in the scheme of things. I really just don't understand seeing it as an actual roadblock.
(Of course, there are other situations where it could matter like if you had to install/maintain 20 machines, but that's not what we're talking about here.)
One thing is the pace is very, very consistent. Real humans don't usually maintain that level of consistency, they'll speed up, slow down, some words come out fast, some come out slow, etc.
Maybe I misunderstood you but my point was if it interpreted the language preferences I set in the normal config as "knowing" the languages I added and didn't offer translations, that wouldn't necessarily be what I want.
The languages I might want to see aren't necessarily the ones I know. People who are learning languages might set that (I did for the language I'm learning, anyway).
The timing and similarity highly suggests this is a problem with how almost all software has implemented the webp standard in its image processing software.
Did you read the article or the post? The point was that both places where the vulnerability was found probably used libwepb
. So it's not that there's something inherently vulnerable in handling webp, just that they both used the same library which had a vulnerability. (Presumably the article was a little vague about the Apple side because the source wasn't open/available.)
given that the programs processing images often have escalated privileges.
What? That sounds like a really strange thing to say. I guess one could argue it's technically true because browsers can be considered "a program that processes images" and a browser component can end up in stuff with escalated privileges. That's kind of a special case though and in general there's no reason for the vast majority of programs that process images to have special privileges.
People that love to read only the title. What could be better than a bunch of titles in a row?
As a general statement: No, I am not.
You didn't qualify what you said originally. It either has the capability or not: you said it didn't, it actually does.
You’re making an over specific scenario to make it true.
Not really. It isn't that far-fetched that a company would see an artist they'd like to use but also not want to pay that artist's fees so they train an AI on the artist's portfolio and can churn out very similar artwork. Training it on one or two images is obviously contrived, but a situation like what I just mentioned is very plausible.
This entire counter argument is nothing more than being pedantic.
So this isn't true. What you said isn't accurate with the literal interpretation and it doesn't work with the more general interpretation either. The person higher in the thread called it stealing: in that case it wasn't, but AI models do have the capability to do what most people would probably call "stealing" or infringing on the artist's rights. I think recognizing that distinction is important.
Furthermore, if I’m making such specific instructions to the AI, then I am the one who’s replicating the art.
Yes, that's kind of the point. A lot of people (me included) would be comfortable calling doing that sort of thing stealing or plagiarism. That's why the company in OP took pains to say they weren't doing that.
@Kerfuffle
@sh.itjust.works