# OSINT feed

Live updates from public reports.

My role: I design the collection and alerting workflow, including source selection and how related reports are grouped into updates.

I built this to follow developing events without reading the same report over and over. The workflow collects public reports and turns them into readable updates.

[Open live feed](https://raidz.net/projects/osint/#osint) — Live posts and media · last 60 minutes. If the connection fails, a labeled demo runs until it recovers.

## Explore the process

- Bring reports together News sources and public posts provide reports. The collection system retains references to the material each update came from.

- Find reports about the same event Related reports are grouped so repeated coverage does not overwhelm the feed. Several posts quoting one report still share one source.

- Separate support from repetition Early reports or conflicting accounts need judgment. A concise summary should preserve that uncertainty, even when many accounts repeat the same claim.

- Push the public update Delivered Signal posts are pushed to this site with their media. Source lists and outgoing links are removed from this public view.

## Reading the feed

New posts arrive automatically, and timestamps use your local time. Scroll up to read earlier posts; return to the bottom to follow updates.

## A readable public view

The collection and source-reference workflow runs privately. The website shows a limited feed with text and available media. It must distinguish current live items, a cached snapshot, and fictional fallback material.

The workflow helps organize reporting. It does not make every collected claim reliable. Keeping original references and uncertainty is part of making a summary useful.

## Related notes

- [One report, many reposts](https://raidz.net/notes/repeated-reports-and-evidence/)

[Read the Atlas integration notes](https://raidz.net/projects/atlas/)

Canonical HTML: [https://raidz.net/projects/osint/](https://raidz.net/projects/osint/)
