Well then, just FYI, it’s doing something different. Obviously lots of people are still able to see it, so it’s not the end of the world, just wanted to give a heads up that there’s been some kind of regression here.
They’re showing as an external link for me (on liftoff) that I have to click through to display. Whereas previously they were an image directly in the post.
Looking at the URLs, both types of image are webp’s hosted on sh.itjust.works, the only difference is the new ones have an additional format=jpeg parameter. I think the errors are on our side (ie the user’s apps, not the uploader’s), to treat these posts the same.
Have you changed something about the way you’re posting? Your posts from earlier than today seem to show up fine. Today’s posts don’t.
Todays posts are through an app instead of browser/desktop.
Well then, just FYI, it’s doing something different. Obviously lots of people are still able to see it, so it’s not the end of the world, just wanted to give a heads up that there’s been some kind of regression here.
They’re showing as an external link for me (on liftoff) that I have to click through to display. Whereas previously they were an image directly in the post.
Looking at the URLs, both types of image are webp’s hosted on sh.itjust.works, the only difference is the new ones have an additional format=jpeg parameter. I think the errors are on our side (ie the user’s apps, not the uploader’s), to treat these posts the same.
On sync, I didn’t notice a difference so jerboa probably needs a bug report
deleted by creator
Works for me on connect! Also, thanks for posting!
I’m on Connect too and the image loads and then quickly becomes a “failed to load”-placeholder black image. Very strange.
Maybe too mamy people are trying to send you nude girls?
Not a single one, buddy.