this post was submitted on 04 Mar 2024
43 points (97.8% liked)
Sync for Lemmy
15108 readers
3 users here now
๐
Welcome to Sync for Lemmy!
Welcome to the official Sync for Lemmy community.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Community Rules
1- No advertising or spam.
All types of advertising and spam are restricted in this community.
Community Credits
Artwork and community banner by: @MargotRobbie@lemmy.world
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I'd be cautious.
These malformed images may be malicious.
A malformed image should not cause a crash. I'm not sure what libraries Sync uses for this stuff, but the bug should be reported upstream (assuming it's not just some exception mishandling going on in Sync.)
They're on a platform I don't recognise.
I'm guessing that a non-Lemmy server doesn't provide some optional fields that Lemmy servers always provide, or that it provides some unexpected but valid data points in the API. The API docs aren't exactly very detailed, so I wouldn't be surprised if LJD assumed some optional field to always be present (because on every post on Lemmy that has been the case).
I took a look at the JSON Lemmy generates and it seems perfectly fine. Unfortunately, Sync is obfuscated so I can't get a clue at what object is malformed in the database to see what could be causing this.