Carlos E. R. wrote:
On 2014-04-14 18:53, Linda Walsh wrote:
Carlos E. R. wrote:
No way to differentiate youtube traffic. Except... perhaps let the download start, find the IP used, and then create the rule. Possible... cumbersome...
Usually you'd use a predefined block of IP's to manage.
Surely youtube uses a large range of IPs, and they probably change and rotate. So, I would have to maintain that list, manually.
Rotate? I wouldn't think so. websites don't usually rotate IP's in their purpose -- they might have a group and shift/rotate within the group, but the group would usually be a fixed size at a given point (might expand, or less frequently, contract, based on load). Once you have the list, it would just 'stay'. You might have to add to it once in a while, but I doubt you'd have to worry about subtracting anything in the near future..
I did not identify "-O" as the appropriate switch... O:-)
Does that mean it might work, or that it does? .. I.e. when I had a 'too long' google filename, it worked.
Ok, I'll try now - wait [...] nope:
HTTP request sent, awaiting response... 403 Forbidden 2014-04-14 21:53:16 ERROR 403: Forbidden.
That is different -- that indicates you don't have access to that URL. It might only be good while you are watching it, OR it might require cookie support. (note, as you already have it solved, don't bother w/more testing... just file it away for future ref)
This command is easier, it understand "youtube" directly:
youtube-dl --write-sub --sub-lang 'en,es' -r 50K \ -f 135 http://www.youtube.com/watch?v=...
youtube does it's own handshakes within it's protocol, ...
Specially when they use "DASH" - see my other post. FF doesn't appear to have it, perhaps Chrome does.
Depends on V of FF, newer versions have it, but don't know when it went in... within the last year, I think.
In fact, when I watch a youtube video in FF, it often stutters or worse. But when I watch it in the dedicated android app of my mobile phone it works nicely, albeit on a very small display. So surely this device negotiates successfully, whereas FF doesn't.
---- "Negotiate" a 320x200 display on your PC and I'll bet it won't stutter.
Another thing to try is to 'strangle' FF. nice & ionice it down and limit it to 1 cpu. Then you could indirectly slow it down by running something else w/high cpu prio on the same cpu.
I'm not sure that ionice would do it, it is about disk i/o, I understand. AND, it requires running as root.
Ahhh.. no ionice alone wouldn't do it -- that was an "and" statement. To control wayward MS-OS processes all 3 are necessary -- now they post OS I/O through the 'System' process so it is "anonymous", and System will instantly "blue-screen' your system if you change it's priority or it's I/O privilege level. (Even tells you that "something" changed it's "holy-priority", and that's why it is dying (can't touch this!).
The combination of "trickle" and "youtube-dl" works very nicely. I can do other things while the download slowly progress, and in any machine. It is what I wanted: to do the download slowly. Not at a constant low speed, but it is acceptable. It can even resume an interrupted download!
Pity that the flash download add-ons to Firefox that I know about are unable to do such an, at least apparently, simple thing as throttling down the download.
Well, it's about "DEMAND", -- i.e. there are more people trying to figure out how to *speed up* a D/L than slow it down. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org