Quote:
Originally Posted by Jiaz
Wrong wording on "force plugin updates". They are not forced but normal plugin updates can be downloaded/installed/applied in background/without restart if there is no pending core update waiting for installation.
|
The wording
"normal plugin updates can be downloaded/installed/applied" sounds like a manual user action, while
"small plugin updates are sometimes auto-installed in the background without any notification" is strikingly similar to "it's possible to force plugin updates silently in the background" except "forced" wasn't meant as in "required before the user is allowed to continue" but as in "pushed without any user interaction/notification". Sorry for that sloppiness
Quote:
Originally Posted by Jiaz
See **External links are only visible to Support Staff**...
|
Turns out my wording was so similar because that's exactly the page where I read the info
BTT ...
Quote:
Originally Posted by Jiaz
See my answers in text
|
Summarizing:
1. the fix is part of the core
2. updating the core requires a restart
3. the fix wasn't part of the youtube plugin so it needed no update
1. & 2. are the parts that I already knew, hence I wrote:
Quote:
Originally Posted by JDmurphy
On August 29th (!) late afternoon, I noticed youtube dl speeds were back to normal again out of nowhere (...) and that without me updating JDownloader. So I assumed google had simply lifted the throttle, just like they did last time at some point.
|
... and this seems to be what apparently happened, because:
Quote:
I was still on build #46316 of June 26th.
|
... which means since August 29 youtube video download speeds were
back to normal = unthrottled even when still using the old, unchanged build.
Here's one of the abovementioned screenshots from September 1 (maxed-out 50 Mbit/s line) for proof, before installing the update:
Quote:
Originally Posted by Jiaz
Updates has been released on August 29 15:30 o'clock german time.
|
That's why I put a "
(!)" in "
On August 29th (!) late afternoon, I noticed youtube dl speeds were back to normal (...) without me updating JDownloader" to point out the coincidentiality/simultaneity
Thanks for this reply:
Quote:
There are several version of *player js* and when speed was low a new version got deployed that incorporates current date and also required error handling support. this broke our plugin and therefore speed was low. but it is one player out of many, so either the js (depending on the date) behaved differently and did not break or a new player has been deployed or the the video was using a different/working player.
|
Due to lack of specific knowledge I stumbled over
"this broke our plugin" tho, since you said earlier
"the fixed function is not part of the plugin".
Are you still referring to the
youtube plugin, or another one? Or do I have to read it as:
"Due to changes in the player.js library the JD youtube plugin wasn't working properly, and a core function had to be fixed to make the plugin work again while fixing the plugin itself wasn't required."
?
Please just ignore that whole section/question entirely if it's beyond the scope of this thread. The main point was to demonstrate how youtube video download speeds were back to normal again (for me and probably others) around the same time the update was released
without installing that update.