Post content fact checking
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
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
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from 10up/classifai
-
wpvc
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
wpvc
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Register ClassifAI functionality with the Abilities APIPossibly taken @nhrrob claimed this 10 days ago. Openhelp wanted
Difficulty 4/5 3-5 days Newbie friendliness 48/100
10up/classifai#1249 · 1 assignee ·
Maintainers usually reply within 1 day
-
OpenAI usage tracking: Project ID setting is ignoredPossibly taken @dajiaohuang claimed this 30 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
BYOK Openai modelsOpen
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 1 day
Similar issues
-
Exclude module `require-dev` and `autoload-dev` from the generated `composer.json`Possibly taken @keiserjb claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
uiowa/uiowa#10310 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
mailcow/mailcow-dockerized#7677 · 1 comment ·
Maintainers usually reply within 1 day
-
a11y
Difficulty 2/5 1-3 hours Newbie friendliness 67/100