Attention PDS devs! We merged a lexicon change last week increasing the max image upload for Bluesky posts from 1 MB to 2 MB. This rolled out to our PDSs instances last Friday.

We'll begin enabling this in the Bluesky app soon. If your PDS implementation is still validating at 1 MB, plz update! ✌️

I've built a small system that helps people decide whether they should use a bloom filter on their use cases. It can give some false positives, but at least I never saw it give a false negative.

That must feel amazing

A Bluesky group chat, but the UI is not prepared for it, and it looks like a regular direct chat between 2 people. People are having to write in the messages who is sending them.

Well, the backend works 🤷

We are rolling out a fix, it should be fixed in a few minutes.

Will try to take a look at this during the week

They are calling it "clip clops" and you don't understand why

Can you try again now?
We've rolled out a fix. It is a weird case, hopefully we've got it.

Mind sharing the specific error you are getting on the network call, if know how to do that? I can give instructions

I will take a look now

One easy way to see that is to check the URL for that image. If it ends in `@jpeg` (as the one with the white background does), that user was not rolled out to webp yet.

... So 60% of users have their images being shown as webp. So for each of those users, all of their images (feed, banner, avatar) are in webp, while for the other 40% all their images are in jpeg.

@michelbestaat.thereforeiam.eu That's expected for now. We're doing a gradual rollout. We're at 60% of the image authors having their images shown as webp, and 40% still show in jpeg. Should be done within the next few days.

To be clear: the gradual rollout is by the image owner DID. ...

Yeah, my current guess is they are still migrating but possibly taking multiple days for some users

See also bsky.app/profile/bail.... It might be that there is no permanent issue and just that the migrations are taking a long time (multiple days) and images will just look broken while that is ongoing.

Thanks! Yeah, I believe this is the issue, just an ongoing migration. So there might be no real issue, just some delay in converging to the correct state that is causing a temporary failure due to the image URL change.

We have 1 Blacksky user experiencing the issue. Can you or someone DM me so I can send the user's profile?

Thanks, I'm also contacting them and will provide instructions to investigate.

@bergcathyb.eurosky.social I see now your banner and avatar, did they fix themselves or did you re-upload them? I still see some images on your feed are not loading.

... I believe this is some issue with the PDS migration, unsure yet if on our end or on the 3rd-party PDSs end. I've reported to our protocol team, and also want to let @eurosky.social and @rude1.blacksky.team know this is happening and might be on their end. Please reach out if you need.

... (but are listing them). The image format migration is causing the URLs to change and that causes them to miss our CDN cache and fall back all the way to the user's PDS to get the original image again and reprocess. And that call is failing in some cases. ...

If your own images have not been loading since yesterday, that's related to the jpeg -> webp migration we're doing, but the root cause seems to be the user's PDSs. I've seen 2 cases so far, and they were from users who migrated to 3rd party PDSs. The PDSs are not returning the blobs ...

Some specifics: I can find blob bafkreiauwb34hdu3zjvuwqrddnvee3deousrop4q257s2eqlsurpsj5uoy, which is of an image that is showing correctly, but can't from bafkreibysh2de4wg6rbcwzajgh3hwgorljluph5jfqbu6cl6p64n6vkzba. But listing blobs, both CIDs are returned.

I investigated a bit, it seems your PDS is failing to return some of your images. It will list all the blobs, but not be able to return all of them.

I'd recommend either waiting a bit if you migrated recently, or contacting the person who hosts your PDS. I can give specifics.

How long ago did you migrate to Eurosky? There might be some issue there, or still an ongoing migration issue.

Some images by @bergcathyb.eurosky.social load, some give a 404. It seems just a coincidence that the banner and avatar fail.

Adding `@jpeg` doesn't make them work for me.

Will take a look, sorry about that. This is the first issue I'm hearing about.

My best guess rn is that it is a caching issue, and it will fix itself in 24 hours.

Note that we're not deleting anything, so the original image is still there, untouched. Another guess is that it fails to convert.

Each one copes differently

I won't deal with any of this shit on my OOO day, you can be sure of that.

You had me in the first half there, ngl