cross-posted from: https://lemmy.world/post/46349663

Odysee has announced something interesting: they’re building the ability to watch YouTube videos directly within their platform. Their reasoning is sound—it gives users frustrated with YouTube a better interface while still letting them access the content they want.

https://piunikaweb.com/2026/02/20/odysee-youtube-video-playback-feature/

https://www.tech2geek.net/odysee-to-let-users-watch-youtube-videos-directly-on-its-platform-a-major-shift-in-online-video-streaming/

This got me thinking: could PeerTube learn from this approach?


The Odysee Move: Strategic Context

Odysee’s announcement frames this as a “game changer for everyone that’s fed up with YT”—and creators’ YouTube earnings won’t be affected. The move essentially positions Odysee as a parallel interface to YouTube: you get better UX, less bloat, and potentially more privacy, but you’re still accessing the same content.

It’s pragmatic. Instead of competing head-to-head with YouTube’s massive content library, they’re saying: “Use our platform as your gateway instead.”


Why This Could potentially Work for PeerTube

PeerTube’s biggest weakness right now is the content problem. It’s a fantastic platform for creators, but users looking for variety still have to go to YouTube for the bulk of video content. This creates friction and limits adoption.

A YouTube integration could solve this by:

  1. Reducing friction for new users People could migrate to PeerTube gradually, discovering local content while still having access to their favorite YouTube creators.

  2. **Increasing user engagement** More time spent on the platform = more discovery of federated content.

  3. Privacy benefits Users watching YouTube through PeerTube (with privacy-respecting integrations) means they’re not directly feeding YouTube’s tracking apparatus.

  4. Network effects More users means more potential creators, which attracts more viewers, which attracts more creators.


The Elephant in the Room: Privacy

Here’s where PeerTube could actually do better than Odysee.

Instead of relying on YouTube embeds or direct scraping, PeerTube could potentially partner with, or integrate, privacy-respecting YouTube frontends like:

NewPipe - Open source, no account needed, ad-free

Invidious - Lightweight, privacy-focused alternative frontend

LibreTube - Modern, FOSS YouTube client

Piped - Another excellent privacy-respecting option

etc.

The advantage of this approach:

Users get YouTube access *without Google tracking them*

PeerTube positions itself as the privacy-conscious choice

It’s a genuine value-add over native YouTube usage

These projects are already solving the technical challenges


The Counterargument: Mission Creep?

I can hear the pushback: “PeerTube’s mission is to be a decentralized YouTube alternative, not a YouTube wrapper.”

Fair point. But there’s a difference between:

Being a platform for YouTube alternatives (feeding the centralized beast)

Being a platform that happens to also host YouTube access (while building something decentralized alongside it)

The second seems like a stronger position—you’re not abandoning the mission of building federated video infrastructure; you’re just acknowledging the world we actually live in.


What Would This Look Like?

Hypothetical scenario:

  1. PeerTube instances could optionally enable a “YouTube Integration” feature

  2. This would use privacy-respecting frontends (Piped, Invidious, LibreTube, etc.) as backends

  3. Users see YouTube videos in the standard PeerTube interface, with full privacy proxying

  4. The integration is federated friendly—it’s just another content type the ActivityPub ecosystem can reference


## Questions for Discussion

Is this a slippery slope toward becoming “just” a YouTube wrapper?

What are the legal implications of integrating with privacy frontends? (vs. embedding YouTube directly)

How would this affect server load and moderation practices?

Does this dilute PeerTube’s identity as an alternative, or strengthen it by making migration easier?

Are there other federated platforms that could benefit from this kind of hybrid approach?

I’m genuinely curious what the community thinks.

Edit:

Invidious might be the best route, if Peertube did up doing this, considering that Invidious also uses instances, as well

  • hendrik@palaver.p3x.de
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    2 days ago

    Uhm, and how is that supposed to work?

    I’d first like to see if Odysee can do it. From my experience, Youtube is CRACKING DOWN HARD on third parties. I can’t even watch or download a single video from my VPS. Individous instances have been notoriously unreliable for a long time. It’s a mess. Would make a nice feature, though. If it worked…

  • poVoq@slrpnk.net
    link
    fedilink
    arrow-up
    8
    ·
    7 days ago

    These alternative frontends constantly play cat and mouse with being blocked on YT and running them isn’t cheap due to the high bandwidth requirements.

    Peertube already allows creators to mirror their YT channels quite seamlessly, so that it the much better solution.

  • Default Username@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    4
    ·
    7 days ago

    NewPipe and its forks already support PeerTube, and I have some notes.

    As someone who has been using NewPipe (or a fork) since its first alpha, I almost never subscribe to PeerTube channels for a couple of reasons:

    Discoverability (this is the big one). In the related videos feed of the current video I’m watching, which is the main way I discover new channels, there is zero PeerTube content. Of course, this is due to the related feed being directly scraped from YouTube. I’m not sure how this could be solvable other than implementing some sort of recommendation algorithm that also applies to YouTube videos and mixes its feed with YouTube’s feed, essentially making PeerTube content transparent. I’m not exactly sure how feasible this is, especially while also recommending PeerTube videos from other instances and how to sort/mix the recommendations with the YouTube ones. Another option could be having a separate tab specifically for PeerTube recommendations in addition to the YouTube tab.

    Speed of loading the video (a bit less of an issue, but I still experience some buffering compared to YouTube).

  • Auster@thebrainbin.org
    link
    fedilink
    arrow-up
    2
    ·
    7 days ago

    I’d have some considerations.

    First, such an integration could indeed help making people stick longer.

    However, counterpoint 1, you’d need to be careful to not make Peertube an Youtube platform with optional Peertube content.

    Counterpoint 2, Youtube took several years to become a standard, and on an analogy, if you take the bake too soon from the stove because you’re getting hungry, the resulting product will be at least partially raw.

    And counterpoint 3, Google from what I can observe does not like 3rd party tools for watching/fetching their contents. So either they’d need to have an official integration (a risk due to EEE as someone in the .ml post mentioned, and/or a risk to privacy), or the project would need to keep a cat-and-mouse game, straining resources of a project that is already on the niche side due to the cost of hosting, attempting to be an alternative to a consolidated service (as bad as it may be), and the user finding an instance that both has public signups and rules that align being a hit or miss.

    A positive, though a smaller one since RSS bots already let you achieve that, is that then people can comment/react on Youtube contents here on the fediverse without worrying about their reactions misteriously disappearing.

    But then another counterpoint, fediverse softwares often allow embedded videos, so a RSS bot that brings videos over would indirectly make these videos integrate to a given fediverse platform.

    All things considered, while I understand the anxiety to make Peertube the relevant platform, I think patience and improving on what already is there are key to Peertube’s success.