All projects

BiasLens

Public product name: BiasLens. Canonical product repository: bitbaum/biaslens.

Beta — running, not released

Problem

Media bias and lack of transparency in information sources, making it difficult for users to understand different perspectives and make informed decisions.

Solution

BiasLens provides a dynamic, explainable, and reproducible way to measure media bias, offering a per-article dashboard with bias scores, uncertainty metrics, and missing perspectives.

Mission

BiasLens aims to provide a transparent and explainable way to measure media bias, helping users understand different perspectives and make informed decisions.

Vision

BiasLens aspires to become a leading platform for media bias analysis, enabling users to navigate complex information landscapes with confidence.

Technical context

The stack has not been written down yet.

Investigate this project with Loki →

Sign in to ask about architecture, evidence, delivery risks and next steps in your workspace.

Roadmap

  1. A report worth reading

    in progress · 8/9 steps done

    • An evaluation harness and rubric that score reports before and after every method change — done
    • A test set of about twelve real Swiss and English articles in it — not done
    • A published catalogue of writing techniques, each with what counts and what does not — done
    • Quotes found even when a PDF or a copy-paste changed the spacing, hyphens or quotation marks — done
    • Articles read from PDF links and uploaded PDFs, including press clippings — done
    • Claims attributed to the person who made them, not to the article — done
    • Figures checked for a source, a sample size and contradictions within the article — done
    • The article shown with its passages highlighted, one tap to see why — done
    • The report in the reader's language, including Swiss German — done
    Where this comes from
  2. Replies you can send

    planned · 5/6 steps done

    • Saved reports with their own link — done
    • A reply page made for the person receiving it — done
    • Reply lengths for every occasion: one line, a short brief, a full page — done
    • A printable dossier of a reading, for classes and letters to the editor — not done
    • Share images for messages, posts and stories — done
    • Open any article by putting the BiasLens address in front of its link, or from the phone's share menu — done
    Where this comes from
  3. Who is speaking

    planned · 1/2 steps done

    • Profiles of authors, quoted people and outlets from sourced public records, with a source on every line — done
    • What BiasLens reports on an author's or outlet's articles show, with the number of articles and its limits stated — not done
    Where this comes from
  4. Rewrite studio

    planned · 6/7 steps done

    • A neutral version of the article that fixes the flagged passages — done
    • Each change in the neutral version linked to the passage it fixes — not done
    • A response to the article: from BiasLens, as a letter to the editor, or as a draft of your own — done
    • The same facts written from stated values (the eight smartvote dimensions) instead of a political label — done
    • "How would this outlet write it", always marked as a simulation — done
    • "How would this public figure answer it", only for people with a public body of work, always marked as a simulation — done
    • A check that a rewrite kept the original facts and added none — done
    Where this comes from
  5. Investigations you can return to

    planned · 0/3 steps done

    • Save, revisit and revise investigations across sessions — not done
    • Independent source retrieval with traceable citations — not done
    • Compare claims across sources without collapsing disagreement into a single truth or bias score — not done
    Where this comes from
  6. Conversation analysis you can inspect

    later · 0/2 steps done

    • Reviewable source timestamps and correction history on conversation records — not done
    • Audio and video transcription with editable speaker attribution, evaluated before any comparison is shown — not done
    Where this comes from
  7. Reasons to come back

    later · 0/4 steps done

    • Several outlets' coverage of one story, compared side by side — not done
    • A daily "spot the technique" round with a shareable result — not done
    • Replies that continue as a conversation between the two people — not done
    • Your reports and replies kept in your account — not done
    Where this comes from
  8. An open method you can challenge

    later · 0/4 steps done

    • "Disagree with this" on every finding, with corrections shown on the report — not done
    • Published accuracy per technique and per method version — not done
    • Moderated discussion and challenge resolution with a visible record of what changed and why — not done
    • Reproducible records of which model and provider produced a report, without implying that availability means quality — not done
    Where this comes from
  9. BiasLens as a publication

    later · 0/4 steps done

    • Regular published readings of the stories people are sending each other — not done
    • Labelled debates: two simulated outlets answer the same facts — not done
    • A newsletter, and audio and video versions of readings — not done
    • An interface for newsrooms and teachers — not done
    Where this comes from
  10. Article examination

    done · 4/4 steps done

    • Examine an article from a link or pasted text, with an exact passage behind each quoted claim — done
    • Ask questions about the article, answered from its text only — done
    • Choose the language of the analysis — done
    • Download a report with the method version and a digest of the examined text — done
    Where this comes from
  11. Foundations

    done · 3/3 steps done

    • A public method that separates facts, values and causal claims, open to challenge — done
    • Timed transcript analysis of debates: speaking time and overlaps — done
    • Accounts with passkeys and two-factor sign-in — done
    Where this comes from

