Public Link for Uploaded Images on Dify Platform

[OlyMarco]

I'm currently facing an issue with the Dify platform's image upload feature.

Unlike the Coze platform, which provides a public link for each uploaded image, Dify seems to transmit the image directly to the model without generating a public link. This has been causing me some trouble, as I have an image interface that I'd like to implement on the Dify platform. This interface has already been successfully implemented on the Coze platform.

The lack of a public link for uploaded images on Dify is quite frustrating, and I believe it would greatly enhance the platform's functionality if this feature were added. I'm looking forward to seeing this improvement in future updates.

Thank you for your attention to this matter😘

[dosubot[bot]]

Based on the context provided, it seems that the Dify platform does have the capability to handle images via URLs, similar to the functionality on the Coze platform. This is suggested by the presence of the PasteImageLinkButton component, which is integrated into the TextGenerationImageUploader component. This component handles both local file uploads and remote URL uploads based on the settings.transfer_methods configuration.

The PasteImageLinkButton component allows users to paste a link to an image, which implies the platform supports handling images via URLs. The ImageLinkInput component within PasteImageLinkButton triggers the onUpload function with an imageFile argument, suggesting that the platform can process and potentially generate public links for these images.

However, the exact functionality of the onUpload function and how it handles the imageFile object, especially when the type property is set to TransferMethod.remote_url, is not explicitly defined in the provided code. The onUpload function is designed to handle or initiate the upload process for an image file represented by the imageFile object, with properties indicating its type, ID, upload progress, and URL.

The onUpload function's behavior and how it processes the imageFile object further would depend on its implementation in the parent component, which is not provided in the given context. Therefore, without additional context or code that specifically addresses handling based on the type property, we cannot accurately describe how the imageFile object is handled when its type is TransferMethod.remote_url.

In conclusion, while the Dify platform appears to have the capability to handle images via URLs, the exact process of generating a public link for each uploaded image, similar to the functionality on the Coze platform, is not explicitly defined in the provided code. It would be beneficial to have more information or context about the onUpload function's implementation in the parent component and how it handles the imageFile object based on its type property.

For more details, you can refer to the following sources:

• web/app/components/base/image-uploader/text-generation-image-uploader.tsx
• web/app/components/base/image-uploader/image-link-input.tsx
• web/app/components/base/image-uploader/utils.ts

I hope this information is helpful. If you have any further questions or need more clarification, please feel free to ask.

Sources

• web/app/components/base/image-uploader/text-generation-image-uploader.tsx
• web/app/components/base/image-uploader/image-link-input.tsx
• web/app/components/base/image-uploader/utils.ts

About Dosu

This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

If you want to continue the conversation, start your reply with @dosu-bot.