"processed with imgix" is deprecated?

Few days back I noticed that the places where my application was supposed to show extracted face of the person was not showing the face, but it was showing originally uploaded photo.

For some days I ignored it thinking it could be temporary blip or it could be connected to the attacks that happened sometime back on Bubble and some things might be down, and then for some more time I thought it could be that my images have got saved wrongly and hence processing might not be showing for older images.

But the problem continued. So I thought of checking it up today and I noticed that in the editor the operator “processed with imgix” is being shown as Deprecated!

I thought it could be that it was some plugin and that plugin stopped working, even though I was reasonably confident that it was Bubble’s native feature. When I didn’t find any plugin of that type, I searched on forum, but didn’t find anything. Then I reached out to support and AI bot informed me that the feature has been deprecated and it is updated in the documentation, so. But it did not know since when it is deprecated.

I asked bot if there was a forum announcement of this, but it didn’t find any.

So here I am. Wondering if it is only me who is bothered by it.

It was a native feature of Bubble and quite a crucial one for so many situations in the apps where we need to do small processing on images before rendering e.g. showing a face mask.

But it was deprecated just like that without any warning and a good workaround? I see some workaround in documentation that says we should create an account with imgix and render images ourselves etc. But frankly, that’s not equivalent. And there is so much learning curve now to figure out how it is done and to do it with urgency as the app is already broken.

My application has stopped behaving the way I want it to and I need to figure out how to do this integration and change at all the places in my app?

I don’t even know what would be the implications on WUs and imgix cost because of this.

I am surprised that no one else is bothered by it. Is it not a needed feature or people have easy workarounds? I would like to know.

And very importantly I want to understand why did Bubble deprecate it just like that without a heads up and a workaround. It was a native feature as far as I have developed with Bubble, and if Bubble can choose to deprecate native features like this, I wonder what will Bubble deprecate tomorrow suddenly? What if for example tomorrow Bubble deprecated bbcode?

Sincerely hoping that I have misunderstood something and I am doing something wrong and there is an easy fix to this.

Would be very strange if it was deprecated by a human being with intelligence and logic behind their decision making.

If it was thoughtfully deprecated, I’d only imagine it’s a cost issue, if it’s a cost issue, we all might be in trouble.

If it was deprecated by an AI Agent now given much more autonomy in decision making, we are in for a very bumpy ride.

If it was done by an attacker, we are in for a bumpy ride.

No matter which way you cut it, the fact it happened is troublesome.

Yes, I am truly surprised at the way it has been done.

@fede.bubble can we get some details on this please?

My guess is they’re trying to shore up 3rd party access points which could act as points of vulnerability. That’s how most of these hacks are happening.