points by detaro 5 years ago

The webhost had a different situation: neither code nor binaries were hosted with them. Although DMCA specifically doesn't apply to a German hoster of course, and uberspace is run by the kinds of people that'd probably try and take this to court instead of just rolling over.

bigbubba 5 years ago

I don't follow, a few days ago I downloaded the tarball of the code and 'binary' (it's a Python script) from their website. Both seemed to be hosted there.

https://youtube-dl.org/downloads/latest/youtube-dl-2020.11.1...

  • boogies 5 years ago

    Same, but interestingly enough today when I click the link my browser Palemoon’s popup dialog (asking whether to open in an extractor app or just download) says the file is from https://gitlab.com.

  • detaro 5 years ago

    That link redirects to a file on gitlab.com, and that they don't host it was given by uberspace as part of the reason for ignoring the request.

    • bigbubba 5 years ago

      Huh, so that's basically the excuse TPB uses right? "We don't host content, just links to content."

  • jefftk 5 years ago

    It's hosted on gitlab.com:

        $ curl -sS -D- -o/dev/null \
           https://youtube-dl.org/downloads\
           /latest/youtube-dl-2020.11.12.tar.gz
        HTTP/1.1 302 Found
        Date: Mon, 16 Nov 2020 15:04:10 GMT
        Server: Apache/2.2.15 (CentOS)
        Location: https://youtube-dl.org/downloads\
          /2020.11.12/youtube-dl-2020.11.12.tar.gz
        Content-Length: 3
        Connection: close
        Content-Type: text/html; charset=iso-8859-1
    
        $ curl -sS -D- -o/dev/null \
           https://youtube-dl.org/downloads/\
           2020.11.12/youtube-dl-2020.11.12.tar.gz
        HTTP/1.1 302 Found
        Date: Mon, 16 Nov 2020 15:05:03 GMT
        Server: Apache/2.2.15 (CentOS)
        Location: https://gitlab.com/dstftw/\
          youtube-dl/uploads/99d745f22ca3c2a8e9a2\
          3def5446289a/youtube-dl-2020.11.12.tar.gz
        Content-Length: 3
        Connection: close
        Content-Type: text/html; charset=iso-8859-1
    • JosephRedfern 5 years ago

      Weird. It's hosted by github.com when I run identical commands:

          (base) /tmp  curl -sS -D- -o/dev/null https://youtube-dl.org/downloads/latest/youtube-dl-2020.11.12.tar.gz
          HTTP/1.1 302 Found
          Date: Mon, 16 Nov 2020 15:52:13 GMT
          Server: Apache/2.2.15 (CentOS)
          Location: https://youtube-dl.org/downloads/2020.11.12/youtube-dl-2020.11.12.tar.gz
          Content-Length: 3
          Connection: close
          Content-Type: text/html; charset=iso-8859-1
      
          (base) /tmp  curl -sS -D- -o/dev/null https://youtube-dl.org/downloads/2020.11.12/youtube-dl-2020.11.12.tar.gz
          HTTP/1.1 302 Found
          Date: Mon, 16 Nov 2020 15:52:27 GMT
          Server: Apache/2.2.15 (CentOS)
          Location: https://github.com/ytdl-org/youtube-dl/releases/download/2020.11.12/youtube-dl-2020.11.12.tar.gz
          Content-Length: 3
          Connection: close
          Content-Type: text/html; charset=iso-8859-1
    • theli0nheart 5 years ago

      This is a little meta, but you can use the the -I / --head argument to tell curl to download headers only. This will ignore the rest of the response and means you can eliminate all of those other flags. E.g.:

          $ curl -I https://youtube-dl.org/downloads/latest/youtube-dl-2020.11.12.tar.gz
          HTTP/1.1 302 Found
          Date: Mon, 16 Nov 2020 19:10:37 GMT
          Server: Apache/2.2.15 (CentOS)
          Location: https://youtube-dl.org/downloads/2020.11.12/youtube-dl-2020.11.12.tar.gz
          Connection: close
          Content-Type: text/html; charset=iso-8859-1
      • jefftk 5 years ago

        Not quite: when you pass "-I" curl makes a HEAD request instead of a GET request:

            $ curl -sS -v -I \
                https://www.jefftk.com 2>&1 | grep '^>'
            > HEAD / HTTP/1.1
            > Host: www.jefftk.com
            > User-Agent: curl/7.58.0
            > Accept: */*
            
            $ curl -sS -v -D- -o/dev/null \
                https://www.jefftk.com 2>&1 | grep '^>'
            > GET / HTTP/1.1
            > Host: www.jefftk.com
            > User-Agent: curl/7.58.0
            > Accept: */*
            >
        

        It turns out that, often enough to be worth worrying about, servers do not return the same headers in response to a HEAD request as a GET request, so I always send a GET request when debugging strange behavior.