The Curtain Has Closed on Meta’s Movie Rating-Inspired Content Filters
The Motion Picture Association, which came up with PG-13, was not happy with the association.
The curtain has been drawn on Meta’s movie rating-inspired content filters for teens on Instagram after the Motion Picture Association, which created the ratings, essentially said—loudly and legally—that it didn’t want its ratings anywhere near the social media company’s products.
The clash between Meta and the MPA began in October 2025, when Meta rolled out new content filters on its Teen Accounts for minors on Instagram. According to the company, the new filters would curate age-appropriate content for users guided by PG-13 movie ratings. It appeared to be a way to take advantage of the credibility of the film industry’s existing age ratings, with the rollout accompanied by promotional influencer posts and ads likening the experience to teens watching a movie.
That didn’t fly with the MPA, the film industry group that introduced the PG-13 standard roughly four decades ago. It was squarely unhappy with Meta’s new content filters and sent a cease and desist letter saying that the labeling was “literally false and highly misleading.”
On Tuesday, Meta finally gave up their bid following months of tension. The tech giant and the MPA announced in a joint statement that Meta would “substantially reduce” references to the PG-13 standard in its descriptions and would include a disclaimer when it does so.
“There are lots of differences between social media and movies. We didn’t work with the MPA when updating our content settings, and they’re not rating any content on Instagram, and they’re not endorsing or approving our content settings in any way,” the disclaimer will read once the agreement takes effect on April 15. “Rather, we drew inspiration from the MPA’s public guidelines, which are already familiar to parents. Our content moderation systems are not the same as a movie ratings board, so the experience may not be exactly the same.”
PG-13 movies include some “mature themes” while still keeping it moderate enough that it’s appropriate for teens. A good example would be most Marvel movies, which involve some violence and romantic scenes but nothing too excessive. Meta says that because of the obvious differences between a movie that is two hours long and a photo carousel or a 15-second Reel, they couldn’t issue the PG-13 restrictions in its entirety and instead took inspiration from that rating in deciding what kind of content should be available for teens using the Teen Accounts.
A Meta spokesperson in the statement said that while how the company presents the restrictions in Teen Accounts will change, the criteria that they use will stay the same. The MPA, meanwhile, wants it to be clear once and for all that these two systems are not the same.
“While we welcome efforts to protect kids from content that may not be appropriate for them, this agreement helps ensure that parents do not conflate the two systems – which operate in very different contexts,” MPA CEO and chairman Charles Rivkin said in the release. “The MPA is proud of the trust we have built with parents for nearly sixty years with our film rating system, and we will continue to do everything we can to protect that trust.”
There might be some reason for MPA’s reluctance to be associated with Meta’s social media controls for minors. Namely, Meta’s reputation for child safety has been through the wringer the past couple of months.
Earlier this month, the tech giant was handed losses in two separate landmark cases, one in New Mexico and the other in California, regarding the lack of safety measures for minors on the company’s social media platform, Instagram.
The New Mexico trial claimed that Meta executives created a breeding ground on Instagram for sexual predators looking to exploit children. The California case claimed that deliberate design choices on Instagram, like infinite scrolling, got kids addicted to social media from an early age and worsened serious mental health issues like depression, anxiety, body dysmorphia, and thoughts of self-harm.
“Meta executives knew their products harmed children, disregarded warnings from their own employees, and lied to the public about what they knew,” New Mexico Attorney General Raul Torrez said in a statement following the verdict.
The social media litigation also came on the heels of a Reuters investigation from August 2025, which generated significant backlash with its claims that Meta permitted its AI chatbots to have “sensual” conversations with children.
Gizmodo
https://gizmodo.com/the-curtain-has-closed-on-metas-movie-rating-inspired-content-filters-2000740392Sign in to highlight and annotate this article

