Per the comments at https://github.com/chrippa/livestreamer/issues/1478#issuecomment-247242827
and https://github.com/chrippa/livestreamer/issues/1478#issuecomment-247392244 , the expected solution for this is via livestreamer's '--http-header' option, which can be provided in one of two ways. On the livestreamer command line, add the option: --http-header=Client-ID=ewvlchtxgqq88ru9gmfp1gmyt6h2b93 Or in ~/.livestreamerrc, add a line reading http-header=Client-ID=ewvlchtxgqq88ru9gmfp1gmyt6h2b93 (Other Client-IDs could potentially work; that one is the ID apparently assigned to livestreamer itself. People have reported success using the ID assigned to the Twitch Web-based player, but that seems less appropriate.) Whether having this in the config file would cause any problems for streaming from other sites I don't know, but it seems to make things work fine for Twitch, with the livestreamer version currently available in testing. There's also a patch in that thread which looks as if it should both make the Client-ID potentially configurable (without exposing a configuration interface for it, though) and use the ID automatically. I haven't tested with it, although I wouldn't be surprised if it or a derivative had been adopted by the 'streamlink' fork. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw
signature.asc
Description: OpenPGP digital signature
