Authenticated Attachment URLs
Hi guys,
For many areas of my bot, embeds access images that are posted into an #assets channel either by me or by select others in my community.
The CDN links for these are stored in mongo and referenced again and again, as the embed is sent.
They are only used and accessed within the discord client itself.
Does anyone have any more insight, confirmation, or thoughts on what the long term feasibility of this is?
Reading the announcement and all I can find, I don't know what to expect for the links hosted in this way.
The client behavior is not changing and will refresh posted URLs to be automatically valid, so your app doesn't need to worry about refreshing URLs itself if the link was valid at the time of posting.2 Replies
I'll be investigating some other solution to it for the long term now anyway.. I might have to go down the route of some image host where the community also have access to it
- They're not used outside of discord - if they are, the image breaking is fine.
- they're always sent via the API, as part of an EmbedBuilder or occasionally as the AvatarUrl of a webhook
- because of the above, they're always viewed through the discord client
I don't understand if it will continue to work past the end of year, for old and new
Well, this has come into enforcement today and has absolutely wrecked me.
URLs are only refreshed for the original message.
Any messages that refers to this original image - will not work. Image will be dead.
Are the assets static, or are new ones posted all the time? If it's static, you can use a CDN hosted on GitHub or Cloudflare.