linetrades

Precision signals for systematic traders.

A column by Kyle Donnelly

News

How TradingView’s New Moderation Policy Impacts Pine Script Developers

TradingView just moved the gate from after-the-fact takedowns to pre-publication moderator review for every new Pine Script indicator or strategy landing in the community feeds, according to the TradingView Blog.

Kyle Donnelly, Algorithmic Trader & Market Technician·updated August 15, 2026

How TradingView’s New Moderation Policy Impacts Pine Script Developers

The old model was publish-first, review-later; the new one flips that sequence, ostensibly to clean up feed noise and improve script discoverability. For systematic traders who actually source tooling from that feed, this is a workflow change with second-order consequences worth measuring before anyone celebrates a quieter signal stream.

The mechanism, and why it matters

Every freshly submitted script now sits in a moderation queue before it surfaces in community scripts. TradingView frames this as a quality filter — fewer low-effort repaints and indicator spam reaching the front page, better ranking for scripts that pass review. Reasonable hypothesis. The feed was noise-heavy; a casual scroll through the public library looked more like a graveyard of MACD variants and "no-repaint" labels than a usable research pool. A gate reduces surface area for garbage, which in theory raises the signal-to-noise ratio of what actually gets published.

Where I push back

But moderation introduces a variable that doesn't appear in the official framing: latency. A script I publish today doesn't reach the feed today. It reaches the feed whenever a moderator clears it. That adds a queue-dependent delay to the publish–track–iterate loop, and it changes the population of scripts that surface in ways the announcement doesn't address.

For a hobbyist this is irrelevant. For someone running a public signal service or iterating on a strategy in public, it breaks the feedback cadence. The metric I'm watching: median time between publication and first community fork or comment once the gate is live. If that stretches past 48 hours, the platform is functionally shifting from a real-time signal marketplace to a curated archive.

There's also a sampling problem. Moderators are humans. Human filters carry subjective variance — what one reviewer rejects as "misleading," another approves as "educational." The feed's composition will shift not just toward higher quality but toward whatever the moderation team subjectively weights. That's not a neutral filter. That's a policy layer with an undisclosed loss function.

What I'm tracking over the next month

  • Moderation latency. Median and tail distribution of publish-to-approval time. The tail matters more than the median — a 90th percentile of three days breaks rapid iteration.
  • Approval rate. What fraction of submitted scripts actually clear review. Above 80% and the gate is decorative. Below 50% and discoverability for new authors collapses into a curated bottleneck.
  • Post-gate feed composition. Are the scripts that surface after moderation measurably better by any objective standard — Sharpe, drawdown, forward-test performance — or just cleaner-looking? "Quality" is easy to claim. Quantifying it against the pre-gate population requires a controlled comparison nobody outside TradingView has access to.

The bottom line

Moderation is not a free filter. It costs time, injects subjective variance, and shifts the population of scripts that reach traders. Whether the cost is worth paying depends entirely on data we don't have yet, and I won't be running the numbers until enough post-gate publications accumulate to form a meaningful sample size.

For now, recalibrate your discovery workflow. The feed you were scrolling last week is not the feed that exists today.