Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Leaking YouTube creators' private videos

javoriuski.com

Post reply on HN
Print view View original

91–100 of 436 posts

Re: Leaking YouTube creators' private videos

#91

Post by jambalaya8 »

throwrioawfo wrote: post #58
Mg6yDfjp5U wrote: post #10

I recently left Google having worked on a number of projects with various YouTube teams. I think I can explain why it's being handled this way by YouTube. This is a fairly nuanced/involved issue, so the task of classifying the bug likely made it's way to one of the engineers responsible for the implementation of this feature. That engineer has already launched this project, and filed it away under their GRAD (perform…

I feel like things have become so much more cynical in the last 5 years, in this regard. I feel like part of it is the "over-systemization" of promos. I see the logic behind it to some extent - if there's a system, it's "fairer"/"more democratic". But, then we end up with ridiculous gamified promo systems.

Eh, clearcut promo paths used to be a bigger thing in the 90s and they did work for a little while, they just didn't handle exceptions well, and then the whole developed world up and thought they were also exceptions. Certifications used to matter more, now they are so cheapened that you cannot do much without them.

Re: Leaking YouTube creators' private videos

#92

Post by Terr_ »

rwmj wrote: post #15
algoth1 wrote: post #2

Google doesnt care about prompt injection attacks??? This is insane

Can they do anything about it? It's a fundamental flaw in how data is fed to LLMs. I'm getting PHP / SQL injection flashbacks.

Yep, and worse because the entire product relies on injection to operate, because everybody's excited about the "flexibility" of just telling it what your want.

Re: Leaking YouTube creators' private videos

#93

Post by goosejuice »

ghurtado wrote: post #42
Mg6yDfjp5U wrote: post #10

I recently left Google having worked on a number of projects with various YouTube teams. I think I can explain why it's being handled this way by YouTube. This is a fairly nuanced/involved issue, so the task of classifying the bug likely made it's way to one of the engineers responsible for the implementation of this feature. That engineer has already launched this project, and filed it away under their GRAD (perform…

Of all the fucked up things in this comment, giving a single Engineer lifetime responsibility for all bugs in code they wrote is probably the dumbest. And it's slowly becoming the norm. The last place I worked at, a large and well known Tech company, didn't even roll with QA's. That just wasn't a role anywhere in the division. You are fully responsible for all the bugs in all the code you ever wrote Cute at first. Un…

It's not cute, it's a sensible way to build greater understanding by learning from mistakes. The thing is, it has to be engrained in the culture and that also means it may need to take priority over other work. Responsibility doesn't need to mean you have to write the code, just see it through.

Re: Leaking YouTube creators' private videos

#94

Post by wahnfrieden »

throwrioawfo wrote: post #58
Mg6yDfjp5U wrote: post #10

I recently left Google having worked on a number of projects with various YouTube teams. I think I can explain why it's being handled this way by YouTube. This is a fairly nuanced/involved issue, so the task of classifying the bug likely made it's way to one of the engineers responsible for the implementation of this feature. That engineer has already launched this project, and filed it away under their GRAD (perform…

I feel like things have become so much more cynical in the last 5 years, in this regard. I feel like part of it is the "over-systemization" of promos. I see the logic behind it to some extent - if there's a system, it's "fairer"/"more democratic". But, then we end up with ridiculous gamified promo systems.

It’s not about fairness or democracy (maybe you meant meritocracy?) at all although it’s sold that way to participants - it’s primarily about ownership’s ability to cascade management duties, including mitigating latent negotiation powers by individual workers and groups of workers

Re: Leaking YouTube creators' private videos

#95

Post by UnlockedSecrets »

strictnein wrote: post #35
citizenpaul wrote: post #29

Earlier quoted context omitted.

What do you mean? Youtube is unquestionably one of the most successful projects ever launched? Seems like the process works astoundingly well.

Youtube wasn't launched by Google, it was purchased.

Youtube launched 1 year and 8 months before being acquired by google.... It's largely semantics to say that what Youtube is today, isn't a direct result of Google's ownership for nearly 20 years now....

Re: Leaking YouTube creators' private videos

#96

Post by zahlman »

quantummagic wrote: post #39
smallpipe wrote: post #7

Now if only OP talked to humans once in a while and not LLMs they’d stop writing “it’s not X, it’s Y”

Why is writing "it's not X, it's Y" a bad thing? Other than it happens to be used a lot by LLM's, it seems like a fine language construct. It's not like it's new; it was used plenty before the time of LLMs too. In my opinion, we shouldn't let the LLM companies claim parts of the English language for themselves, and make it effectively unusable by everyone else. That's what is happening because of this pervasive hatre…

It only happens twice in this article and they're both fairly reasonable. There are many other tells that I find a lot worse. In particular, "The Setup" is an awful choice for the first h2-level heading, especially when the description is that short. Better not to have a separate heading for the teaser at all.

(Also better not to lead with a 1.6 MB hero image that's completely irrelevant to the topic, for less than a thousand words of text that are still probably at least twice as many as merited; but that's probably not the LLM's fault, it's just how people do web stuff nowadays.)

Re: Leaking YouTube creators' private videos

#97

Post by c-hendricks »

zahlman wrote: post #64
b-kf wrote: post #9

bit meta but can I just applaud the article? Descriptive title, immediately comes to the point, no elaborate fluff, factual... what a nice change of pace. 95% of other users finding this would have done much worse. This is not clickbait, not calling for a social media campaign, has no embedded tweets of interaction with Google engineers trying to shame them, no singling out of individuals, ... Not sure if a user post…

With JavaScript disabled I had to inspect page source and remove "hidden" attributes from divs for content to show up. There's no placeholder text, no attempt to justify the need for JS at all, no consideration of the possibility that someone might be using a JS whitelisting tool (such as NoScript) on the modern Web despite its clear utility. For a blog post. Aside from that: > Descriptive title, immediately comes to…

I really feel like this genre of comment should fall under this "don't" from the HN guidelines:

> Please don't complain about tangential annoyances—e.g. article or website formats, name collisions, or back-button breakage. They're too common to be interesting.

You're willingly disabling a part of web atandards.

Re: Leaking YouTube creators' private videos

#98

Post by Terr_ »

zahlman wrote: post #71
rwmj wrote: post #15

Earlier quoted context omitted.

Can they do anything about it? It's a fundamental flaw in how data is fed to LLMs. I'm getting PHP / SQL injection flashbacks.

The described attack sounds like it's expecting the human to forget about having just clicked a UI element asking for a comment summary, and responding to a comment summary that tries to sound like an "important message from YouTube" as if it were actually such. It doesn't seem to involve the LLM actually having any agency to, for example, send an email to the creator. Mitigations would include ensuring it doesn't ha…

That sounds a bit like "nobody would ever fall for a phishing email." I don't think we should overestimate the technical sophistication and unceasing vigilance of the average YouTube user.

Even if it's just a non-clickable link to "more information", some data can be exfiltrated that way.

Re: Leaking YouTube creators' private videos

#99

Post by carl_dr »

dfxm12 wrote: post #90
Mg6yDfjp5U wrote: post #10

I recently left Google having worked on a number of projects with various YouTube teams. I think I can explain why it's being handled this way by YouTube. This is a fairly nuanced/involved issue, so the task of classifying the bug likely made it's way to one of the engineers responsible for the implementation of this feature. That engineer has already launched this project, and filed it away under their GRAD (perform…

It's ultimately Google's responsibility to ship bug free products. I don't care who implements a fix, but Google management should make sure someone fixes it.

No, it’s really not, it’s none of our jobs to do that. It’s our job to make our employer (even if you are your own employer) money.

It’s incredibly rare you have the luxury of even trying to deliver bug free code, let alone achieve it.

Re: Leaking YouTube creators' private videos

#100

Post by dfxm12 »

ghurtado wrote: post #42
Mg6yDfjp5U wrote: post #10

I recently left Google having worked on a number of projects with various YouTube teams. I think I can explain why it's being handled this way by YouTube. This is a fairly nuanced/involved issue, so the task of classifying the bug likely made it's way to one of the engineers responsible for the implementation of this feature. That engineer has already launched this project, and filed it away under their GRAD (perform…

Of all the fucked up things in this comment, giving a single Engineer lifetime responsibility for all bugs in code they wrote is probably the dumbest. And it's slowly becoming the norm. The last place I worked at, a large and well known Tech company, didn't even roll with QA's. That just wasn't a role anywhere in the division. You are fully responsible for all the bugs in all the code you ever wrote Cute at first. Un…

It's even worse when you don't work at a tech. Even the simplest of Excel formulae, power automate flows simply go abandoned once the creator moves on, or maybe a very expensive consultant is onboard to maintain what amounts to a handful of lines of code. It's embarrassing how little initiative the average information worker has when it comes to stuff like this.
Post reply on HN