Here is what the thread over at Discourse on the security patch info says:
- the composer accepted image, video and audio uploads, so their URLs could be reused in a post
- media URLs on their own line (external images, uploaded videos and audio) render as oneboxes, which
PostAnalyzer#embedded_media_countignored because it counted from the stripped cooked HTML- video uploads render as
.video-placeholder-container, not<video>, so they weren’t counted either- a link whose URL doesn’t look like media but whose response is (an image served without an extension) became a media onebox after validation
And all of that sounds like what we’ve been doing to get YouTube videos and photos to work in posts. But now…
This change:
- counts rendered media (excluding rich onebox previews) and pending media oneboxes in
embedded_media_count- adds
Guardian#can_embed_media?, used by the post validator and exposed ascan_embed_mediaon the current user- refuses image, video and audio uploads in the composer when the user can’t embed media
And to us:
- video uploads and media URLs now count towards
newuser_max_embedded_mediaandskip_review_media_groups
What we’ve been using seem to be what Discourse calls “media URLs”, and it is explicitly blocking them. We can link to images and videos off the site, but we can no longer have it embedded in a post anymore, despite the fact that it’s being hosted elsewhere and we aren’t uploading anything.