CanadaJim Of course, you can go to YT leave comments there, but this isn't a choice you're making: it's a workaround, an action forced on you by YT, in order to drive traffic away from our forum to their platform.
If we continue down this route, the ultimate outcome will be that the only reason to visit the forum will be to discover this Season's theme and to get the link to the playlist; following which, there would be no reason to revisit the forum again for the rest of that week. If you're looking to build/maintain a community here, relying on this workaround is not a sustainable option long-term.
I note that viewing VT content within a thread is still possible on UU (link here to an example - since I can't post a screenshot - note how being able to view an embedded video in the forum into which it's embedded - a video, incidentally, that does also display title/creator info in the embed thumbnail - helps promotes interaction within a thread). Perhaps someone who knows what to look for for, could take a look over there to see what they do to make embedded viewing possible.
When searching myself for the causes of, and solutions to YT 153 errors, a commonly proffered suggestion is that it arises from Using incorrect or outdated YouTube embed codes. This post on github offers a fuller, but more technical explanation:
Description
openedon Oct 29, 2025
Expected Behavior
Adding a Browser Source with a YouTube embed URL (in other words, in the formathttps://www.youtube.com/embed/VIDEOID) should load the resulting video and play as expected, without having to navigate or interact with YouTube's full desktop webpage.
Current Behavior
The embedded player fails to initialize with YouTube error code 153, indicating a misconfiguration.
Steps to Reproduce
Create or edit an existing Browser Source
Add a YouTube embed URL in the URL field ā as an example,https://www.youtube.com/embed/YDvsBbKfLPA/
Attempt to start the embedded video
Anything else we should know?
Guidance from YouTube/Google suggests they are enforcing a new restriction on player embeds:
"Our Terms of Service require embedders to provide a HTTP Referer. If this information is missing, viewers attempting to watch embedded YouTube videos will encounter blocked playback and an error screen (āerror 153ā). These viewers will still be able to click āWatch on YouTubeā to view the video on YouTube. Note that directly accessing the embedded player without an enclosing webpage or context (such as accessing it from your web browser's address bar) will typically not have a HTTP Referer and users will encounter the error screen; the embedded player is only intended to be used within an embedded context.
Embedders who want to fix blocked playback can provide a HTTP Referer to their requests to YouTube. See the developer documentation for technical details."
A more technical explanation can be foundin YouTube's API documentation.
The above suggests the Browser Source is not providing the information needed to avoid throwing this error. Other software that allows users to embed YouTube videos are reportingsimilar issues.
This mention of an HTTP Referer, led me to this coding suggestion for specifying our forum's HTTP Referer policy (whatever that may mean): to make sure that our HTTP Referer policy is not Referer-Policy: same-origin but Referer-Policy: strict-origin-when-cross-origin ("Referer's" not a typo btw, it's this idiosyncratic American objection to doubling a consonant between two short vowels when the final syllable of a word is a qualifier viz. traveler, marvelous, etc. - and of course, all code's written in American).
Error 153 Video player configuration error on YouTube embeds
I recently noticed that almost every YouTube video onmy blogwas displaying the same mysterious error message:

[snip]
[These edits to how I code YT links in my blog] mostly fixed the problemā¦
(Weirdly on some refreshes of the page I [still] get the⦠error. I'm not sure why that is.)
UPDATE: Avoid Referrer-Policy: same-origin#
As explainedover here, it turned out the reason I still saw some failures is that Django's SecurityMiddleware defaults to sending this header:
$$
Referrer-Policy: same-origin
$$
ButYouTube's documentationexplains that this header, which strips all Referer information on links to external sites, causes the error in YouTube.
The fix is to send this HTTP header instead:
$$
Referrer-Policy: strict-origin-when-cross-origin
$$
Or leave the Referrer-Policy off entirely.
Created 2025-09-30T10:07:00-07:00, updated 2025-11-30T
In any case, I'm sorry to keep banging on about this, for myself as much as for those following these exchanges., particularly on a beautiful Bank Holiday morning.
Hopefully, we will be able to find someone here with the coding skills/experience to resolve this.