I see the appeal of that, but this is generally a teriible idea. If you copy that url and image gets deleted you will never know where its being used.
We need something better than just copying the url. Maybe variables with bindings would be the right solution.
we need references, not copy-pasted urls
the urls might change any time even due system changes
why do you btw need a twitter:image? isn't it already set automatically via open graph tags we just added?
oh you want to select a different one for twitter vs facebook
Ah fuck if the url changes thats a bit painful.
Just for some extra context, this is typical in most builders.
Another example scenario:
I have a PDF I want to link to and send to my users. With other builders I can upload it to media and grab the link, add it to the email.
Or custom coded stuff, if i want to build something that needs me to write in the html block, there's no where I can upload an image.
Yeah that and also twitter has extra card options I can define alongside the image
Example of default twitter card embed:
(customized card incoming give me 2min to publish)
I think for such advanced customizations we need a separate plugin that would show an insanely complex UI with customizations for every social network and what not
I honestly think the setup where we can define anything in meta pairs is 99% perfect.
It's infinitely better than what others provide forcing you to just pick from defined meta tags.
This is the exact same tweet (didn't edit it). But I applied twitter metadata on WS.
(large featured image card).
@Ivan Starkov do you see a danger in exposing the asset url to the user via copy button? is the url gonna change eventually?
Im not getting the question
Just for clarification. I can control this layout change on X cards without needing an image url. (it can use the OG prop)
But I find a decent amount of use cases where being able to copy the image url is benefitial. Ideally I don't need to also maintain a media server for assets I want to link to from other places.
@Ivan Starkov check the top of the thread
https://discord.com/channels/955905230107738152/1170274130646552618/1170274130646552618 i explain here 🙂
if we add a button that lets user copy the image url, will url be stable? they will use it in uncontrolled ways
The main issue that we are preventing our (transformed images) (and as I know not exposing raw asset urls) to users. So our assets can’t be used on 3rd party sites. It works for Social image as twitter etc download our image
But this will not work if user place url somewhere else
Is it possible to generate a direct link to the unoptimized media? Or are we not storing them perhaps?
Idea that we dont want to be a image hosting, or transform hosting
The issue that untransformed media uses same path as transformed. So url will work only with social
But Im user, I have url through UI, so I can use it everywhere
Is this a statement or a concern?
I mean you have image url, what prevent u to paste it to the other resource
And then write to our help that urls you provide are not working
But we didnt give you this url
Yeah correct.
So the theory is that we're not giving it to users in builder because we're concerned about them abusing it?
If it doesnt work, we are free to say we didnt give you our url
Yep we dont want to be free image transform service
Yeah.
But I still have the same problem. Being:
In other builders I can easily copy url and use it for other things. But i can't with WS.
For context, this is more of a marketing thing than "free image hosting". Because i want to be able to link to media assets in emails and stuff. With other builders I can keep it all centralized in their media.
Leading back to the orginal question:
- Will the image url's change in the future?
At builder we dont know even right image url
I think all those builders just use that url and it may break in the future.
change the domain - all urls broken
ideally one would use a separate permanent url feature or servie like url shortener to have a perm link that you can update any time.
I guess if user is using the url that can change in external media its their problem?
or we need to create a separate feature with perm urls
its not connected to user's domain
they don't have a dynamic resizer
they resize at publish time
I guess we could configure a fixed subdomain that will always reference the original image in a stable manner?
Only if this doesn't impact image URLs on published sites as there's SEO implications when the image is being served from a different domain.
I thought that custom fields in the future can have types like image type
As same issue with json+ld links etc, most need to be an absolute url
But until publish we dont know absolute url
User can add/remove/select different domains this is the main issue with all that social hrefs/src
oki oki. In that case i think we can close this thread and revisit when we get closer to CMS.
@Ivan Starkov webflow gives user ability to copy url like I pasted above. Its available without publish, right after upload, because its the url to original image and its not connected to user's domain.
We don't need to use this url for our rendering, but it seems like we need to provide this url to users so they can copy the original image url.
Its basically like a perm link.
Why? Its builder related url, from what I remember only builder can access this urls
There is no good use case of this url
For seo reasons its bad - 3rd party domain, for support reason its bad - its our internal details
yeah, its like a separate feature - perm link
we don't use it internally but user might
I don't have a good answer for alternatives, but I can see that people will ask for this
If they will we can improve asset manager allowing to select domain and copy
There we can explain that images are referrer related
we can have a separate standard domain that will be used to provide a perm link to that image, without using that domain ourselves
But why user will need that domain?
3rd party stuff, email as example
Isnt images are injected into emails as base64
could be, but could be a link
As my email clients always block all 3rd party images
@Alex wouldn't it be better for emails to download the image and embed it in whatever platform is used for emails? I don't see linking it as strong. use case either
and using it in the meta - should be possible by choosing the image from asset manager or using a binding
In our design we already have a Download button, so we definitely need a way to download the image from buidler
but maybe actually linking is completely bad idea
we should indeed protect our CDN/Storage from linking in random ways
otherwise over time we will be drained for unpredictable reasons
these things at scale can cost money
actually I now understand the problem better: we can't expose a direct link to the asset, because it won't go through our worker and won't count traffic towards user's limits
we need to make sure all traffic goes through user's worker and so we can create a traffic limit at the end that includes everything that belongs to one project
and since worker is accessible through user's domain, we can't expose an asset url that doesn't go over non-user's worker domain
