978
Google just broke all third-party YT clients, including yt-dlp; a full JS implementation is now required. (github.com)
submitted 1 year ago* (last edited 1 year ago) by to c/technology@lemmy.world
276 comments fedilink hide all child comments
 

cross-posted from: https://lemmy.org/post/1872634

So, starting now, Google started mandating full JS for YT, effectively breaking all third-party clients and locking the site to their official client.

This reeks of DRM.

UPDATE: Installing Deno and installing yt-dlp through PyPi fixes yt-dlp but the very idea that Google is mandating JS to lock down YT in an attempt at pseudo-DRM is still crappy.

UPDATE #2: inv.nadeko.net is working again for now.

you are viewing a single comment's thread
view the rest of the comments
[–] 5 points 1 year ago* (last edited 1 year ago) (3 children)

PeerTube or LBRY (The protocol, not Odysee) might help in that. As in decentralized instances focussing on specific content. All connected via hubs/open-protocols.

Basically Decentralized or distributed networks are key. The next hurdle is populating those platforms with content.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 2 points 1 year ago

    Unfortunately video platforms are also much harder on small hosts. More storage, more bandwidth, harder to moderate.

    I feel like the solution might be a media management company, like buffer, offering to host videos directly and over a open protocols for a small upgrade in addition to posting to YT et all.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 2 points 1 year ago (1 child)

    Not just populating with content, but also create revenue in some way. Otherwise creators won't post their content there, they have to make a living from whatever platforms they're on after all

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •