I like invidious.snopyta.org because its parent website seems to be a privacy focused organization, but is it actually good for privacy, and are there any other Invidious instances with good privacy track records?

    • AgreeableLandscape@lemmy.mlOP
      link
      fedilink
      arrow-up
      5
      ·
      4 years ago

      Other than Cloudflare instances (while we’re at it, AWS/Azure/Google Cloud hosted instances are also no-go’s), a major concern of mine is the instance maintainers themselves using it to collect data to sell.

  • ufra@lemmy.ml
    link
    fedilink
    arrow-up
    4
    ·
    4 years ago

    Would be great to know. It’s hard to imagine an established, reputable organisation getting behind a service that circumvents youtube tos.

    Without such guarantees it does ease the mind a little to see the community takes GPL violations seriously ( https://github.com/iv-org/invidious/issues/1456) but your point remains that what goes on over the fence on server with so much data is opaque to us and could be malicious.

      • ufra@lemmy.ml
        link
        fedilink
        arrow-up
        2
        ·
        4 years ago

        Whether or not it’s legal in various jurisdictions I don’t know, but I have a hard time imagining an organisation like Debian for example, who already has “Team Social” (https://wiki.debian.org/Teams/DebianSocial) with Pleroma, Pixelfed, Peertube and others, creating an invidious instance. It would be great but I imagine they would come under fire and as in the case of yt-dl, I could imagine yt tos being ammunition.

          • ufra@lemmy.ml
            link
            fedilink
            arrow-up
            2
            ·
            4 years ago

            Maybe on Debian, I don’t have any specific knowledge of their view of such things. I don’t think they have network or technological barriers to running it if they want.

            In terms of youtube, the takedown specifically calls (bogusly) out tos violations.

            As there, the youtube-dl source code available on Github (which is the subject of this notice) circumvents YouTube’s rolling cipher to gain unauthorized access to copyrighted audio files, in violation of YouTube’s express terms of service,3 and in plain violation of Section 1201 of the Digital Millennium Copyright Act, 17 U.S.C. §1201.

            https://github.com/github/dmca/blob/master/2020/10/2020-10-23-RIAA.md