Discourse is expiring my Loom videos

Support

AI-generated summary

Discourse is Expiring Loom Videos

ScottWorld reported that Loom videos embedded in Discourse posts expire after 90 days, despite the video still being available on the Loom website. supermathie explained that this is likely due to Loom providing a time-limited authorization signature for the embedded video.

However, supermathie also mentioned that Discourse has since improved support for Loom videos. To resolve the issue, supermathie suggested rebuilding the HTML of old posts containing Loom videos, which should allow them to onebox using the embedded player and work indefinitely. ScottWorld thanked supermathie for the fix and expressed appreciation for their help.

1

Hi there,

I am an admin of a Discourse forum, and whenever I paste a Loom video’s URL into a post, Discourse embeds the entire Loom video into the post (instead of taking the user to the Loom website).

This is fine, because it’s convenient to be able to watch the embedded Loom video directly from the post itself.

However, the problem is that after 90 days, Discourse “expires/disables/retires” the Loom video so it is no longer playable within the post.

The Loom video still exists on the Loom website, and the Loom video is still at the exact same URL on the Loom website. But Discourse no longer allows the embedded Loom video to play anymore.

Is there any way to prevent this behavior from happening?

Thank you!

2

What’s probably happening here is Loom is giving Discourse an embedded “playback key” that only lasts for 90 days and this is being baked into the Discourse post.

Do you have a specific example you can show us of an expired video?

If you don’t want to post it public, please send a PM.

3

@ScottWorld, this is exactly what was happening. When you originally made the posts, it was generating an embed that used a URL with a time-limited authorisation signature from Loom, for example:

https://cdn.loom.com/sessions/transcoded/48d9de9a084af86fd477202764a9a3b1.mp4?Policy=eyJTdGF0ZQiOlt7IlJlc291cmNlIjoiaHR0W1lbncHM6Ly9jZG4ubG9vbS5jb20vc2Vzc2lvbnMvdHJhbnNjb2RlZC8zODRhNDc3MjAyNzY0ZjhkOWRlOWEwODZmZGE5YTNiMS5tcDQiLCJDb25kaXRpb24iOnsiRGF0ZUxlc3NUaGFuIjp7IkFXUzpFcG9jaFRpbWUiOjE5OTIyODc0OTR9fX1dfQ__&Key-Pair-Id=APKAJBGSW7XQIC5XK7FQ&Signature=h7BfrZiVgz7QFpUgl3BRYwsYC4yel%7E2y8Ctc7NKINXCe-zqvUAOaxQXgT1qUUk1IcSoou6v6Q-XqJNMFnmytU6YPt4n96GxujGoaF1haUZwB3l5HvhOPyJ3cu7RGJtLDQzg2tZFED-Iu%7E2iEZvuvrKh8yb8dhE-6Rt9hzmtJi-FnGXujIjpQ-LOpt0khBAkqhTE0ft0dWUUT%7EF%7ECmts97tWRDfrvmvz-PKkIV1yaie0WvLgKBOWtbptUnX4vliPsCWxVWcxR2NkCFj2UrzxTCCP2PTqXNnP0wkPI1VdvYvZAzda3RkLQclIHEsRsAglVkJNdy0O4qN93nUKaf863Tg__

but we’ve since improved support for Loom videos as other users reported this problem on meta you can see here.

If you Rebuild HTML[1] of old posts containing Loom videos, they should now onebox using the embedded player rather than the stream URL and work indefinitely.

  1. image
    image571×588 32.1 KB
    ↩︎

4

Hi @supermathie,

Sorry for my delayed reply, but thank you so much for looking into this for me — and thank you so much for fixing this for me as well!! :smiley: :raised_hands:

You are the best!! :smiley:

Best,
Scott