Upgraded my instance from 0.19.3 to 0.19.9 today, and fetching metadata for Youtube videos no longer works. Worked perfectly on 0.19.3 as of 3 hours ago (pre-upgrade).
This is how it’s supposed to look:
Good job, lemmy devs! 👍
We forgot to backport the above fix to 0.19. I did that now, sooner or later we might release 0.19.10 with that.
“sooner or later”
I just patched that into 0.19.9 (or, rather, changed 64 to 1024 and recompiled) and it fixed it on my end at least.
Ugh. I’ve already decided I’m not going to 1.0, so if it’s not in 0.19.10 maybe I’ll patch it in myself until I figure out a way to move my instance to Piefed.
I kinda wish I was on piefed, but the thought of migration sounds hella daunting. Ping me if you find a decent script or something
Will do. Prob even make a post about the process.
Also, yeah, I wish Piefed existed when I originally stood up my instance. Kbin was a thing at that time, but it had its own problems.
Blame YouTube for putting a megabyte (that’s a million characters) of data before the tags that are needed for this.
Be that as it may, it worked fine in 0.19.3 three hours ago.
Hmm. Do they accept an HTTP Range-Request?
Doesn’t matter if they do, Lemmy cuts off the connection after streaming the number of bytes it wants.
It sounds like the issue is the bytes that come before the data it wants, rather than after.
Maybe. But then you’d have to know where the tags are. And YouTube likes playing around.
Could probably search for it, if one could determine from a snippet of the content whether-or-not one is too far.
The instance I use (SDF) has stopped fetching Youtube video titles and thumbnails weeks ago. I just add them manually now.
The SDF instance runs 0.19.8.This is why I don’t “upgrade” my software unless there’s like a 9.9 CVE to worry about. Always some dumbass regression to spoil the whole thing (and not enough benefits to outweigh that).
Ugh.
Same here. But I avoid saying it too often because I always get jumped by a bunch of forced-upgrade lemmings who insult me and tell me I’m a dumbass because I expose myself to immediate and terrible danger from evil hackers in the next 30 seconds. Which of course isn’t true, but most people have been so drilled into blindly updating anything anytime an update is available without even checking what they’re installing that they’ll aggressively confront you if you don’t.
The morale of the store is, read the release notes to see what’s changing.
I don’t blinly update everything, but I do try to be on the more up to date end of things.
Case in point is nextcloud, that’s now on 31.0.0. I don’t ever jump to the latest untill the first point release is out, as nextcloud 31.0.1 is now out Wednesday night is nextcloud update time
The morale of the store is, read the release notes to see what’s changing.
You do that, I do that, but most people just click Update. And that’s if whatever wants to update itself lets you even opt out: Windows for example will nag you into submission at best, and more likely simply apply the update without asking your permission, and while you’re in the middle of important work if it wants to.
Like the update to the Moto Z3 which broke compatibility with all external cameras (those bolt-on thermal ones, USB borescopes, even the official Hasselblad Moto Mod for that series) and was never fixed because that also happened to be the last update ever issued for that model and Lenovo dropped support for it immediately thereafter.
Thanks a lot, guys!
I suppose that more automated testing could help catch some of these before releases.