Conversation starters
Daily AI Digest
Get the top 5 AI stories delivered to your inbox every morning.
Knowledge Map
Connected Articles — Knowledge Graph
This article is connected to other articles through shared AI topics and tags.
More in Products
How to Add Structured Logging to Node.js APIs with Pino 9 + OpenTelemetry (2026 Guide)
<p>Logging is the first thing you reach for when something breaks in production. Yet most Node.js APIs still write plain-text <code>console.log</code> statements that are useless in a distributed system. In 2026, <strong>structured JSON logging correlated with distributed traces</strong> is the baseline for any serious API. This guide shows you exactly how to wire up Pino 9 + OpenTelemetry so that every log line carries a <code>traceId</code> and <code>spanId</code>, making root-cause analysis a matter of seconds rather than hours.</p> <h2> Why <code>console.log</code> Kills You at Scale </h2> <p>Before diving in, let's be concrete about the problem. A log like this:<br> </p> <div class="highlight js-code-highlight"> <pre class="highlight plaintext"><code>[2026-04-01T08:00:12.345Z] ERROR:
Why Most Agencies Deploy WordPress Multisite for the Wrong Reasons
<p><em>(Originally published on <a href="https://fachremyputra.com" rel="noopener noreferrer">fachremyputra.com</a>)</em></p> <p>Managing fifty separate WordPress instances is an operational nightmare. Updating core files, testing plugin compatibilities, and syncing theme deployments across fragmented server environments drains engineering hours and bleeds profit. The promised utopia is a Multisite network where you manage a single codebase, update a plugin once, and watch the entire network reflect the change instantly.</p> <p>I will say it clearly: most agencies push Multisite for the wrong reasons. They trap enterprise clients in a monolithic database nightmare simply because the agency wanted an easier time updating plugins. We build architecture for business ROI, not developer conveni
AgentX-Phase2: 49-Model Byzantine FBA Consensus — Building Cool Agents that Modernize COBOL to Rust
<h1> AgentX-Phase2: 49-Model Byzantine FBA Consensus </h1> <h2> Building Cool Agents that Modernize COBOL to Rust </h2> <p><strong>Author:</strong> Venkateshwar Rao Nagala | Founder & CEO<br><br> <strong>Company:</strong> For the Cloud By the Cloud | Hyderabad, India<br><br> <strong>Submission:</strong> Solo.io MCP_HACK//26 — Building Cool Agents<br><br> <strong>GitHub:</strong> <a href="https://github.com/tenalirama2005/AgentX-Phase2" rel="noopener noreferrer">https://github.com/tenalirama2005/AgentX-Phase2</a><br><br> <strong>Demo Video:</strong> <a href="https://youtu.be/5_FJA_WUlXQ" rel="noopener noreferrer">https://youtu.be/5_FJA_WUlXQ</a><br><br> <strong>Full Demo (4:44):</strong> <a href="https://youtu.be/k4Xzbp-M2fc" rel="noopener noreferrer">https://youtu.be/k4Xzbp-M2fc</a> </
Choosing and Integrating Mobile Video SDKs: FFmpeg, ExoPlayer, and Commercial Options
<ul> <li>A pragmatic evaluation rubric: performance, licensing, and feature fit</li> <li>FFmpeg mobile, ExoPlayer, and MediaCodec — where each tool genuinely earns its keep</li> <li>Commercial SDKs and when enterprise support actually repays the cost</li> <li>Integration realities: maintenance, ABI churn, and the binary-size tax</li> <li>Practical application: migration checklist and benchmarking protocol</li> </ul> <p>Video is the single feature that will expose architectural compromises in seconds: dropped frames, battery complaints, and suddenly-visible license obligations. Choose the wrong video stack and you’ll pay in performance, team time, and sometimes legal review.</p> <p>Playback stutters are rarely the UI team's fault — they’re the symptom of a pipeline problem: wrong codec fall

Discussion
Sign in to join the discussion
No comments yet — be the first to share your thoughts!