known
known copied to clipboard
Known photo images appear to disappear from old posts sometime after a few hundred...
It appears that photo images in Known standalone installs are disappearing somewhere in the hundreds of photos ranges. Two examples have been found by paging back through the photo content view.
Example 1: @jeremycherfas’s photo stream starting at offset 550 shows photo images, however if you click "Older", you will see the photo posts, but no images, instead only alt text being rendered.
E.g. this photo post and older ones are missing their images.
Example 2: @benwerd’s own site, werd.io, shows photos backwards through offset=420, however if you click "Older" there, you will see at offset=440 (or perhaps the next one) that one or more photo posts are missing their images, and are falling back to rendering only their alt text.
E.g. this photo post is missing its image.
(Originally published at: https://tantek.com/2020/043/b1/)
I haven’t seen this yet; only have an archive going to offset 420
I looked at the source for my earliest photo in Known: https://stream.jeremycherfas.net/2017/untitled
That shows https://stream.jeremycherfas.net/file/bf35f40d158be32064b398f67efef842/ig1NhK4x.jpg
I looked at the database in phpmyadmin, and could not find any row that contained a value that began with bf35f4, neither uuid
nor _id
I did find the row for the post itself, but it appears to have no image associated with it. The blob is 1.5 KiB. I cannot actually browse the blob.
If there's anything I can do to assist, please tell me what. I don't think I have any database backups, but I will look.
Looks like I've been hit with the same issue on offset < 100.
Following up: it looks to me that there was a bug in the photo plugin in some versions of Known. My early photos are showing up OK - and later ones too - but there's a period in 2016 / 2017 when photos have disappeared. I don't understand why yet.
IIRC we changed the way thumb and image metadata was referenced, so maybe there was some overlap where the names of the metadata weren't being handled correctly