Reading Lustro as an evidence pipeline, not a similarity score

I found Lustro while looking into research on antidisinformation clusters. One question kept me reading: if a story appears in Russian state media and later in a Polish outlet, what evidence would show how it got there?

Jakub Sikora’s whitepaper, Cross-Lingual Information Diffusion and Temporal Alignment: Russian State Media and Polish Outlets, is published under the ProjektLustro.eu Open Research Initiative. It looks at more than whether texts resemble each other across languages. Publication timing matters too, as does the evidence for a possible connection.

Similarity is a starting point

Cross-lingual similarity can turn up candidates. It cannot, on its own, tell you where a story came from. Two articles might cover the same event without either copying the other, and translation or paraphrase makes the comparison harder.

I’d want a pipeline to keep four questions separate:

1. Do the texts make the same specific claims?
2. Is there an explicit citation or other evidence of a source path?
3. Does the publication order support that path?
4. What is still uncertain after those checks?

This matters for engineers too. Fold candidate retrieval and source attribution into a single “match,” and the result may sound firmer than the evidence is. Timing can narrow the possibilities. It cannot prove intent or coordination.

I’d start with the reading version of the whitepaper to see the method and its limits, rather than treating a cluster as a verdict. The ProjektLustro.eu site is the project landing page.

I’m sharing the work, not claiming I built or independently reproduced it. Finding related content is one job. Showing how information moved is another.