Changelog

  1. October 26, 2026

    Who is speaking. Every report lists the people and organisations the article quotes or cites, how the article describes them and whether they support its main claim. The author is never listed as a source. The text, marked up. The article is shown with flagged passages highlighted. Tap one to see which technique it is, why it was flagged and a neutral wording. A published technique catalogue. Sixteen techniques, from a claim without a source to a poll without a sample size, each with what counts and what does not, on the method page. The numbers. Figures are listed with whether the article names a source, a sample size or a comparison, and figures that do not match each other are flagged. PDFs. Paste a link to a PDF, such as a press clipping, or upload one; its text appears in the paste box to check before examining. Report in your language. Headings and text follow the report language, including Swiss German with Swiss spelling, and the language is preselected from your browser. Progress while it works. The page says which step the examination is on. Claims belong to whoever made them. An explanation offered by a quoted expert is shown as that expert’s, not the article’s. Quotes survive copy-paste. A passage is found even when quotation marks, dashes, spaces or line breaks differ; a changed word still fails. No political labels. BiasLens no longer applies left/right or similar labels in its own voice; the rule and its word list are on the method page. Second sign-in factors apply everywhere. An account with two-factor sign-in now asks for it whichever way the person signs in.

  2. October 26, 2026

    Every reading has a link. A finished report is saved, without the article text, so it can be opened again and shared. The same text examined again opens the saved reading at once. Send a reply. Choose who it is for (a friend, a group chat, the author, a public post, a disagreement, a class), a length and what to include, and see exactly what will be sent before creating the link. A page for the person who receives it. It opens on their article and the three findings they can check against its own words, with an optional “guess first” question, the sender’s note and a way to reply back. Share images. Every reading and reply has a link preview image and downloadable square and story images that carry “AI reading · not a fact check” in the picture itself. More ways in. Put the BiasLens address in front of any article link, open /analyze?u= with a link, or install BiasLens and use “Share → BiasLens” from a news app on Android.

  3. October 26, 2026

    The same facts, told another way. Under every reading: rewrite the article as a neutral report, from one or two stated values (the smartvote dimensions), as a chosen outlet would have written it, or as a public figure might — or write a response to it from BiasLens, as a letter to the editor, or as your own reply. Labels that cannot be lost. Every text says who wrote it. An outlet or person is always marked “Simulation · not written by …”, and that label is written by BiasLens, not by the model. Only public figures. A person can be simulated only if Wikidata shows a public figure with a public body of work; private people never are, two people with the same name are not guessed between, and anyone can ask to be left out. What the framing did to the facts. A rewrite of the article is checked against the original: how many of its facts were kept, which were changed or left out, and any fact that was added. Send it. A rewrite can go out with a reply, and the person who receives it sees it with its label and the facts check.

  4. October 26, 2026

    Tap a name. Authors, quoted people and the outlet in a report open a profile: occupation, employer, offices, recorded party membership, owner and the owner’s owner, founding year, and the opening of the Wikipedia article — every line linked to its source on Wikidata. No guessing. A name is linked only when the article’s own description of the person matches the record; when two people fit, the reader chooses. BiasLens adds no rating or label of its own, and every profile has a way to report a mistake.

  5. October 26, 2026

    No invented figures. A neutral rewrite of an article that cites a poll without its sample once supplied a sample size and a margin of error the article never gave. A rewrite now says when the article leaves something out instead of filling the gap, and when the facts check finds an added fact the text is sent back once to remove it. The check shown is always the one of the text you read. Suggested rewordings in a report follow the same rule.

  6. October 26, 2026

    Nothing else is asked. No display name, and a password needs 8 characters instead of 12, with no other rule. The same change reaches every product on the shared account package (accountkit 0.7.0), so signing up looks and works the same everywhere.

  7. October 26, 2026

    Registration confirms the chosen password before submitting and offers show/hide controls. The shared account forms also include Spanish labels. What changed for people using BiasLens, newest first.

  8. October 26, 2026

    The research notebook is one box. Say or type what you want to understand, or tap one of three examples, and the notebook sets out the question, its scope, the explanations to keep open and what would change your mind. Talk to the same box to change it ("only Switzerland", "add an economic explanation"), take a suggestion with one tap, or undo. Everything it wrote is marked as a draft and editable with a tap. A source is a link. Paste it and the page's title fills itself; "supports, challenges or context" is one tap, and where in the source is optional. Speak to the article. The chat under a report has a microphone that works in every browser, and its first suggestions are the questions the report itself raised.

  9. October 26, 2026

    Signing up asks for the password once. The repeat field is gone; an eye inside the password field shows what you typed instead (accountkit 0.8.0, the same in every product on it).

  10. October 25, 2026

    Ask about the article. A conversation under the report answers questions from the article's own text and shows the passage behind each answer. Analysis language. The report can be written in English, German or French, whatever language the article is in. Account recovery. Resetting a password and recovering an account now complete end to end.

  11. October 24, 2026

    One visual system. Every BiasLens page uses the same type, spacing and controls, with clearer paths into examining a source, a question or a conversation. Built on the shared fleet foundation. Site header, footer, accounts and publishing come from the shared packages used across the fleet. Consistent reports. Reports follow the same structure whichever model or language produced them. Long articles. The article body is read before the length limit is applied, so long pages no longer lose their main text to navigation and boilerplate.

  12. October 23, 2026

    Accounts. Sign up and sign in with a password or a passkey and manage your profile. Article examination is easier to use. Clearer input, progress and error states on the examination page.

  13. October 22, 2026

    The open method, versioned. The Open Epistemic Method was published with its limits, evidence requirements and a public challenge path. Debate airtime. Paste a timestamped transcript to see each speaker's speaking time and where speakers overlapped, computed in your browser. Journal. Essays on the method, with an RSS feed.

  14. October 21, 2026

    Article analysis. Examine an article from a link or pasted text. The report separates factual, value and causal claims and shows the passage behind each quoted claim. Downloadable report. Save the report with its method version and a digest of the exact text examined. The open method. A public description of how claims, evidence and causal links are examined, with a way to challenge it. No false verification. The evidence-counting demonstration is no longer presented as a fact check.

Roadmap and changelog come from this project's canonical development record, read October 29, 2026.