360
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/piracy@lemmy.dbzer0.com
67 comments fedilink hide all child comments
 

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
[–] 24 points 1 year ago (8 children)

May this be the hoped-for token of enshittification that will spring Peertube and other platforms upwards!

  • permalink
  • fedilink
  • source
  • hideshow 8 child comments
    •
  • [–] 24 points 1 year ago (7 children)

    I doubt it. Bandwidth and storage costs for distributed video on the scale of YouTube isn’t going to happen without some kind of monetisation beyond stray donations.

    Places like Nebula have better operating models but they’re also very niche.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 7 child comments
    •
  • [–] 9 points 1 year ago (6 children)

    on the scale of YouTube

    That's precisely the trick. Don't try to copy Youtube. You're gonna lose. And it's not the Peertube intended use case anyway.

    Instead, Peertube and other such platforms should work as cross-indexing domain-specific, configuration-specific video galleries. A retro videogame video archive does not need 4K 120fps Dobly 14.3 audio; they can just encode most of everything in 480i 30fps and their storage costs will go down significantly. A news report / news reel archive can save some costs by encoding as SDR (or even lower) with ~80kbps mono MP3 audio or somesuch, since most of everything past the intro jingle is human voice.

    Play to your advantages. Trying to break into a monopoly game where the rules are broken, the only other player is broken, and the entry fees are broken is self-defeating.

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

    should work as cross-indexing domain-specific, configuration-specific video galleries

    Yes indeed - this is great idea and probably the only way a "web scale" distributed video service can work - unfortunately this doesn't quite exist yet. Even mature implementations like Mastodon have hard time dealing with "global" free text searching (or any kind of taxonomy). But maybe that's the idea that starts a truly free web!

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

    Sell ads, pay for storage and transmission fees, pay a pittance to the creators.

    Vs

    Require a single person to finance everything and hope for enough donations to keep running, no incentivization for content creation.

    Peertube is missing a couple of things to even be reasonably viable.

  • permalink
  • fedilink
  • source
  • parent
  • [–] [S] 2 points 1 year ago* (last edited 1 year ago) (2 children)

    A news report / news reel archive can save some costs by encoding as SDR (or even lower) with ~80kbps mono MP3 audio or somesuch, since most of everything past the intro jingle is human voice

    • Opus would have MP3 beat for speech at lower bitrates as per the HydrogenAudio KB, Opus is transparent for speech at 32kbit/s with stereo speech being transparent at 40kbit/s. Beyond that, a typical bitrate for Opus audio on YT is something like 150kbit/s and that codec is transparent for music at 160-192kbit/s. Point being if one works in spoken word and they want to save as much space and bandwidth as possible while still sounding reasonable, 40-48kbit/s Opus would be the ideal audio codec for that as it would give transparent speech at half the bitrate of the 80kbit/s MP3 that's quoted here.
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 1 year ago (1 child)

    ...Huh, it seems I'm quite out of date with the advantages of opus then!

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] [S] 2 points 1 year ago* (last edited 1 year ago)

    To directly quote the HydrogenAudio KB article on Opus:

    • 32kbit/s CELT encoding gives you: Essentially transparent speech plus moderately good stereo music
    • 40kbit/s CELT encoding gives you: Essentially transparent mono or stereo speech, fairly good stereo music
    • 48kbit/s CELT encoding gives you: Essentially transparent mono or stereo speech, reasonable music

    You're getting basically transparent speech at a bit over half the bitrate of 80kbit/s MP3 or less, and even with music, Opus like I said is transparent for music at 160-192kbit/s according to the same KB article I'm quoting, while MP3 needs 320kbit/s CBR for transparency for music, although if I'm transcoding FLAC files to Opus, I normally just max out the codec at 510kbit/s where MP3's transparency bitrate of 320kbit/s is also the bitrate it maxes out at.

    The only good reason IMO why one should use MP3 in 2025 when better codecs exist, both lossy and lossless, is when the device they're targeting is so old or crappy that it can't support anything better than MP3.

  • permalink
  • fedilink
  • source
  • parent