Outrage
Strongly condemnatory and angry wording.
Methodology 1.1.0
We describe observable wording, framing, sourcing, and context and support findings with excerpts. We do not decide whether the author is lying, what they truly think, or how they feel.
What scores mean
A value from 0 to 100 describes the intensity of observable language patterns in the analyzed text. It is not a probability, a media quality rating, or a measure of emotions, intent, or truthfulness.
Strongly condemnatory and angry wording.
Language of helplessness, irritation, and repeated complaints.
Ironic or mocking contrast in the wording.
Leading questions, insinuations, and unsupported implications.
Personal attacks, sharp confrontations, and denigration.
Concrete, verifiably phrased information; not factual correctness.
A second analysis layer
We separately examine whether the headline and composition push a conclusion, whether a disputed issue relies mainly on one side, whether claims are clearly attributed and supported within the article, and whether context needed to understand the dispute is missing.
The headline, lead, or composition pre-frames an emotional or evaluative conclusion.
A disputed issue relies mainly on one side without a relevant response.
The origin or status of important claims is insufficiently clear.
Significant claims lack a concrete basis stated within the article.
Information needed to interpret the reported dispute is missing.
Combined indicator
Rhetorical intensity summarizes how strongly five tracked rhetorical patterns appear in the article. A lower number means fewer of these patterns; it is not a poor rating.
The value is the arithmetic mean of outrage, frustration, sarcasm or irony, suggestiveness, and confrontation scores. Factual style is shown separately and is not included in the mean.
Few tracked rhetorical patterns.
Some patterns are more noticeable.
Patterns appear prominently in the text.
Patterns are very prominent in the text.
The bands are currently indicative and have not been calibrated against a human-annotated corpus. The indicator does not verify facts, source credibility, or the article's overall quality.
From URL to result
The URL, DNS results, and redirects pass SSRF checks; downloads have time and size limits.
The main text, headline, and available metadata are separated from HTML without running page scripts.
Segments are heuristically labeled as editorial voice, quoted person, headline, or unclear attribution.
The provider returns six language indicators, five editorial concerns, explanations, short supporting excerpts, and confidence levels.
The backend checks the schema, value ranges, offsets, and exact match of each excerpt against the extracted text.
Provenance, model, methodology version, time, and uncertainties are stored; the complete article is not publicly archived.
Technical design
The current version combines safe retrieval, full-article availability checks, normalized extraction, a structured model call, and several independent validations.
A lightweight HTTP request is tried first; dynamic content may fall back to an isolated browser.
Readability-v2 selects the main content and the system checks for a complete article before analysis.
The model returns only predefined JSON; article content is treated as untrusted input, not instructions.
A result is published only after schema, range, and textual evidence checks.
Quality assurance
We separate automated technical checks that already run from methodological validation that is still being prepared.
Implemented
Validation plan
Interpretation boundaries
MediaLens stays focused on the language of a specific text. It does not replace fact-checking, psychological assessment, or consideration of the wider social context.
MediaLens does not verify factual correctness or source reputation. It evaluates only support, attribution, balance, and context visible in the article.
We do not infer personality, mental state, hidden motives, or genuine emotions of the author or speaker from the text.
Irony, indirect speech, and missing context can produce an uncertain or incorrect result.
Automatic extraction can fail on paywalls, dynamic websites, or unusual page structures.
The result passed automated technical checks but has not been independently reviewed by a human under the methodology.
Transparent development
Changing the model, prompt, or rules can change the result. Every analysis therefore shows its technical provenance, and older results are not silently overwritten.