Yeah… AI hallucinates a lot. I wouldn’t rely on it.
1 Like
This problem can be fixed with the introduction of new plugin?
The bug doesn’t really seem to be a Discourse problem, it seems like Loom is expiring videos IMO.
1 Like
Just to note, this video is now broken for me, can anyone else play it? (Video on loom seems intact, just broken here)
Yes that’s the problem
Initially it works but after as days passes by, the player seems to get frozen
I have been sharing Loom videos for over 4+ months in Brave Community and have been actively updating all of the Loom video linked topics frequently and im sure i havent noticed the issue in the last 3 months use case as the videos always worked, so this might be an issue caused due to an update from discourse…
Added the exact same link again
video seems to be playing fine again, but soon this video can be expected to Frozen
this is not a timeout/expiry issue of Loom/discourse but rather cache/embedding functionality of discourse…
That video embed plays just fine for me and I’ve tested it on my dev instance and a hosted forum and it plays on both of those. I’m really not sure what the issue is but it’s possible the information appended after the ? in the address is expiring after a period of time. There may be a rate limit or something on those video links.
the video in the above reply works for now, but the problem which we are discussing is the video linked in my earlier reply on Mar 1 seems to be frozen
1 Like
yes I know, that is why I said this:
interesting indeed
I rebuilt html on the one that was first posted and it is working for me again. Definitely doesn’t have anything to do with Brave browser… I don’t know anything about Loom videos and this topic was the first I had heard of them.
1 Like
Maybe team needs to make a backend Loom plugin for Loom video use cases on discourse powered communities where it does what you did(Automates) for every 30 minutes sitewide for Loom video links ?
My understanding is when you paste https://www.loom.com/share/eb54c7d0d6f2417e9b56c3bc36b2d0d3,
the actual video file (mp4) is being figured out with a different strategy like:
https://www.loom.com/share/eb54c7d0d6f2417e9b56c3bc36b2d0d3
→
https://www.loom.com/v1/oembed?url=https%3A%2F%2Fwww.loom.com%2Fshare%2Feb54c7d0d6f2417e9b56c3bc36b2d0d3&format=json
→
https://www.loom.com/embed/eb54c7d0d6f2417e9b56c3bc36b2d0d3
→
https://cdn.loom.com/sessions/transcoded/eb54c7d0d6f2417e9b56c3bc36b2d0d3.mp4?Policy=eyJTdGF0ZW1lbnQiOlt7IlJlc291cmNlIjoiaHR0cHM6Ly9jZG4ubG9vbS5jb20vc2Vzc2lvbnMvdHJhbnNjb2RlZC9lYjU0YzdkMGQ2ZjI0MTdlOWI1NmMzYmMzNmIyZDBkMy5tcDQiLCJDb25kaXRpb24iOnsiRGF0ZUxlc3NUaGFuIjp7IkFXUzpFcG9jaFRpbWUiOjE3MDk1OTE0NDJ9fX1dfQ__&Key-Pair-Id=KQOSYIR44AIC0&Signature=SJYPMsuWnmbkoqXt0iKu%7EblkXNrLYaYxwbvKfvBdYP8yvBcDj0Q9rLSBHRQE9lGBRNNXHFs42t7%7EEKnLqoyGIqLfCMghwbYuKjRdVgxNLDCm1o19FCp5lEPEvJ7%7ElemdrZKcMSS9M86U5Y3kpELJfprqVVXMonyjflVGolOgs00Rw2kCKZvX9zMheBfONmilqwLybVa1sD3U5urvtjfQO2Pe%7EnO5K9YSCVg4tTBZumExVj%7EpNd-IT679gSxrDoEorz5O6VS8TScUbB4SYVLhnO2dbVhPWuJKFyPelKu6bj8eCSSo4t2ZH7ZiNbdyrEY8TYSqpMPVtymwf1JtQA0SiA__
The issue is that the final .mp4 file, loom attaches session attributes.
In the Brave topic, where the video freezes, the credential attached is not the same as the one attached on this topic. I’m talking about Policy=, Key-Pair-Id and Key-Pair-Id=.
My wild guess is that the session got invalidated, possibly each session has an expiration time (or for some others reasons). So, unless you refresh the post to generate a link with fresh credentials, you might get invalid links at some point.
One solution would be to use loom inside an iframe.
That’s could be a feature request to make a rule for loom, for sure! 
You can retrieve the data from the embed URL:
{
"type": "video",
"version": "1.0",
"html": "<iframe src=\"https://www.loom.com/embed/eb54c7d0d6f2417e9b56c3bc36b2d0d3\" frameborder=\"0\" width=\"1920\" height=\"1440\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>",
"height": 1440,
"width": 1920,
"provider_name": "Loom",
"provider_url": "https://www.loom.com",
"thumbnail_height": 1440,
"thumbnail_width": 1920,
"thumbnail_url": "https://cdn.loom.com/sessions/thumbnails/eb54c7d0d6f2417e9b56c3bc36b2d0d3-00001.gif",
"duration": 180.957,
"title": "Google - 8 January 2024",
"description": ""
}
Note: there is a rake command to re-generate the onebox: rake posts:refresh_oneboxes if it can help.
3 Likes
I have made the Loom team aware of this issue
Hopefully they could provide permanent solution/suggestions for discourse embedding use case by letting us know how this issue can be Fixed/resolved/avoided.
1 Like
I don’t think this is an issue with Loom, though.
There is a valid reason to use credentials such as personalized user experience, analytics, or security.
We should not use their .mp4 session link directly but instead their embedded version.
1 Like
These are embed codes but adding them does not make the video appear
<div style="position: relative; padding-bottom: 56.25%; height: 0;"><iframe src="https://www.loom.com/embed/eb54c7d0d6f2417e9b56c3bc36b2d0d3?sid=d7fce860-58ac-4548-bced-8d3fb8bcce78" frameborder="0" webkitallowfullscreen mozallowfullscreen allowfullscreen style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"></iframe></div>
Try something like:
<iframe
src="https://www.loom.com/embed/eb54c7d0d6f2417e9b56c3bc36b2d0d3"
width="800"
height="400"
scrolling="no"
frameborder="0"
allowfullscreen
></iframe>
And do not forget to allow the domain in allowed iframes settings.
2 Likes
Exactly where ? Can you share an image of Screenshot ?
This can be done only by admins of brave community because while i pasted your code, it appears Empty in preview page here…
Maybe if it worked here then i could confidently go ahead and make request to Brave Staff.
1 Like
Right, on Brave community, you will have to ask an admin.
If an admin here enabled iframes for this community and if the embedding worked here, it would give a strong reason and serve as a Good Example for Letting Brave team admins know why they should activate iframes
Like @Zee said, this issue started happening only recently
For the last 3 months use case, there have been no issues, so its backend issue of discourse
After discussing with Loom Support, it’s clear the update of Loom isnt causing issue but an update from discourse…
1 Like