How FirstTide builds a story and checks it
FirstTide files every post about one event under one story. Then it gives the story a reliability level in words, with a one-line reason.
How a story forms
Posts across languages are matched on what they mean and filed under one story, at the town where it happened. Every post keeps a link to its original.
What gets a level?
The story, not each post. Its level is a word, from Very low to High.
What does it read?
3 things, kept apart.
- Your ratings
- How your team rates each channel it adds.
- Separate channels
- How many channels carry the story.
- The posts
- What they say about their source.
How does it move?
When a new channel joins, the level and the reason update, and the story's timeline records the change with the post behind it.
What does it tell you?
How well the story is reported across your channels, and what to open first. Every post is one click away, in its original language.
What if posts disagree, or nothing more comes?
Posts that disagree both stay on the story, each with its original. A story that no other channel picks up loses ground over time, and the reason says so.
Fire at a refinery in Tuapse after a reported drone attack
EN
Aggregator account
BREAKING: Major Russian refinery hit.
RU
Refinery operator's news feed
Пожар на территории НПЗ ликвидирован.
The fire on the refinery grounds is out.
Coming: a check on every post. It will read each post on its own and say, in words, how well the post backs its claim.
See it on a real story.
In 15 minutes we open a story on a demo list of public channels and walk through its level, its reason and the posts behind it. If it fits your work, a 30-day pilot follows on the channels your team picks.