Post content fact checking

Open
#761 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
php
Domain
ai, content

Research direction

Start by researching Loki and the existing ClassifAI architecture to assess available fact-checking tools and their applicability. Measure processing time for posts of varying lengths, then determine where an author- or editor-triggered check could fit in the pre-publish flow; the integration point and blocking behavior remain to be decided.

Written by the indexing model from the issue text.

Description

Is your enhancement related to a problem? Please describe.

AI tooling exists that can help automate the process of verifying factuality. Tools like Loki provide "a comprehensive pipeline for dissecting long texts into individual claims, assessing their worthiness for verification, generating queries for evidence search, crawling for evidence, and ultimately verifying the claims." Tools like Loki could be used to plug into a post's pre-publish flows and act as a fact checker (whether it blocks publishing or not is up to debate). Also worth validating is how long this takes to process post of varying lengths to help determine where best to integrate this sort of check (e.g. if its a lengthy process then probably before the pre-publish panel, potentially in an author/editor-triggered manner).

Designs

No response

Describe alternatives you've considered

Some research on available tools, their applicability into our ClassifAI architecture, and then some performance tests to then identify how and where best to integrate this sort of feature into ClassifAI.

Code of Conduct
  • I agree to follow this project's Code of Conduct
Dominant language
PHP
Stars
714
Forks
68
Avg merge
4h 32m
Merged PRs (30d)
23

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from 10up/classifai

All issues in 10up/classifai

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.