I was not using relay in a specific situation of common carriage of a message (California) or of intelligence (Massachusetts). A relay could be used in a situation of private carriage.

The YouTube embedding HTML would be something like the following:

http://a%20href=

The iframe HTML directive is a lot like the a href= directive. When the latter is clicked, the browser goes to the specified webpage. When the former directive is clicked, the browser creates a frame in the current webpage and puts the destination webpage in the frame. I don't see how there is any difference in the monetization of the YouTube video for the YouTube account holder.

Ask ChatGPT: "What does the HTML iframe directive do?" ChatGPT will explain.

First, this was not a uniform “YouTube embed” situation. The Second Circuit treated the claims differently:

The Melle Mel video was a YouTube embed, and that claim was barred because of YouTube’s license terms

The Michael Jordan video was not a YouTube embed, and that claim was revived because republishing the full video could act as a market substitute

So the opinion doesn’t say embedding is broadly protected—it shows that license + use + context control.
Second, the source matters. From the record, the Jordan video was posted to X by Daily Loud without authorization, and Townsquare then built its article around that content. There was even a separate action against Daily Loud that resulted in a default judgment, which underscores that this wasn’t a clean, authorized origin.

Third, beyond the video itself, Townsquare also extracted screenshots and used them as prominent visuals across multiple articles. The Second Circuit rejected the district court’s “de minimis” ruling for exactly that reason—the images were recognizable and centrally displayed. In other words, once the original work is clearly identifiable and used as a focal point, it’s not trivial copying, and you don’t get out of the case on that basis. The court also made clear that fair use can’t be resolved at the pleading stage on this record.
Finally, the “telegraph/relay” analogy doesn’t fit what happened here. A relay doesn’t:

Select the content

Frame it within its own article

Use it to drive traffic and revenue

Townsquare did all three. That’s why the court focused on real-world effect—whether users could consume the work there instead of going to the original source—not just where the packets originate.
So the takeaway isn’t “embedding is safe.” It’s:

YouTube embeds may be protected where a license applies

But outside that, courts look at how the work is used and whether it substitutes for the original

And those are fact-driven questions, which is why this case moves forward

At the end of the day:

It’s not about where the data lives—it’s about whether the defendant used someone else’s work to attract and monetize an audience without authorization.

That’s exactly what the Second Circuit said needs to be examined here.

I think we’re getting closer, but the gap is here: network architecture doesn’t answer copyright liability.

A few clarifications based on the opinion:

1) The Second Circuit didn’t say “all embedding is protected.”
It treated the YouTube embed separately and affirmed only that claim because of YouTube’s Terms of Service—i.e., a license-based defense. That doesn’t create a blanket rule for embedding. Outside a valid license, the question is still fair use and market effect.

2) “Relay” doesn’t resolve “use.”
Even if YouTube delivers the packets, the embedding site is still choosing, framing, and presenting the video as part of its own article. That’s why courts look at purpose and effect—especially whether the page functions as a substitute for the original. If users can watch the whole work on the defendant’s page, that can impact the market regardless of where the bytes are hosted.

3) No license = no safe harbor.
You asked how infringement happens without a relicense clause. That’s exactly the point—the legality of embedding often turns on whether a license exists and its scope. The Second Circuit allowed the YouTube embed because of the ToS; it did not extend that protection to other uses or say embedding is inherently non-infringing.

4) This case is moving forward because these are fact questions.
The court said you can’t resolve fair use on the pleadings where full-work use could be a substitute. That’s independent of any “common carrier” framing.

So unbundling can describe functions, but it doesn’t change the core test:

Is the defendant using the work, and does that use substitute for or exploit the original in the market—absent a license?

That’s what discovery is for here.

I meant.

Current Section 230 caselaw collapses transmission/carriage and editorial discretion/content creation into a single category of publishing in defiance of long established caselaw and without authority in the statute.