Usually, they don't unfurl at all.
When using an alternate domain (https://stream-new.vercel.app) instead of (https://stream.new) it is more reliable. The alternate domain always seems to unfurl and sometimes it's the correct image, other times it's the image from the homepage.
My only conclusion is that slack is not properly recognizing the https://stream.new domain. This behavior is consistent across different slack workspaces.
This one shows no og:image for stream.new but when using stream-new.vercel.app it pulls in the cover image from the homepage.

Here's an example where the stream.new link doesn't unfurl at all, but stream-new.vercel.app unfurls correctly.

I'm talking with slack support about this, no resolution yet
Usually, they don't unfurl at all.
When using an alternate domain (
https://stream-new.vercel.app) instead of (https://stream.new) it is more reliable. The alternate domain always seems to unfurl and sometimes it's the correct image, other times it's the image from the homepage.My only conclusion is that slack is not properly recognizing the
https://stream.newdomain. This behavior is consistent across different slack workspaces.This one shows no
og:imageforstream.newbut when usingstream-new.vercel.appit pulls in the cover image from the homepage.Here's an example where the
stream.newlink doesn't unfurl at all, butstream-new.vercel.appunfurls correctly.I'm talking with slack support about this, no resolution yet