Hi there, I was posting on [email protected] for a while, and I’d post links to youtube videos, and it’d automatically make thumbnails so that was cool.
But then “something changed” and it no longer made thumbnails, at least when seen on the web interface. But sometimes it does? The following image shows an example. In the first post, it has no thumbnail but in the second case it does:
MY QUESTION: how do make a Lemmy post to a video (especially on youtube) such that the post includes a thumbnail?
- Either automatically-generated, or custom-made by me.
- Preferrably via a computer client rather than phone.
I haven’t gotten any answers, but here’s what I’ve figured out myself so far. It’s useful to look at three different views of [email protected]:
- https://slrpnk.net/c/[email protected] - all of the youtube thumbnails are present.
- https://lemm.ee/c/[email protected] - only some of the youtube thumbnails are present.
- https://lemmy.world/c/[email protected] - most of the youtube thumbnails are missing
lemmy.world is running the older backend 0.19.3, which may explain its behavior. But slrpnk.net and lemm.ee are both running backend 0.19.5 so why are they behaving differently? If I compare the same post on the two servers:
I notice that the slrpnk.net one, while it does have a thumbnail, does not have the in-line images that I added and that are visible in the lemm.ee version. Possibly slrpnk.net does not allow uploaded in-line images? However, the lemm.ee version also has a video description in what appears to be Cyrillic. I read somewhere that this was due to a hosting issue. So maybe that is also responsible for the thumbnail issue. To summarize:
HYPOTHESIS: three things are responsible for image behavior differences:
- the older version of lemmy.world
- a hosting configuration of lemm.ee
- image upload restrictions of slrpnk.net
According to @[email protected], the issue with inline images not being visible from slrpnk is related to a bug in the image proxy code, though SLRPNK’s image size restriction could also be contributing to it as well.
Apparently the image proxy code bug has already been fixed upstream, so that shouldn’t be a problem for lemmy 19.6.
Thanks for the info! I suspect a lot of these issues will be resolved over time. But just like early html, there may always be some variation in how it’s ultimately displayed to the end-user.