Right now I still have the warning for any previous files with the s3.amazonaws.com/… URL.
The Wasabi files have been fine this whole time because it’s my own bucket and a lot of people would have to flag that URL to get the same issue.
Right now I still have the warning for any previous files with the s3.amazonaws.com/… URL.
The Wasabi files have been fine this whole time because it’s my own bucket and a lot of people would have to flag that URL to get the same issue.
This makes sense. Thank you, download your plugin now.
Im telling you this, because, on my app, i have about 300 users, everything is hosted on my wasabi bucket, and all my user that uses edge and wants to display a media with a wasabi URL, they get this flagging file message
@redvivi What would seal the deal is some GCP function or something that could take Bubble files and upload them to Wasabi with unlimited file size in the background because other plugins want to upload to Bubble.
Like a cookie-cutter thing we deploy cause we have no idea how to code
That I have no idea… it’s your own bucket and everything?
Yep !
I saw on Edge you can click a link to say it’s not malicious, one of the options said you are the owner and it wants to you fill out a form… maybe go through with all of that… clearly something when wrong with SmartScreen and it’s falsely claiming stuff, Bubble’s method was abandon ship with the common URLs for everyone
This is quite annoying.
There are a few bubble oookies that also have the name of the bubble app. GDPR dictates that these need to be shown in the cookie banner, and the names are also in the privacy policy which is very annoying.
Hopefully no one’s property management app under the hood is called tentacleloverapp-test5
That would be awkward…
Another reason why we should be able to rename apps (ahem, feature that’s been needed since day 1)
The reason behind it is because of the Avast issues I think. The root cause of those issues were from the aws file URLs (i think). I just wish we could attach our custom domain to the cdn like cdn.yourdomain.com the same way we connect our domains with our app ![]()
This is literally how our app name is. “Xxxx-3.0-test”
Sure, but there’s most definitely other ways to go about this than using the current format in the URL…
The URL appName.cdn.bubble.io could also make a big impact for other large companies built using Bubble who wishes to hide this from users.
This is also an issue for us as our app name is an old brand name that we don’t wish to be visible to users.
@Bubble @nick.carroll any plans on addressing?
Supabase would never do this to us.
You can change it to “anything”.cdn.bubble.io
The real problem is that we don’t want users seeing “bubble.io”
Exactly. We do not want to advertise to our users and competitors that our app is created using Bubble.
Looking into it - very valid concern.